Home
last modified time | relevance | path

Searched full:series (Results 1 – 25 of 1195) sorted by relevance

12345678910>>...48

/linux/Documentation/gpu/amdgpu/
H A Dapu-asic-info-table.csv3 Ryzen 3000 series / AMD Ryzen Embedded V1*/R1* with Radeon Vega Gfx, RAVEN/PICASSO, DCN 1.0, 9.1.0,…
4 Ryzen 4000 series, RENOIR, DCN 2.1, 9.3, VCN 2.2, 4.1.2, 11.0.3
5 Ryzen 3000 series / AMD Ryzen Embedded V1*/R1* with Radeon Vega Gfx, RAVEN2, DCN 1.0, 9.2.2, VCN 1.…
7 Ryzen 5000 series / Ryzen 7x30 series, GREEN SARDINE / Cezanne / Barcelo / Barcelo-R, DCN 2.1, 9.3,…
8 Ryzen 6000 series / Ryzen 7x35 series / Ryzen 7x36 series, YELLOW CARP / Rembrandt / Rembrandt-R, 3…
9 Ryzen 7000 series (AM5), Raphael, 3.1.5, 10.3.6, 3.1.2, 5.2.6, 13.0.5
10 Ryzen 9000 series (AM5), Granite Ridge, 3.1.5, 10.3.6, 3.1.2, 5.2.6, 13.0.5
11 Ryzen 7x45 series (FL1), Dragon Range, 3.1.5, 10.3.6, 3.1.2, 5.2.6, 13.0.5
12 Ryzen 7x20 series, Mendocino, 3.1.6, 10.3.7, 3.1.1, 5.2.7, 13.0.8
13 Ryzen 7x40 series, Phoenix, 3.1.4, 11.0.1 / 11.0.4, 4.0.2, 6.0.1, 13.0.4 / 13.0.11
[all …]
H A Ddgpu-asic-info-table.csv2 AMD Radeon (TM) HD 8500M/ 8600M /M200 /M320 /M330 /M335 Series, HAINAN, --, 6, --, --
3 AMD Radeon HD 7800 /7900 /FireGL Series, TAHITI, DCE 6, 6, VCE 1 / UVD 3, --
5 AMD Radeon (TM) (HD|R7) 7800 /7970 /8800 /8970 /370/ Series, PITCAIRN, DCE 6, 6, VCE 1 / UVD 3, --
6 AMD Radeon (TM|R7|R9|HD) E8860 /M360 /7700 /7800 /8800 /9000(M) /W4100 Series, VERDE, DCE 6, 6, VCE…
8 AMD Radeon (R9|TM) 200 /390 /W8100 /W9100 Series, HAWAII, DCE 8, 7, VCE 2 / UVD 4.2, 1
10 AMD Radeon (TM) R9 200 /380 /W7100 /S7150 /M390 /M395 Series, TONGA, DCE 10, 8, VCE 3 / UVD 5, 3
11 AMD Radeon (FirePro) (TM) R9 Fury Series, FIJI, DCE 10, 8, VCE 3 / UVD 6, 3
12 Radeon RX 470 /480 /570 /580 /590 Series - AMD Radeon (TM) (Pro WX) 5100 /E9390 /E9560 /E9565 /V735…
13 Radeon (TM) (RX|Pro WX) E9260 /460 /V5300X /550 /560(X) Series, POLARIS11, DCE 11.2, 8, VCE 3.4 / U…
14 Radeon (RX/Pro) 500 /540(X) /550 /640 /WX2100 /WX3100 /WX200 Series, POLARIS12, DCE 11.2, 8, VCE 3.…
[all …]
/linux/drivers/ata/pata_parport/
H A DKconfig15 tristate "MicroSolutions backpack (Series 5) protocol"
19 parallel port Series 5 IDE protocol. (Most BACKPACK drives made
20 before 1999 were Series 5) Series 5 drives will NOT always have the
21 Series noted on the bottom of the drive. Series 6 drivers will.
23 In other words, if your BACKPACK drive doesn't say "Series 6" on the
27 tristate "MicroSolutions backpack (Series 6) protocol"
31 parallel port Series 6 IDE protocol. (Most BACKPACK drives made
32 after 1999 were Series 6) Series 6 drives will have the Series noted
33 on the bottom of the drive. Series 5 drivers don't always have it
36 In other words, if your BACKPACK drive says "Series 6" on the
/linux/arch/m68k/include/asm/
H A Dmachines.h46 #define SM_3_160 0x01 /* Sun 3/160 series */
47 #define SM_3_50 0x02 /* Sun 3/50 series */
48 #define SM_3_260 0x03 /* Sun 3/260 series */
49 #define SM_3_110 0x04 /* Sun 3/110 series */
50 #define SM_3_60 0x07 /* Sun 3/60 series */
51 #define SM_3_E 0x08 /* Sun 3/E series */
54 #define SM_3_460 0x01 /* Sun 3/460 (460,470,480) series */
55 #define SM_3_80 0x02 /* Sun 3/80 series */
58 #define SM_4_260 0x01 /* Sun 4/200 series */
59 #define SM_4_110 0x02 /* Sun 4/100 series */
[all …]
/linux/Documentation/devicetree/bindings/hwmon/
H A Dmoortec,mr75203.yaml32 Some of the units have number of series, each series can have slightly
94 moortec,ts-series:
106 Default for series 5 = 60000
107 Default for series 6 = 57400
115 Default for series 5 = 200000
116 Default for series 6 = 249400
124 Default for series 5 = 4094
125 Default for series 6 = 4096
132 Default for series 5 = -100
133 Default for series 6 = 0
/linux/drivers/phy/samsung/
H A DKconfig6 tristate "Exynos SoC series Display Port PHY driver"
15 tristate "S5P/Exynos SoC series MIPI CSI-2/DSI PHY driver"
29 Enable PCIe PHY support for Exynos SoC series.
33 tristate "Exynos SoC series UFS PHY driver"
42 tristate "S5P/Exynos SoC series USB 2.0 PHY driver"
80 tristate "Exynos5 SoC series USB DRD PHY driver"
88 Enable USB DRD PHY support for Exynos 5 SoC series.
90 present on Exynos5 SoC series.
/linux/drivers/net/dsa/microchip/
H A DKconfig3 tristate "Microchip KSZ8XXX/KSZ9XXX/LAN937X series switch support"
11 LAN937X series switch chips, being KSZ8863/8873,
17 tristate "KSZ series I2C connected switch driver"
24 tristate "KSZ series SPI connected switch driver"
36 KSZ8563/KSZ9563/LAN937x series of switches. KSZ9563/KSZ8563 supports
41 tristate "KSZ series SMI connected switch driver"
/linux/drivers/thermal/st/
H A DKconfig7 tristate "Thermal sensors on STMicroelectronics STi series of SoCs"
9 Support for thermal sensors on STMicroelectronics STi series of SoCs.
13 tristate "STi series memory mapped access based thermal sensors"
16 tristate "Thermal framework support on STMicroelectronics STM32 series of SoCs"
20 Support for thermal framework on STMicroelectronics STM32 series of
/linux/Documentation/scsi/
H A Dscsi-generic.rst28 - sg version 2 from lk 2.2.6 in the 2.2 series. It is based on
30 - sg version 3 found in the lk 2.4 series (and the lk 2.5 series).
40 This describes the sg version 3 driver found in the lk 2.4 series.
43 lk 2.2 series can be found at
66 Both packages will work in the lk 2.4 series. However, sg3_utils offers more
76 Here is a list of Linux kernels in the 2.4 series that had the new version
87 For reference here is a list of Linux kernels in the 2.2 series that had
99 The lk 2.5 development series currently contains sg version 3.5.23
/linux/arch/m68k/sun3/
H A Didprom.c33 { .name = "Sun 3/160 Series", .id_machtype = (SM_SUN3 | SM_3_160) },
35 { .name = "Sun 3/260 Series", .id_machtype = (SM_SUN3 | SM_3_260) },
36 { .name = "Sun 3/110 Series", .id_machtype = (SM_SUN3 | SM_3_110) },
40 { .name = "Sun 3/460 Series", .id_machtype = (SM_SUN3X | SM_3_460) },
43 // { .name = "Sun 4/100 Series", .id_machtype = (SM_SUN4 | SM_4_110) },
44 // { .name = "Sun 4/200 Series", .id_machtype = (SM_SUN4 | SM_4_260) },
45 // { .name = "Sun 4/300 Series", .id_machtype = (SM_SUN4 | SM_4_330) },
46 // { .name = "Sun 4/400 Series", .id_machtype = (SM_SUN4 | SM_4_470) },
/linux/Documentation/devicetree/bindings/iio/pressure/
H A Dhoneywell,hsc030pa.yaml7 title: Honeywell TruStability HSC and SSC pressure sensor series
11 series.
17 The vendor calls them "HSC series" and "SSC series". All of them have an
34 …nsors/board-mount-pressure-sensors/trustability-hsc-series/documents/sps-siot-trustability-hsc-ser…
35 …nsors/board-mount-pressure-sensors/trustability-ssc-series/documents/sps-siot-trustability-ssc-ser…
/linux/drivers/misc/mei/
H A DKconfig24 7 Series Chipset Family
25 6 Series Chipset Family
26 5 Series Chipset Family
27 4 Series Chipset Family
28 Mobile 4 Series Chipset Family
/linux/Documentation/arch/arm/spear/
H A Doverview.rst19 - SPEAr3XX (3XX SOC series, based on ARM9)
26 - SPEAr6XX (6XX SOC series, based on ARM9)
29 - SPEAr13XX (13XX SOC series, based on ARM CORTEXA9)
52 Each machine series have a directory with name arch/arm/mach-spear followed by
53 series name. Like mach-spear3xx, mach-spear6xx and mach-spear13xx.
/linux/Documentation/process/
H A Dmaintainer-kvm-x86.rst67 room for the size of a series, patches that are "cache hot", etc. Fixes,
80 on series that break the build or fail tests lead to unhappy maintainers!
98 The only exception to using ``kvm-x86/next`` as the base is if a patch/series
99 is a multi-arch series, i.e. has non-trivial modifications to common KVM code
101 arch patch/series should instead be based on a common, stable point in KVM's
103 you're unsure whether a patch/series is truly multi-arch, err on the side of
112 :ref:`maintainer-tip-coding-style`, as patches/series often touch both KVM and
211 E.g. when doing a series of "git blame", the details of each change along the
245 At a bare minimum, *all* patches in a series must build cleanly for KVM_INTEL=m
317 Do not explicitly reference bug reports, prior versions of a patch/series, etc.
[all …]
H A Dmaintainer-netdev.rst14 - don't post large series (> 15 patches), break them up
166 the mailing list. For example to mark a series as Changes Requested
171 As a result the bot will set the entire series to Changes Requested.
172 This may be useful when author discovers a bug in their own series
245 Please always resend the entire patch series and make sure you do number your
252 Occasionally a patch series gets applied before receiving critical feedback,
253 or the wrong version of a series gets applied.
258 the patches the way they would look like if your latest patch series was to be
295 should generally come as one series. If series becomes too large
301 user space patches should form separate series (threads) when posted
[all …]
H A D5.Posting.rst80 everything else should be made as a logical series of changes. Splitting
85 - The patch series you post will almost certainly not be the series of
106 patch series is interrupted in the middle, the result should still be a
107 working kernel. Partial application of a patch series is a common
118 - It can be tempting to add a whole new infrastructure with a series of
120 in the series enables the whole thing. This temptation should be
121 avoided if possible; if that series adds regressions, bisection will
126 Working to create the perfect patch series can be a frustrating process
134 So now you have a perfect series of patches for posting, but the work is
346 patches in the series, and "subsys" is the name of the affected subsystem.
[all …]
/linux/Documentation/devicetree/bindings/gpio/
H A Dgpio-palmas.txt5 - "ti,palams-gpio" for palma series of the GPIO controller
6 - "ti,tps80036-gpio" for Palma series device TPS80036.
7 - "ti,tps65913-gpio" for palma series device TPS65913.
8 - "ti,tps65914-gpio" for palma series device TPS65914.
/linux/sound/firewire/
H A DKconfig33 * Midas Klark Teknik VeniceF series
54 * Mackie(Loud) Onyx-i series (former models)
108 * Behringer Digital Mixer X32 series (X-UF Card)
151 tristate "TASCAM FireWire series support"
164 tristate "Mark of the unicorn FireWire series support"
191 tristate "RME Fireface series support"
195 Say Y here to include support for RME fireface series.
/linux/arch/loongarch/kernel/
H A Dmcount_dyn.S25 * that the T series regs are available and safe because each C functions
91 * As we didn't use S series regs in this assmembly code and all calls
92 * are C function which will save S series regs by themselves, there is
93 * no need to restore S series regs. The T series is available and safe
94 * at the callsite, so there is no need to restore the T series regs.
/linux/drivers/scsi/qla2xxx/
H A DKconfig35 tristate "TCM_QLA2XXX fabric module for QLogic 24xx+ series target mode HBAs"
42 series target mode HBAs.
46 bool "TCM_QLA2XXX fabric module DEBUG mode for QLogic 24xx+ series target mode HBAs"
50 QLogic 24xx+ series target mode HBAs.
/linux/Documentation/devicetree/bindings/pwm/
H A Dti,twl-pwm.txt1 Texas Instruments TWL series PWM drivers
4 On TWL4030 series: PWM1 and PWM2
5 On TWL6030 series: PWM0 and PWM1
H A Dti,twl-pwmled.txt1 Texas Instruments TWL series PWM drivers connected to LED terminals
4 On TWL4030 series: PWMA and PWMB (connected to LEDA and LEDB terminals)
5 On TWL6030 series: LED PWM (mainly used as charging indicator LED)
/linux/drivers/net/ethernet/brocade/bna/
H A DKconfig3 # QLogic BR-series network device configuration
7 tristate "QLogic BR-series 1010/1020/1860 10Gb Ethernet Driver support"
10 This driver supports QLogic BR-series 1010/1020/1860 10Gb CEE capable
/linux/drivers/comedi/drivers/ni_routing/
H A DREADME62 (a) ni_route_values/ni_[series-label]series.c
229 NI_CtrA(0) G0_A_Select see M-Series user
231 NI_CtrA(1) G1_A_Select see M-Series user
233 NI_CtrB(0) G0_B_Select, up/down see M-Series user
235 NI_CtrB(1) G1_B_Select, up/down see M-Series user
237 NI_CtrZ(0) see M-Series user
239 NI_CtrZ(1) see M-Series user
/linux/drivers/net/ethernet/brocade/
H A DKconfig3 # QLogic BR-series device configuration
7 bool "QLogic BR-series devices"
15 the questions about QLogic BR-series cards. If you say Y, you will be

12345678910>>...48