Home
last modified time | relevance | path

Searched refs:writing (Results 1 – 25 of 42) sorted by relevance

12

/drivers/mtd/lpddr/
Dlpddr_cmds.c78 shared[i].writing = shared[i].erasing = NULL; in lpddr_cmdset()
227 contender = shared->writing; in get_chip()
281 shared->writing = chip; in get_chip()
353 if (shared->writing == chip && chip->oldstate == FL_READY) { in put_chip()
355 shared->writing = shared->erasing; in put_chip()
356 if (shared->writing && shared->writing != chip) { in put_chip()
358 struct flchip *loaner = shared->writing; in put_chip()
369 shared->writing = NULL; in put_chip()
370 } else if (shared->erasing == chip && shared->writing != chip) { in put_chip()
/drivers/firmware/google/
DKconfig17 platforms. This provides an interface for writing to and
19 driver provides an interface for reading and writing NVRAM
/drivers/staging/iio/Documentation/
Dsysfs-bus-iio-dds10 can control the desired active tuning word by writing Y to the
41 accumulator output by writing Y to the phase_en file.
/drivers/block/
DKconfig157 Synchronous operation (i.e. always writing data to the host's disk
184 writing them to floppy. Furthermore, some Linux distributions avoid
312 tristate "Packet writing on CD/DVD media (DEPRECATED)"
320 If you have a CDROM/DVD drive that supports packet writing, say
325 Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
329 See the file <file:Documentation/cdrom/packet-writing.rst>
344 a disc is opened for writing.
/drivers/staging/fbtft/
DREADME5 The module 'fbtft' makes writing drivers for some of these displays very easy.
/drivers/ata/
Dpata_hpt3x2n.c300 static int hpt3x2n_use_dpll(struct ata_port *ap, int writing) in hpt3x2n_use_dpll() argument
305 if (writing) in hpt3x2n_use_dpll()
/drivers/staging/greybus/Documentation/
Dsysfs-bus-greybus110 If the value read is "off", then writing "on" (or '1', 'y',
115 If the value read is "on", then writing "off" (or '0', 'n',
259 file will disable the watchdog, writing 1 will enable it.
/drivers/mtd/chips/
Dcfi_cmdset_0001.c796 shared[i].writing = shared[i].erasing = NULL; in cfi_intelext_partition_fixup()
973 contender = shared->writing; in get_chip()
1027 shared->writing = chip; in get_chip()
1046 if (shared->writing == chip && chip->oldstate == FL_READY) { in put_chip()
1048 shared->writing = shared->erasing; in put_chip()
1049 if (shared->writing && shared->writing != chip) { in put_chip()
1051 struct flchip *loaner = shared->writing; in put_chip()
1062 shared->writing = NULL; in put_chip()
1063 } else if (shared->erasing == chip && shared->writing != chip) { in put_chip()
DKconfig50 data bits when writing the 'magic' commands to the chips. Saying
160 This enables support for reading, writing and locking so called
/drivers/scsi/
Dst.h44 int writing; member
Dscsi_ioctl.c416 int writing = 0; in sg_io() local
433 writing = 1; in sg_io()
443 rq = blk_get_request(sdev->request_queue, writing ? in sg_io()
/drivers/thunderbolt/
DKconfig24 Enables writing to device configuration registers through
/drivers/s390/char/
DKconfig176 prompt "API for writing z/VM monitor service records"
179 Character device driver for writing z/VM monitor service records
/drivers/pnp/pnpbios/
DKconfig34 not be notified of any resource changes made by writing directly.
/drivers/staging/fieldbus/Documentation/ABI/
Dsysfs-class-fieldbus-dev37 Note: this area is accessible by writing to the associated
/drivers/staging/greybus/tools/
DREADME.loopback31 type - By writing the test type to this file, the test starts.
90 …specified printout is in a user-friendly non-CSV format. This option suppresses writing to CSV file
/drivers/acpi/pmic/
DKconfig8 to control power rails and sensor reading/writing on the
/drivers/block/drbd/
DKconfig50 The actual simulation of IO errors is done by writing 3 values to
/drivers/media/dvb-frontends/
Drtl2832.c178 u8 msb, lsb, reading[4], writing[4], len; in rtl2832_wr_demod_reg() local
199 writing[i] = (writing_tmp >> ((len - 1 - i) * 8)) & 0xff; in rtl2832_wr_demod_reg()
201 ret = regmap_bulk_write(dev->regmap, reg_start_addr, writing, len); in rtl2832_wr_demod_reg()
/drivers/mmc/core/
DKconfig77 in host controllers. The tests are executed by writing to the
/drivers/soc/ti/
DKconfig18 Packets are queued/de-queued by writing/reading descriptor address
/drivers/net/wireless/marvell/mwifiex/
DREADME8 # is available by writing to the Free Software Foundation, Inc.,
192 2) For writing value to firmware memory location.
/drivers/xen/
DKconfig37 could be added by writing proper value to
106 For example, by reading and writing the "xenbus" file, guests
/drivers/md/
Dmd-bitmap.c1005 int writing = 0; in md_bitmap_unplug() local
1018 if (!writing) { in md_bitmap_unplug()
1026 writing = 1; in md_bitmap_unplug()
1029 if (writing) in md_bitmap_unplug()
/drivers/net/wireless/ralink/rt2x00/
DKconfig261 These debugfs files support both reading and writing of the

12