Searched full:revisions (Results 1 – 25 of 319) sorted by relevance
12345678910>>...13
| /Linux-v5.10/arch/mips/include/asm/sibyte/ |
| D | sb1250_defs.h | 33 * for chip features only present in certain chip revisions.
62 * and earlier revisions of the named chip type.
78 * Mask values currently include room for additional revisions of each
97 /* Bit mask for chip/revision. (use _ALL for all revisions of a chip). */
103 /* Default constant value for all chips, all revisions */
120 /* Bit mask for revisions of chip exclusively before the named revision. */
124 /* Bit mask for revisions of chip exclusively after the named revision. */
|
| /Linux-v5.10/Documentation/hwmon/ |
| D | abituguru.rst | 19 it to behave as a hwmon IC. There are many different revisions of the
20 firmware and thus effectively many different revisions of the uGuru.
21 Below is an incomplete list with which revisions are used for which
32 .. [1] For revisions 2 and 3 uGuru's the driver can autodetect the
|
| D | k8temp.rst | 24 revisions of K8 except the first two revisions (SH-B0 and SH-B3).
53 For newer revisions of CPU (rev F, socket AM2) there is a mathematically
|
| D | abituguru3.rst | 15 it to behave as a hwmon IC. There are many different revisions of the
16 firmware and thus effectively many different revisions of the uGuru.
17 Below is an incomplete list with which revisions are used for which
|
| /Linux-v5.10/arch/mips/include/asm/octeon/ |
| D | cvmx-helper-board.h | 68 * data to determine board types and revisions. It relys on the
86 * data to determine board types and revisions. It relys on the
108 * data to determine board types and revisions. It relys on the
|
| /Linux-v5.10/Documentation/devicetree/bindings/arm/msm/ |
| D | qcom,saw2.txt | 10 Multiple revisions of the SAW hardware are supported using these Device Nodes.
11 SAW2 revisions differ in the register offset and configuration data. Also, the
|
| /Linux-v5.10/arch/mips/cavium-octeon/executive/ |
| D | cvmx-helper-board.c | 55 * data to determine board types and revisions. It replies on the
200 * data to determine board types and revisions. It relies on the
287 * data to determine board types and revisions. It relys on the
|
| /Linux-v5.10/drivers/pinctrl/mvebu/ |
| D | pinctrl-mvebu.h | 80 * The variant can be used to combine different revisions of one SoC to a
120 * setting and allows to distinguish between different revisions of one SoC.
|
| /Linux-v5.10/drivers/scsi/ |
| D | scsi.h | 7 * Subsequent revisions: Eric Youngdale
|
| /Linux-v5.10/Documentation/devicetree/bindings/arm/ |
| D | fw-cfg.txt | 26 revisions / feature bits.
|
| /Linux-v5.10/Documentation/devicetree/bindings/i2c/ |
| D | brcm,iproc-i2c.txt | 24 Should contain the I2C interrupt. For certain revisions of the I2C
|
| /Linux-v5.10/drivers/net/dsa/sja1105/ |
| D | Kconfig | 12 linkage to PHYLINK. The driver supports the following revisions:
|
| /Linux-v5.10/include/kvm/ |
| D | arm_psci.h | 29 * revisions. It is thus safe to return the latest, unless in kvm_psci_version()
|
| /Linux-v5.10/drivers/pwm/ |
| D | pwm-atmel-hlcdc.c | 66 /* Errata: cannot use slow clk on some IP revisions */ in atmel_hlcdc_pwm_apply()
79 /* Errata: cannot divide by 1 on some IP revisions */ in atmel_hlcdc_pwm_apply()
|
| /Linux-v5.10/Documentation/devicetree/bindings/net/ |
| D | micrel.txt | 28 Note that this option in only needed for certain PHY revisions with a
|
| /Linux-v5.10/drivers/phy/ti/ |
| D | phy-dm816x-usb.c | 34 * kernel is writing to those so it's possible that later revisions
151 * what the TI tree is doing in case later revisions use in dm816x_usb_phy_runtime_resume()
|
| /Linux-v5.10/drivers/net/wireless/broadcom/brcm80211/brcmfmac/ |
| D | firmware.h | 20 * @revmask: bitmask of revisions, e.g. 0x10 means rev 4 only, 0xf means rev 0-3
|
| /Linux-v5.10/Documentation/devicetree/bindings/iommu/ |
| D | arm,smmu-v3.yaml | 15 revisions, replacing the MMIO register interface with in-memory command
|
| /Linux-v5.10/Documentation/power/ |
| D | suspend-and-cpuhotplug.rst | 197 In this case since we probably need to apply different microcode revisions
250 type/model and the need for validating whether the microcode revisions are
|
| /Linux-v5.10/Documentation/virt/kvm/arm/ |
| D | psci.rst | 16 observe two different "firmware" revisions. This could cause issues if
|
| /Linux-v5.10/Documentation/devicetree/bindings/memory-controllers/ti/ |
| D | emif.txt | 6 of the EMIF IP and memory parts attached to it. Certain revisions
|
| /Linux-v5.10/arch/sparc/include/asm/ |
| D | mbus.h | 54 #define ROSS_604_REV_CDE 0x0 /* revisions c, d, and e */
|
| /Linux-v5.10/include/video/ |
| D | uvesafb.h | 33 /* for all VBE revisions */
|
| /Linux-v5.10/drivers/ide/ |
| D | alim15x3.c | 23 * Allow UDMA6 on revisions > 0xC4
138 * No UDMA on revisions <= 0x20
139 * Disk only for revisions < 0xC2
|
| /Linux-v5.10/Documentation/scsi/ |
| D | lpfc.rst | 31 In older revisions of the lpfc driver, the driver internally queued i/o
|
12345678910>>...13
