Home
last modified time | relevance | path

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

12

/drivers/mtd/lpddr/
Dlpddr_cmds.c92 shared[i].writing = shared[i].erasing = NULL; in lpddr_cmdset()
213 contender = shared->writing; in get_chip()
267 shared->writing = chip; in get_chip()
339 if (shared->writing == chip && chip->oldstate == FL_READY) { in put_chip()
341 shared->writing = shared->erasing; in put_chip()
342 if (shared->writing && shared->writing != chip) { in put_chip()
344 struct flchip *loaner = shared->writing; in put_chip()
355 shared->writing = NULL; in put_chip()
356 } else if (shared->erasing == chip && shared->writing != chip) { in put_chip()
/drivers/firmware/google/
DKconfig17 platforms. This provides an interface for writing to and
18 clearing the EFI event log and reading and writing NVRAM
/drivers/staging/xgifb/
DTODO2 going to be long. So, I'm writing "cleanups" and not the list.
/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.
Ddevice.txt3 This is not intended to provide a comprehensive guide to writing an
41 Raw value writing function. Used for writable device values such
/drivers/block/
DKconfig163 Synchronous operation (i.e. always writing data to the host's disk
190 writing them to floppy. Furthermore, some Linux distributions avoid
349 tristate "Packet writing on CD/DVD media (DEPRECATED)"
356 If you have a CDROM/DVD drive that supports packet writing, say
361 Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
365 See the file <file:Documentation/cdrom/packet-writing.txt>
380 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.c299 static int hpt3x2n_use_dpll(struct ata_port *ap, int writing) in hpt3x2n_use_dpll() argument
304 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.c772 shared[i].writing = shared[i].erasing = NULL; in cfi_intelext_partition_fixup()
949 contender = shared->writing; in get_chip()
1003 shared->writing = chip; in get_chip()
1022 if (shared->writing == chip && chip->oldstate == FL_READY) { in put_chip()
1024 shared->writing = shared->erasing; in put_chip()
1025 if (shared->writing && shared->writing != chip) { in put_chip()
1027 struct flchip *loaner = shared->writing; in put_chip()
1038 shared->writing = NULL; in put_chip()
1039 } else if (shared->erasing == chip && shared->writing != chip) { in put_chip()
DKconfig49 data bits when writing the 'magic' commands to the chips. Saying
157 This enables support for reading, writing and locking so called
/drivers/scsi/
Dst.h45 int writing; member
/drivers/soc/ti/
DKconfig16 Packets are queued/de-queued by writing/reading descriptor address
/drivers/pnp/pnpbios/
DKconfig33 not be notified of any resource changes made by writing directly.
/drivers/fmc/
DKconfig49 acquainted with a mezzanine before writing its specific driver.
/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/s390/char/
DKconfig196 prompt "API for writing z/VM monitor service records"
199 Character device driver for writing z/VM monitor service records
/drivers/block/drbd/
DKconfig51 The actual simulation of IO errors is done by writing 3 values to
/drivers/media/dvb-frontends/
Drtl2832.c191 u8 msb, lsb, reading[4], writing[4], len; in rtl2832_wr_demod_reg() local
212 writing[i] = (writing_tmp >> ((len - 1 - i) * 8)) & 0xff; in rtl2832_wr_demod_reg()
214 ret = regmap_bulk_write(dev->regmap, reg_start_addr, writing, len); in rtl2832_wr_demod_reg()
/drivers/i2c/busses/
Di2c-mpc.c126 static int i2c_wait(struct mpc_i2c *i2c, unsigned timeout, int writing) in i2c_wait() argument
172 if (writing && (cmd_err & CSR_RXAK)) { in i2c_wait()
/drivers/mmc/core/
DKconfig76 in host controllers. The tests are executed by writing to the
/drivers/gpu/drm/i915/
DKconfig.debug12 Do not enable this unless you are writing code for the i915.ko module.
/drivers/net/wireless/marvell/mwifiex/
DREADME7 # is available by writing to the Free Software Foundation, Inc.,
191 2) For writing value to firmware memory location.
/drivers/char/
DKconfig59 If you say Y here, the support for writing user messages (i.e.
86 bool "Enable writing support of OTP pages"
90 If you say Y here, you will enable support for writing of the
280 power-off and for which writing to disk is too insecure. Note
/drivers/xen/
DKconfig49 could be added by writing proper value to
117 For example, by reading and writing the "xenbus" file, guests

12