Home
last modified time | relevance | path

Searched full:flagged (Results 1 – 25 of 324) sorted by relevance

12345678910>>...13

/kernel/linux/linux-6.6/Documentation/devicetree/bindings/serio/
Dps2-gpio.yaml18 the gpio used for the data signal - this should be flagged as
26 the gpio used for the clock signal - this should be flagged as
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/i2c/
Di2c-gpio.yaml22 gpio used for the sda signal, this should be flagged as
30 gpio used for the scl signal, this should be flagged as
/kernel/linux/linux-6.6/include/uapi/linux/
Dneighbour.h80 * flagged entries explicitly are (which is also consistent with the routing
87 * NTF_EXT_MANAGED flagged neigbor entries are managed by the kernel on behalf
91 * NTF_EXT_LOCKED flagged bridge FDB entries are entries generated by the
Dbsg.h30 __u64 request_tag; /* [i] {SCSI: task tag (only if flagged)} */
Ddlm.h51 * -EAGAIN if request would block and is flagged DLM_LKF_NOQUEUE
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/i2c/
Di2c-gpio.yaml22 gpio used for the sda signal, this should be flagged as
30 gpio used for the scl signal, this should be flagged as
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/input/
Datmel,maxtouch.yaml42 (active low). The line must be flagged with
49 (active low). The line must be flagged with
/kernel/linux/linux-6.6/drivers/power/supply/
Dmax8903_charger.c91 * library as the line should be flagged GPIO_ACTIVE_LOW in the device in max8903_dcin()
150 * library as the line should be flagged GPIO_ACTIVE_LOW in the device in max8903_usbin()
206 * library as the line should be flagged GPIO_ACTIVE_LOW in the device in max8903_fault()
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/gnss/
Dmediatek.yaml30 If the line is active low it should be flagged with GPIO_ACTIVE_LOW.
Dbrcm,bcm4751.yaml44 description: An optional active low reset line, should be flagged with
Dsirfstar.yaml46 description: An optional active low reset line, should be flagged with
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/light/
Dcm3605.txt14 to activate the ALS, should be flagged GPIO_ACTIVE_LOW)
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/iio/light/
Dcapella,cm3605.yaml29 ASET line (drive low to activate the ALS, should be flagged
/kernel/linux/linux-6.6/drivers/net/ethernet/toshiba/
Dspider_net.h151 /* we rely on flagged descriptor interrupts */
323 /* We rely on flagged descriptor interrupts */
/kernel/linux/linux-5.10/drivers/net/ethernet/toshiba/
Dspider_net.h152 /* we rely on flagged descriptor interrupts */
324 /* We rely on flagged descriptor interrupts */
/kernel/linux/linux-5.10/drivers/clk/davinci/
Dpll-da830.c27 * NB: Technically, the clocks flagged as SYSCLK_FIXED_DIV are "fixed ratio",
/kernel/linux/linux-6.6/drivers/clk/davinci/
Dpll-da830.c27 * NB: Technically, the clocks flagged as SYSCLK_FIXED_DIV are "fixed ratio",
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/nvmem/
Du-boot,env.yaml37 - description: Two redundant blocks with active one flagged
/kernel/linux/linux-6.6/Documentation/networking/
Drxrpc.rst244 (#) When receiving data or messages for a call, MSG_EOR is flagged by recvmsg
315 for the next taker. MSG_TRUNC will never be flagged.
319 flagged.
616 pick up. MSG_MORE will be flagged by recvmsg() if there's more reply data
625 buffer instead, and MSG_EOR will be flagged to indicate the end of that
724 be delivered with MSG_MORE flagged.
752 MSG_EOR will be flagged to indicate that this is the final message for
/kernel/linux/linux-5.10/Documentation/networking/
Drxrpc.rst244 (#) When receiving data or messages for a call, MSG_EOR is flagged by recvmsg
315 for the next taker. MSG_TRUNC will never be flagged.
319 flagged.
616 pick up. MSG_MORE will be flagged by recvmsg() if there's more reply data
625 buffer instead, and MSG_EOR will be flagged to indicate the end of that
724 be delivered with MSG_MORE flagged.
752 MSG_EOR will be flagged to indicate that this is the final message for
/kernel/linux/linux-6.6/fs/xfs/
Dxfs_health.c71 * However, we must be careful -- when FSCOUNTERS are flagged in xfs_health_unmount()
78 * there were filesystem problems, FSCOUNTERS was flagged, and in xfs_health_unmount()
/kernel/linux/linux-5.10/fs/xfs/
Dxfs_health.c73 * However, we must be careful -- when FSCOUNTERS are flagged in xfs_health_unmount()
80 * there were filesystem problems, FSCOUNTERS was flagged, and in xfs_health_unmount()
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/soc/qcom/
Dqcom,smsm.txt44 Nodes can either be flagged as an interrupt-controller to denote a remote
/kernel/linux/linux-5.10/include/uapi/linux/
Dbsg.h30 __u64 request_tag; /* [i] {SCSI: task tag (only if flagged)} */
Ddlm.h51 * -EAGAIN if request would block and is flagged DLM_LKF_NOQUEUE

12345678910>>...13