Searched full:considered (Results 1 – 25 of 232) sorted by relevance
12345678910
| /Documentation/xtensa/ |
| D | booting.rst | 20 virtual mapping. It is considered physical if it is within the range of
22 XCHAL_KSEG_PADDR + XCHAL_KSEG_SIZE), otherwise it is considered virtual.
|
| /Documentation/process/ |
| D | code-of-conduct-interpretation.rst | 52 considered a violation report unless you want it to be. If you are
93 sent to those mailing lists are considered covered by the Code of
111 may be considered for extreme circumstances.
119 standards or specifications, are not considered bugs.
|
| D | index.rst | 59 volatile-considered-harmful
|
| /Documentation/devicetree/bindings/mfd/ |
| D | aspeed-gfx.txt | 4 participates in pinmux requests on the g5 SoCs. It is therefore considered a
|
| D | twl-familly.txt | 17 it is considered as an interrupt controller cascaded to the SoC one.
|
| /Documentation/devicetree/bindings/w1/ |
| D | w1-gpio.txt | 13 - linux,open-drain: if specified, the data pin is considered in
|
| /Documentation/power/ |
| D | power_supply_class.rst | 106 Maximal/minimal means values of voltages when battery considered
125 design charge values, when battery considered full/empty.
133 considered full/empty at given conditions (temperature, age)".
210 seconds left for battery to be considered empty
213 seconds left for battery to be considered full
|
| /Documentation/dev-tools/ |
| D | kmemleak.rst | 91 An allocated block of memory is considered orphan if no pointer to its
95 block to a freeing function and therefore the block is considered a
101 considered orphan)
109 4. the remaining white objects are considered orphan and reported via
116 block is not considered a leak. One example is __vmalloc().
|
| /Documentation/devicetree/bindings/net/ |
| D | fsl-tsec-phy.txt | 22 When device_type is "mdio", the following strings are also considered:
43 is considered instructive, rather than descriptive. The reg property should
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-log.rst | 9 mirrors, a region would be considered dirty/inconsistent while you
12 Once all writes are complete, the region is considered clean again.
|
| /Documentation/translations/zh_CN/process/ |
| D | index.rst | 53 volatile-considered-harmful
|
| /Documentation/devicetree/bindings/clock/ |
| D | renesas,sh73a0-cpg-clocks.txt | 1 These bindings should be considered EXPERIMENTAL for now.
|
| D | renesas,r8a7740-cpg-clocks.txt | 1 These bindings should be considered EXPERIMENTAL for now.
|
| /Documentation/ABI/stable/ |
| D | sysfs-module | 23 considered stable, only the fact that they will be
|
| D | vdso | 23 ABI of those symbols is considered stable. It may vary across architectures,
|
| /Documentation/block/ |
| D | pr.rst | 44 All initiators with a registered key are considered reservation
51 All initiators with a registered key are considered reservation
|
| /Documentation/devicetree/bindings/sound/ |
| D | tdm-slot.txt | 28 number is considered 1 and 0 is 0. snd_soc_of_xlate_tdm_slot_mask()
|
| /Documentation/ABI/testing/ |
| D | debugfs-cec-error-inj | 31 Other than these basic rules described above this ABI is not considered
|
| D | sysfs-kernel-iommu_groups | 35 are considered to be relaxable and safe.
|
| /Documentation/devicetree/bindings/input/ |
| D | adc-keys.txt | 8 - keyup-threshold-microvolt: Voltage at which all the keys are considered up.
|
| /Documentation/translations/it_IT/process/ |
| D | index.rst | 60 volatile-considered-harmful
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | sharp,ls037v7dw01.txt | 21 configured with external pulls, all the GPIOs are considered optional with holes
|
| D | sharp,lq101r1sx01.txt | 8 driven by the first link (DSI-LINK1), left or even, is considered the primary
|
| /Documentation/devicetree/bindings/usb/ |
| D | mediatek,mtu3.txt | 31 it's considered valid for compatibility reasons, not allowed for
35 it's considered valid for compatibility reasons, not allowed for
|
| /Documentation/driver-api/ |
| D | device_connection.rst | 29 firmware, this is not a problem. It should be considered if the connection
|
12345678910