Home
last modified time | relevance | path

Searched refs:protect (Results 1 – 130 of 130) sorted by relevance

/linux-4.1.27/Documentation/misc-devices/
Deeprom30 Atmel 34C02B 2K 0x50 - 0x57, SW write protect at 0x30-37
31 Catalyst 34FC02 2K 0x50 - 0x57, SW write protect at 0x30-37
32 Catalyst 34RC02 2K 0x50 - 0x57, SW write protect at 0x30-37
33 Fairchild 34W02 2K 0x50 - 0x57, SW write protect at 0x30-37
34 Microchip 24AA52 2K 0x50 - 0x57, SW write protect at 0x30-37
35 ST M34C02 2K 0x50 - 0x57, SW write protect at 0x30-37
69 software write protect register at 0x30 - 0x37 (0x20 less than the memory
73 this address will write protect the memory array permanently, and the
/linux-4.1.27/Documentation/laptops/
Dfreefall.c81 static void protect(int seconds) in protect() function
103 protect(0); in ignore_me()
163 protect(21); in main()
Dthinkpad-acpi.txt1204 therefore, not suitable to protect against fan mode changes made through
/linux-4.1.27/drivers/target/
Dtarget_core_sbc.c603 sbc_set_prot_op_checks(u8 protect, bool fabric_prot, enum target_prot_type prot_type, in sbc_set_prot_op_checks() argument
608 protect ? TARGET_PROT_DOUT_PASS : in sbc_set_prot_op_checks()
610 switch (protect) { in sbc_set_prot_op_checks()
629 pr_err("Unsupported protect field %d\n", protect); in sbc_set_prot_op_checks()
634 protect ? TARGET_PROT_DIN_PASS : in sbc_set_prot_op_checks()
636 switch (protect) { in sbc_set_prot_op_checks()
655 pr_err("Unsupported protect field %d\n", protect); in sbc_set_prot_op_checks()
667 u8 protect = cdb[1] >> 5; in sbc_check_prot() local
673 if (unlikely(protect && in sbc_check_prot()
688 if (protect) in sbc_check_prot()
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/mmc/
Dsynopsys-dw-mshc.txt28 * wp-gpios: specifies the write protect gpio line. The format of the
30 for write-protect, this property is optional.
33 we'd assume that the write protect is hooked up directly to the
34 controller's special purpose write protect line (accessible via
36 want write protect. In that case specify 'disable-wp'.
Dfsl-esdhc.txt15 inverted write-protect state; New devices should use the generic
Dtmio_mmc.txt27 - toshiba,mmc-wrprotect-disable: write-protect detection is unavailable
/linux-4.1.27/arch/parisc/
DKconfig.debug6 bool "Write protect kernel read-only data structures"
/linux-4.1.27/drivers/input/mouse/
Dpsmouse.h127 bool protect; member
149 .protect = _protect, \
Dpsmouse-base.c1712 if (attr->protect) { in psmouse_attr_set_helper()
1728 if (attr->protect) { in psmouse_attr_set_helper()
/linux-4.1.27/drivers/gpu/host1x/
DKconfig18 Say yes if kernel should protect command streams from tampering.
/linux-4.1.27/drivers/irqchip/
Dirq-vic.c82 u32 protect; member
123 writel(vic->protect, base + VIC_PROTECT); in resume_one_vic()
152 vic->protect = readl(base + VIC_PROTECT); in suspend_one_vic()
/linux-4.1.27/Documentation/thermal/
Dnouveau_thermal26 In order to protect the GPU from overheating, Nouveau supports 4 configurable
32 * Shutdown: Shut the computer down to protect your GPU.
/linux-4.1.27/drivers/mtd/devices/
Ddocg3.c1731 int protect, dps0, dps0_low, dps0_high, dps1, dps1_low, dps1_high; in dbg_protection_show() local
1734 protect = doc_register_readb(docg3, DOC_PROTECTION); in dbg_protection_show()
1743 seq_printf(s, "Protection = 0x%02x (", protect); in dbg_protection_show()
1744 if (protect & DOC_PROTECT_FOUNDRY_OTP_LOCK) in dbg_protection_show()
1746 if (protect & DOC_PROTECT_CUSTOMER_OTP_LOCK) in dbg_protection_show()
1748 if (protect & DOC_PROTECT_LOCK_INPUT) in dbg_protection_show()
1750 if (protect & DOC_PROTECT_STICKY_LOCK) in dbg_protection_show()
1752 if (protect & DOC_PROTECT_PROTECTION_ENABLED) in dbg_protection_show()
1754 if (protect & DOC_PROTECT_IPL_DOWNLOAD_LOCK) in dbg_protection_show()
1756 if (protect & DOC_PROTECT_PROTECTION_ERROR) in dbg_protection_show()
/linux-4.1.27/drivers/gpu/drm/nouveau/dispnv04/
Dhw.h244 static inline void NVVgaProtect(struct drm_device *dev, int head, bool protect) in NVVgaProtect() argument
248 if (protect) { in NVVgaProtect()
256 NVSetEnablePalette(dev, head, protect); in NVVgaProtect()
/linux-4.1.27/drivers/net/wireless/ti/wl18xx/
Dscan.h68 u8 protect; /* ??? */ member
Dscan.c72 cmd->protect = 0; in wl18xx_scan_send()
208 cmd->protect = 0; in wl18xx_scan_sched_scan_config()
/linux-4.1.27/Documentation/devicetree/bindings/extcon/
Dextcon-rt8973a.txt5 is a USB port accessory detector and switch that is optimized to protect low
/linux-4.1.27/Documentation/devicetree/bindings/mtd/
Dlpc32xx-mlc.txt7 - gpios: GPIO specification for NAND write protect
Dlpc32xx-slc.txt7 - gpios: GPIO specification for NAND write protect
Dgpmc-nand.txt119 ECC_BYTES number of ECC bytes generated to protect
/linux-4.1.27/include/linux/
Damigaffs.h86 __be32 protect; member
/linux-4.1.27/drivers/scsi/
Dsd.c599 unsigned int protect = 0; in sd_setup_protect_cmnd() local
620 protect = 3 << 5; /* Disable target PI checking */ in sd_setup_protect_cmnd()
622 protect = 1 << 5; /* Enable target PI checking */ in sd_setup_protect_cmnd()
629 return protect; in sd_setup_protect_cmnd()
894 unsigned char protect; in sd_setup_read_write_cmnd() local
1014 protect = sd_setup_protect_cmnd(SCpnt, dix, dif); in sd_setup_read_write_cmnd()
1016 protect = 0; in sd_setup_read_write_cmnd()
1018 if (protect && sdkp->protection_type == SD_DIF_TYPE2_PROTECTION) { in sd_setup_read_write_cmnd()
1031 SCpnt->cmnd[10] = protect | ((rq->cmd_flags & REQ_FUA) ? 0x8 : 0); in sd_setup_read_write_cmnd()
1056 SCpnt->cmnd[1] = protect | ((rq->cmd_flags & REQ_FUA) ? 0x8 : 0); in sd_setup_read_write_cmnd()
[all …]
/linux-4.1.27/Documentation/locking/
Dspinlocks.txt33 before, because you have to make sure the spinlocks correctly protect the
98 If you have a case where you have to protect a data structure across
143 indeed), while write-locks need to protect themselves against interrupts.
Drt-mutex.txt26 mutexes which protect shared resources. Priority inheritance is not a
Drt-mutex-design.txt88 referring to spin locks that are used to protect parts of the PI
/linux-4.1.27/arch/avr32/boards/atngw100/
DKconfig38 This choice disables the detect pin and the write-protect pin for the
/linux-4.1.27/Documentation/RCU/
DarrayRCU.txt4 Although RCU is more commonly used to protect linked lists, it can
5 also be used to protect arrays. Three situations are as follows:
DNMI-RCU.txt4 Although RCU is usually used to protect read-mostly data structures,
Dlockdep-splat.txt70 And maybe that lock really does protect this reference. If so, the fix
Drculist_nulls.txt1 Using hlist_nulls to protect read-mostly linked lists and
DlistRCU.txt4 One of the best applications of RCU is to protect read-mostly linked lists
Drcubarrier.txt209 4 /* Take cpucontrol mutex to protect against CPU hotplug */
Drcu_dereference.txt68 o If you are using RCU to protect JITed functions, so that the
DwhatisRCU.txt321 all three mechanisms, but different defer and protect primitives are
354 This section shows a simple use of the core RCU API to protect a
DRTFP.txt194 tree using software transactional memory to protect concurrent updates
2401 Uses RCU to protect metadata used in dynamic analysis.
/linux-4.1.27/Documentation/security/
DLSM.txt27 what it tries to protect against and in what cases one would expect to
/linux-4.1.27/arch/um/os-Linux/skas/
Dmem.c197 int protect(struct mm_id * mm_idp, unsigned long addr, unsigned long len, in protect() function
/linux-4.1.27/drivers/block/
Dnvme-scsi.c683 u8 protect; in nvme_trans_standard_inquiry_page() local
711 (id_ns->dps) ? (protect = 0x01) : (protect = 0); in nvme_trans_standard_inquiry_page()
717 inq_response[5] = protect; /* sccs=0 | acc=0 | tpgs=0 | pc3=0 */ in nvme_trans_standard_inquiry_page()
875 u8 grd_chk, app_chk, ref_chk, protect; in nvme_trans_ext_inq_page() local
904 (id_ns->dps) ? (protect = 0x01) : (protect = 0); in nvme_trans_ext_inq_page()
905 grd_chk = protect << 2; in nvme_trans_ext_inq_page()
906 app_chk = protect << 1; in nvme_trans_ext_inq_page()
907 ref_chk = protect; in nvme_trans_ext_inq_page()
/linux-4.1.27/Documentation/
Dpreempt-locking.txt32 protect these situations by disabling preemption around them.
128 These may be used to protect from preemption, however, on exit, if preemption
Dvolatile-considered-harmful.txt13 do. In the kernel, one must protect shared data structures against
Dlocal_ops.txt26 require disabling interrupts to protect from interrupt handlers and it permits
Dpi-futex.txt38 I.e. critical RT apps often choose lock structures to protect critical
Dmagic-number.txt6 It is a *very* good idea to protect kernel data structures with magic
Dclk.txt283 Drivers don't need to manually protect resources shared between the operations
Dintel_txt.txt55 measure or protect the integrity of a running kernel, they all
Drobust-futexes.txt107 the futex hung. To protect against this possibility, userspace (glibc)
D00-INDEX301 - list of magic numbers used to mark/protect kernel data structures.
Dbcache.txt17 great lengths to protect your data - it reliably handles unclean shutdown. (It
Datomic_ops.txt524 locking scheme is being used to protect the bitmask, and thus less
DSubmittingPatches475 and protect the submitter from complaints. Note that under no circumstances
Dkernel-parameters.txt33 Double-quotes can be used to protect spaces in values, e.g.:
/linux-4.1.27/fs/affs/
Dinode.c49 prot = be32_to_cpu(tail->protect); in affs_iget()
188 tail->protect = cpu_to_be32(AFFS_I(inode)->i_protect); in affs_write_inode()
/linux-4.1.27/Documentation/gpio/
Dsysfs.txt11 know for example that GPIO #23 controls the write protect line used to
12 protect boot loader segments in flash memory. System upgrade procedures
Dgpio.txt64 MMC/SD card insertion/removal, detecting card write-protect status, driving
Dgpio-legacy.txt630 know for example that GPIO #23 controls the write protect line used to
631 protect boot loader segments in flash memory. System upgrade procedures
/linux-4.1.27/arch/um/kernel/
Dtlb.c72 ret = protect(hvc->id, op->u.mprotect.addr, in do_ops()
434 err = protect(mm_id, address, PAGE_SIZE, prot, 1, &flush); in flush_tlb_page()
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-driver-hid-roccat-arvo35 windows and application keys, to protect the user from the outcome
/linux-4.1.27/sound/isa/msnd/
Dmsnd.c310 int protect = start, nbanks = 0; in snd_msnd_DAPQ() local
354 if (protect) in snd_msnd_DAPQ()
/linux-4.1.27/fs/jffs2/
DREADME.Locking33 the alloc_sem is also used to protect the wbuf-related members of the
93 The erase_completion_lock is also used to protect the c->gc_task
/linux-4.1.27/Documentation/block/
Ddata-integrity.txt5 protect against data corruption. However, the detection of the
34 As written, the protocol extensions only protect the path between
86 they enable us to protect the entire path from application to storage
/linux-4.1.27/drivers/mtd/ubi/
Dwl.c648 int err, scrubbing = 0, torture = 0, protect = 0, erroneous = 0; local
771 protect = 1;
803 protect = 1;
894 if (protect)
/linux-4.1.27/Documentation/ide/
DChangeLog.ide-floppy.1996-200214 * Add media write-protect detection.
DChangeLog.ide-cd.1994-200427 * or data protect error.
/linux-4.1.27/Documentation/mmc/
Dmmc-dev-attrs.txt9 force_ro Enforce read-only access even if write protect switch is off.
/linux-4.1.27/drivers/extcon/
DKconfig92 and switch that is optimized to protect low voltage system
/linux-4.1.27/drivers/infiniband/hw/qib/
Dqib_mad.h323 u8 protect; member
/linux-4.1.27/arch/um/include/shared/
Dos.h260 extern int protect(struct mm_id * mm_idp, unsigned long addr,
/linux-4.1.27/arch/arm64/
DKconfig.debug65 patching and dynamic kernel tracing - and they might also protect
/linux-4.1.27/Documentation/ptp/
Dptp.txt67 should use spin_lock_irqsave/spin_unlock_irqrestore to protect
/linux-4.1.27/drivers/misc/eeprom/
DKconfig20 has any software write-protect mechanism you may want to review the
/linux-4.1.27/block/
DKconfig83 stored/retrieved to help protect the data. The block layer
/linux-4.1.27/security/integrity/ima/
DKconfig117 attribute containing the file hash measurement. To protect
/linux-4.1.27/Documentation/networking/
Dnetdevices.txt74 The locking there should also properly protect against
Dnetdev-features.txt138 protect against other callbacks (the rules you need to find out).
DLICENSE.qlge38 To protect your rights, we need to make restrictions that forbid
49 We protect your rights with two steps: (1) copyright the software, and
DLICENSE.qlcnic38 To protect your rights, we need to make restrictions that forbid
49 We protect your rights with two steps: (1) copyright the software, and
Dip-sysctl.txt1642 authentication to protect the operations of adding or removing new
/linux-4.1.27/drivers/w1/slaves/
DKconfig77 Say Y here to protect DS2433 data with a CRC16.
/linux-4.1.27/Documentation/x86/
Dmtrr.txt161 "write-protect", /* 5 */
258 "write-protect", /* 5 */
Dexception-tables.txt6 To protect itself the kernel has to verify this address.
/linux-4.1.27/drivers/gpu/drm/exynos/
Dexynos7_drm_decon.c381 unsigned int win, bool protect) in decon_shadow_protect_win() argument
388 if (protect) in decon_shadow_protect_win()
Dexynos_drm_fimd.c601 unsigned int win, bool protect) in fimd_shadow_protect_win() argument
614 if (protect) in fimd_shadow_protect_win()
/linux-4.1.27/arch/tile/kernel/
Dhardwall.c696 unsigned long protect = mfspr_XDN(hwt, DIRECTION_PROTECT); in stop_xdn_switch()
697 mtspr_XDN(hwt, DIRECTION_PROTECT, (protect | C_PROTECT) << 5); in stop_xdn_switch()
/linux-4.1.27/arch/x86/
DKconfig.debug90 bool "Write protect kernel read-only data structures"
115 patching and dynamic kernel tracing - and they might also protect
DKconfig1646 itself inside the kernel or to protect the kernel
/linux-4.1.27/Documentation/frv/
Dfeatures.txt96 windows, and (4) rearranges the protection registers to protect all of
127 Barring point (1), there is nothing to protect kernel data against
/linux-4.1.27/Documentation/devicetree/bindings/c6x/
Ddscr.txt50 offset and key values of two "kick" registers used to write protect other
/linux-4.1.27/arch/powerpc/boot/dts/
Dac14xx.dts170 wp-gpios = <&gpio_pic 24 0>; /* write protect */
Dxpedite5200.dts106 * 5: Flash write protect enable
Dxpedite5200_xmon.dts110 * 5: Flash write protect enable
/linux-4.1.27/Documentation/filesystems/
Dporting91 unlock_kernel() so that they would protect exactly what needs to be
247 shift lock_kernel() and unlock_kernel() so that they would protect
346 for details of what locks to replace dcache_lock with in order to protect
Dxfs-self-describing-metadata.txt55 of analysis. We can't protect against every possible type of error, but we can
95 Just adding a block number to the metadata is not sufficient to protect against
Daffs.txt39 protect If this option is set, the protection bits cannot be altered.
Dpath-lookup.txt198 protect the dentry object from disappearing, can perform a seqcount based
301 * Have a per-dentry seqlock to protect the dentry name, parent, and inode,
Drelay.txt420 function - it uses local_irqsave() to protect the buffer and should be
441 separated from the reserve, relay_reserve() doesn't protect the buffer
Dautofs4-mount-control.txt287 the new kernel pipe descriptor. In order to protect mounts against
DLocking474 Note: this does not protect the file->f_pos against concurrent modifications
/linux-4.1.27/security/
DKconfig105 int "Low address space for LSM to protect from user allocation"
/linux-4.1.27/Documentation/virtual/kvm/
Dlocking.txt16 shadow page table is present and it is caused by write-protect, that means
/linux-4.1.27/Documentation/power/
Dswsusp.txt277 It cannot protect your computer while it is suspended. Instead it does
278 protect from leaking sensitive data after resume from suspend.
303 As a rule of thumb use encrypted swap to protect your data while your
/linux-4.1.27/Documentation/video4linux/
Dvideobuf62 need to be an interrupt-safe spinlock which is used to protect (at least)
170 protect access to the data structures, type is the buffer type used by the
/linux-4.1.27/Documentation/scsi/
DLICENSE.qla4xxx39 To protect your rights, we need to make restrictions that forbid
50 We protect your rights with two steps: (1) copyright the software, and
DLICENSE.qla2xxx40 To protect your rights, we need to make restrictions that forbid
51 We protect your rights with two steps: (1) copyright the software, and
DChangeLog.megaraid603 vii. Do not use "host_lock', driver has fine-grain locks now to protect all
DChangeLog.1992-1997691 * scsi.c (scsi_times_out): Pass pid down so that we can protect
/linux-4.1.27/arch/frv/kernel/
Dentry.S699 # handle data DAT fault (write-protect exception)
/linux-4.1.27/drivers/iommu/
DKconfig94 can isolate the DMA memory of different devices and protect the
/linux-4.1.27/tools/usb/usbip/
DCOPYING28 To protect your rights, we need to make restrictions that forbid
39 We protect your rights with two steps: (1) copyright the software, and
/linux-4.1.27/drivers/staging/rtl8192e/
Dlicense34 To protect your rights, we need to make restrictions that forbid anyone to
44 We protect your rights with two steps: (1) copyright the software, and (2)
/linux-4.1.27/drivers/staging/rtl8192u/
Dcopying28 To protect your rights, we need to make restrictions that forbid
39 We protect your rights with two steps: (1) copyright the software, and
/linux-4.1.27/drivers/video/fbdev/
Ds3c-fb.c425 static void shadow_protect_win(struct s3c_fb_win *win, bool protect) in shadow_protect_win() argument
430 if (protect) { in shadow_protect_win()
DKconfig2231 buffer subsystem. Do NOT enable it for normal systems! To protect
/linux-4.1.27/
DCOPYING44 To protect your rights, we need to make restrictions that forbid
55 We protect your rights with two steps: (1) copyright the software, and
/linux-4.1.27/sound/oss/
Dmsnd_pinnacle.c853 register int protect = start, nbanks = 0; in pack_DAPF_to_DAPQ() local
863 if (protect) { in pack_DAPF_to_DAPQ()
/linux-4.1.27/lib/
DKconfig315 number of data bits to protect, 'm' should be chosen such
/linux-4.1.27/Documentation/serial/
Ddriver61 The port_sem semaphore is used to protect against ports being added/
/linux-4.1.27/arch/
DKconfig437 locking is needed to protect against concurrent accesses.
/linux-4.1.27/drivers/net/ethernet/broadcom/
Dtg3.c14450 u32 nvcfg1, protect = 0; in tg3_get_5755_nvram_info() local
14457 protect = 1; in tg3_get_5755_nvram_info()
14472 tp->nvram_size = (protect ? 0x3e200 : in tg3_get_5755_nvram_info()
14475 tp->nvram_size = (protect ? 0x1f200 : in tg3_get_5755_nvram_info()
14478 tp->nvram_size = (protect ? 0x1f200 : in tg3_get_5755_nvram_info()
14489 tp->nvram_size = (protect ? in tg3_get_5755_nvram_info()
14493 tp->nvram_size = (protect ? in tg3_get_5755_nvram_info()
14497 tp->nvram_size = (protect ? in tg3_get_5755_nvram_info()
14544 u32 nvcfg1, protect = 0; in tg3_get_5761_nvram_info() local
14551 protect = 1; in tg3_get_5761_nvram_info()
[all …]
/linux-4.1.27/mm/
DKconfig345 int "Low address space to protect from user allocation"
/linux-4.1.27/Documentation/trace/
Dring-buffer-design.txt678 Only writers move the tail page. This must be done atomically to protect
/linux-4.1.27/Documentation/filesystems/configfs/
Dconfigfs.txt341 protect modifications. Whenever a subsystem wants to navigate the
/linux-4.1.27/net/ipv4/
DKconfig679 Its main (only?) use is to protect BGP sessions between core routers
/linux-4.1.27/net/sched/
DKconfig343 want to protect Xen guests with Remus.
/linux-4.1.27/Documentation/sysctl/
Dvm.txt366 If you would like to protect more pages, smaller values are effective.
Dkernel.txt372 to protect against uses of %pK in dmesg(8) if leaking kernel pointer
/linux-4.1.27/arch/blackfin/
DKconfig1117 Use the processor's MPU to protect applications from accessing
/linux-4.1.27/arch/arm/
DKconfig.debug1593 patching and dynamic kernel tracing - and they might also protect
/linux-4.1.27/Documentation/filesystems/cifs/
DCHANGES921 Also included a modified version of his fix to protect global list manipulation of
/linux-4.1.27/arch/mips/
DKconfig2360 # moment we protect the user and offer the highmem option only on machines