Home
last modified time | relevance | path

Searched refs:CHIP (Results 1 – 16 of 16) sorted by relevance

/linux-6.1.9/tools/testing/selftests/gpio/
Dgpio-sim.sh22 local CHIP=$1
24 for FILE in $CONFIGFS_DIR/$CHIP/*; do
30 LINES=`ls $CONFIGFS_DIR/$CHIP/$BANK/ | egrep ^line`
33 if [ -e $CONFIGFS_DIR/$CHIP/$BANK/$LINE/hog ]; then
34 rmdir $CONFIGFS_DIR/$CHIP/$BANK/$LINE/hog || \
38 rmdir $CONFIGFS_DIR/$CHIP/$BANK/$LINE || \
43 rmdir $CONFIGFS_DIR/$CHIP/$BANK
46 rmdir $CONFIGFS_DIR/$CHIP || fail "Unable to remove the chip"
50 for CHIP in `ls $CONFIGFS_DIR/`; do
51 remove_chip $CHIP
[all …]
/linux-6.1.9/Documentation/devicetree/bindings/net/
Dibm,emac.txt16 "ibm,emac-CHIP" where CHIP is the host ASIC (440gx,
170 "ibm,mcmal-CHIP" where CHIP is the host ASIC (like
190 "ibm,zmii-CHIP" where CHIP is the host ASIC (like
199 "ibm,rgmii-CHIP" where CHIP is the host ASIC (like
/linux-6.1.9/Documentation/devicetree/bindings/ata/
Dfsl-sata.txt8 "fsl,CHIP-sata", where CHIP is the processor
/linux-6.1.9/Documentation/i2c/busses/
Di2c-sis5595.rst67 is a BUS driver, not a CHIP driver. A BUS driver is used by other CHIP
/linux-6.1.9/Documentation/devicetree/bindings/powerpc/fsl/
Decm.txt46 Definition: Must include "fsl,CHIP-ecm", "fsl,ecm" where
47 CHIP is the processor (mpc8572, mpc8544, etc.)
Dmcm.txt46 Definition: Must include "fsl,CHIP-mcm", "fsl,mcm" where
47 CHIP is the processor (mpc8641, mpc8610, etc.)
Dmsi-pic.txt5 The first is "fsl,CHIP-msi", where CHIP is the processor(mpc8610, mpc8572,
/linux-6.1.9/drivers/staging/rtl8723bs/
DKconfig11 the wifi found on the 1st gen Intel Compute Stick, the CHIP
/linux-6.1.9/drivers/video/fbdev/
Dcirrusfb.c255 #define CHIP(id, btype) \ macro
259 CHIP(PCI_DEVICE_ID_CIRRUS_5436, BT_ALPINE),
260 CHIP(PCI_DEVICE_ID_CIRRUS_5434_8, BT_SD64),
261 CHIP(PCI_DEVICE_ID_CIRRUS_5434_4, BT_SD64),
262 CHIP(PCI_DEVICE_ID_CIRRUS_5430, BT_ALPINE), /* GD-5440 is same id */
263 CHIP(PCI_DEVICE_ID_CIRRUS_7543, BT_ALPINE),
264 CHIP(PCI_DEVICE_ID_CIRRUS_7548, BT_ALPINE),
265 CHIP(PCI_DEVICE_ID_CIRRUS_5480, BT_GD5480), /* MacPicasso likely */
266 CHIP(PCI_DEVICE_ID_CIRRUS_5446, BT_PICASSO4), /* Picasso 4 is 5446 */
267 CHIP(PCI_DEVICE_ID_CIRRUS_5462, BT_LAGUNA), /* CL Laguna */
[all …]
/linux-6.1.9/drivers/usb/gadget/legacy/
Dinode.c231 static const char *CHIP; variable
1670 if (0 != strcmp (CHIP, gadget->name)) { in gadgetfs_bind()
1672 shortname, CHIP, gadget->name); in gadgetfs_bind()
2023 CHIP = usb_get_gadget_udc_name(); in gadgetfs_fill_super()
2024 if (!CHIP) { in gadgetfs_fill_super()
2054 dev->dentry = gadgetfs_create_file(sb, CHIP, dev, &ep0_operations); in gadgetfs_fill_super()
2068 kfree(CHIP); in gadgetfs_fill_super()
2069 CHIP = NULL; in gadgetfs_fill_super()
2102 kfree(CHIP); in gadgetfs_kill_sb()
2103 CHIP = NULL; in gadgetfs_kill_sb()
/linux-6.1.9/Documentation/devicetree/bindings/phy/
Dmediatek,tphy.yaml43 0x0800 CHIP
52 0x1800 CHIP
61 into each port; a new bank MISC for u2 ports and CHIP for u3 ports are
/linux-6.1.9/Documentation/gpu/
Dkomeda-kms.rst328 achieve this, split the komeda device into two layers: CORE and CHIP.
331 - CHIP: for register programing and HW specific feature (limitation) handling.
333 CORE can access CHIP by three chip function structures:
/linux-6.1.9/arch/arm/boot/dts/
Dsun5i-gr8-chip-pro.dts219 * The CHIP Pro doesn't have a controllable VBUS, nor does it
/linux-6.1.9/Documentation/spi/
Dspi-summary.rst353 .name = "CHIP",
363 device whose board_info gave a modalias of "CHIP". Your probe() code
371 struct CHIP *chip;
/linux-6.1.9/Documentation/devicetree/bindings/arm/
Dsunxi.yaml544 - description: NextThing Co. CHIP
550 - description: NextThing Co. CHIP Pro
/linux-6.1.9/
DMAINTAINERS6612 DRM DRIVER FOR PARADE PS8640 BRIDGE CHIP
6741 DRM DRIVER FOR TI SN65DSI86 BRIDGE CHIP
18368 SCR24X CHIP CARD INTERFACE DRIVER
18651 SERIAL LOW-POWER INTER-CHIP MEDIA BUS (SLIMbus)
18809 SIFIVE FU540 SYSTEM-ON-CHIP