Home
last modified time | relevance | path

Searched full:gpios (Results 1 – 25 of 498) sorted by relevance

12345678910>>...20

/linux-3.3/sound/soc/
Dsoc-jack.c292 * @gpios: array of gpio pins
298 struct snd_soc_jack_gpio *gpios) in snd_soc_jack_add_gpios() argument
303 if (!gpio_is_valid(gpios[i].gpio)) { in snd_soc_jack_add_gpios()
305 gpios[i].gpio); in snd_soc_jack_add_gpios()
309 if (!gpios[i].name) { in snd_soc_jack_add_gpios()
311 gpios[i].gpio); in snd_soc_jack_add_gpios()
316 ret = gpio_request(gpios[i].gpio, gpios[i].name); in snd_soc_jack_add_gpios()
320 ret = gpio_direction_input(gpios[i].gpio); in snd_soc_jack_add_gpios()
324 INIT_DELAYED_WORK(&gpios[i].work, gpio_work); in snd_soc_jack_add_gpios()
325 gpios[i].jack = jack; in snd_soc_jack_add_gpios()
[all …]
/linux-3.3/Documentation/
Dgpio.txt16 which GPIOs. Drivers can be written generically, so that board setup code
19 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
22 provide GPIOs; multifunction chips like power managers, and audio codecs
28 The exact capabilities of GPIOs vary between systems. Common options:
47 - Most GPIOs can be accessed while holding spinlocks, but those accessed
60 is not the main issue; GPIOs are often used for the kind of board-specific
90 Identifying GPIOs
92 GPIOs are identified by unsigned integers in the range 0..MAX_INT. That
104 So for example one platform uses numbers 32-159 for GPIOs; while another
108 use numbers 2000-2063 to identify GPIOs in a bank of I2C GPIO expanders.
[all …]
/linux-3.3/Documentation/devicetree/bindings/mmc/
Dnvidia-sdhci.txt12 - cd-gpios : Specify GPIOs for card detection
13 - wp-gpios : Specify GPIOs for write protection
14 - power-gpios : Specify GPIOs for power control
23 cd-gpios = <&gpio 69 0>; /* gpio PI5 */
24 wp-gpios = <&gpio 57 0>; /* gpio PH1 */
25 power-gpios = <&gpio 155 0>; /* gpio PT3 */
Dfsl-imx-esdhc.txt15 - cd-gpios : Specify GPIOs for card detection
16 - wp-gpios : Specify GPIOs for write protection
32 cd-gpios = <&gpio0 6 0>; /* GPIO1_6 */
33 wp-gpios = <&gpio0 5 0>; /* GPIO1_5 */
/linux-3.3/drivers/gpio/
DKconfig12 not depend on GPIOs being available, but rather let the user
20 for all their GPIOs, usually starting with ones integrated
45 These checks help ensure that GPIOs have been properly initialized
55 Say Y here to add a sysfs interface for GPIOs.
109 MPC512x/831x/834x/837x/8572/8610 GPIOs.
172 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
174 modes (S3 and higher). The remaining four GPIOs are powered by
175 the Intel SCH suspend power supply. These GPIOs remain
176 active during S3. The suspend powered GPIOs can be used to wake the
178 The Intel Tunnel Creek processor has 5 GPIOs powered by the
[all …]
/linux-3.3/arch/arm/boot/dts/
Dtegra-harmony.dts44 spkr-en-gpios = <&codec 2 0>;
45 hp-det-gpios = <&gpio 178 0>;
46 int-mic-en-gpios = <&gpio 184 0>;
47 ext-mic-en-gpios = <&gpio 185 0>;
75 cd-gpios = <&gpio 69 0>; /* gpio PI5 */
76 wp-gpios = <&gpio 57 0>; /* gpio PH1 */
77 power-gpios = <&gpio 155 0>; /* gpio PT3 */
85 cd-gpios = <&gpio 58 0>; /* gpio PH2 */
86 wp-gpios = <&gpio 59 0>; /* gpio PH3 */
87 power-gpios = <&gpio 70 0>; /* gpio PI6 */
Dimx53-qsb.dts32 cd-gpios = <&gpio3 13 0>;
37 cd-gpios = <&gpio3 11 0>;
38 wp-gpios = <&gpio3 12 0>;
87 phy-reset-gpios = <&gpio7 6 0>;
98 gpios = <&gpio1 8 0>;
105 gpios = <&gpio2 14 0>;
111 gpios = <&gpio2 15 0>;
121 gpios = <&gpio7 7 0>;
Dimx53-evk.dts32 cd-gpios = <&gpio3 13 0>;
33 wp-gpios = <&gpio3 14 0>;
39 cs-gpios = <&gpio2 30 0>, <&gpio3 19 0>;
63 cd-gpios = <&gpio3 11 0>;
64 wp-gpios = <&gpio3 12 0>;
104 phy-reset-gpios = <&gpio7 6 0>;
115 gpios = <&gpio7 7 0>;
Dimx53-ard.dts32 cd-gpios = <&gpio1 1 0>;
33 wp-gpios = <&gpio1 9 0>;
82 gpios = <&gpio5 10 0>;
89 gpios = <&gpio5 11 0>;
96 gpios = <&gpio5 12 0>;
103 gpios = <&gpio5 13 0>;
109 gpios = <&gpio4 0 0>;
Dexynos4210-origen.dts37 gpios = <&gpk2 0 2 0 3>,
50 gpios = <&gpk0 0 2 0 3>,
65 gpios = <&gpx2 0 0 0 2>;
71 gpios = <&gpx2 1 0 0 2>;
77 gpios = <&gpx1 7 0 0 2>;
83 gpios = <&gpx1 6 0 0 2>;
89 gpios = <&gpx1 5 0 0 2>;
Dimx6q-sabrelite.dts28 phy-reset-gpios = <&gpio3 23 0>;
33 cd-gpios = <&gpio7 0 0>;
34 wp-gpios = <&gpio7 1 0>;
39 cd-gpios = <&gpio2 6 0>;
40 wp-gpios = <&gpio2 7 0>;
Dtegra-seaboard.dts64 cd-gpios = <&gpio 69 0>; /* gpio PI5 */
65 wp-gpios = <&gpio 57 0>; /* gpio PH1 */
66 power-gpios = <&gpio 70 0>; /* gpio PI6 */
82 gpios = <&gpio 170 1>; /* gpio PV2, active low */
89 gpios = <&gpio 23 0>; /* gpio PC7 */
/linux-3.3/Documentation/devicetree/bindings/sound/
Dtegra-audio-wm8903.txt40 - nvidia,spkr-en-gpios : The GPIO that enables the speakers
41 - nvidia,hp-mute-gpios : The GPIO that mutes the headphones
42 - nvidia,hp-det-gpios : The GPIO that detect headphones are plugged in
43 - nvidia,int-mic-en-gpios : The GPIO that enables the internal microphone
44 - nvidia,ext-mic-en-gpios : The GPIO that enables the external microphone
66 nvidia,spkr-en-gpios = <&codec 2 0>;
67 nvidia,hp-det-gpios = <&gpio 178 0>; /* gpio PW2 */
68 nvidia,int-mic-en-gpios = <&gpio 184 0>; /*gpio PX0 */
69 nvidia,ext-mic-en-gpios = <&gpio 185 0>; /* gpio PX1 */
/linux-3.3/sound/soc/codecs/
Dwm1250-ev1.c32 struct gpio gpios[WM1250_EV1_NUM_GPIOS]; member
42 ena = wm1250->gpios[WM1250_EV1_GPIO_CLK_ENA].gpio; in wm1250_ev1_set_bias_level()
126 for (i = 0; i < ARRAY_SIZE(wm1250->gpios); i++) { in wm1250_ev1_pdata()
127 wm1250->gpios[i].gpio = pdata->gpios[i]; in wm1250_ev1_pdata()
128 wm1250->gpios[i].label = wm1250_gpio_names[i]; in wm1250_ev1_pdata()
129 wm1250->gpios[i].flags = GPIOF_OUT_INIT_LOW; in wm1250_ev1_pdata()
131 wm1250->gpios[WM1250_EV1_GPIO_CLK_SEL0].flags = GPIOF_OUT_INIT_HIGH; in wm1250_ev1_pdata()
132 wm1250->gpios[WM1250_EV1_GPIO_CLK_SEL1].flags = GPIOF_OUT_INIT_HIGH; in wm1250_ev1_pdata()
134 ret = gpio_request_array(wm1250->gpios, ARRAY_SIZE(wm1250->gpios)); in wm1250_ev1_pdata()
136 dev_err(&i2c->dev, "Failed to get GPIOs: %d\n", ret); in wm1250_ev1_pdata()
[all …]
/linux-3.3/Documentation/input/
Dgpio-tilt.txt1 Driver for tilt-switches connected via GPIOs
4 Generic driver to read data from tilt switches connected via gpios.
13 The array of struct gpio in the gpios field is used to list the gpios
31 one axis in 4 steps and emitts the current tilt via two GPIOs.
48 .gpios = (0 << 1) | (0 << 0),
53 .gpios = (0 << 1) | (1 << 0),
58 .gpios = (1 << 1) | (1 << 0),
63 .gpios = (1 << 1) | (0 << 0),
81 .gpios = sg060_tilt_gpios,
/linux-3.3/drivers/mmc/host/
Dof_mmc_spi.c42 int gpios[NUM_GPIOS]; member
57 bool value = gpio_get_value(oms->gpios[gpio_num]); in of_mmc_spi_read_gpio()
126 for (i = 0; i < ARRAY_SIZE(oms->gpios); i++) { in mmc_spi_get_pdata()
129 oms->gpios[i] = of_get_gpio_flags(np, i, &gpio_flags); in mmc_spi_get_pdata()
130 if (!gpio_is_valid(oms->gpios[i])) in mmc_spi_get_pdata()
133 ret = gpio_request(oms->gpios[i], dev_name(dev)); in mmc_spi_get_pdata()
135 oms->gpios[i] = -EINVAL; in mmc_spi_get_pdata()
143 if (gpio_is_valid(oms->gpios[CD_GPIO])) in mmc_spi_get_pdata()
145 if (gpio_is_valid(oms->gpios[WP_GPIO])) in mmc_spi_get_pdata()
174 for (i = 0; i < ARRAY_SIZE(oms->gpios); i++) { in mmc_spi_put_pdata()
[all …]
/linux-3.3/include/linux/input/
Dgpio_tilt.h22 * @gpios: bitfield of gpio target-states for the value
31 * from the gpios-array defined in gpio_regulator_config below.
34 int gpios; member
40 * @gpios: Array containing the gpios determining the tilt state
41 * @nr_gpios: Number of gpios
57 struct gpio *gpios; member
/linux-3.3/Documentation/devicetree/bindings/gpio/
Dgpio.txt4 1) gpios property
7 Nodes that makes use of GPIOs should specify them using one or more
16 GPIO properties should be named "[<name>-]gpios". Exact
17 meaning of each gpios property must be documented in the device tree
20 For example, the following could be used to describe gpios pins to use
33 chipsel-gpios = <&gpio1 12 0>,
47 Example of the node using GPIOs:
50 gpios = <&qe_pio_e 18 0>;
Dled.txt10 - gpios : Should specify the LED's GPIO, see "gpios property" in
37 gpios = <&mcu_pio 0 1>; /* Active low */
42 gpios = <&mcu_pio 1 0>;
51 gpios = <&mpc8572 6 0>;
55 gpios = <&mpc8572 7 0>;
/linux-3.3/include/linux/regulator/
Dgpio-regulator.h31 * @gpios: bitfield of gpio target-states for the value
37 * from the gpios-array defined in gpio_regulator_config below.
41 int gpios; member
56 * @gpios: Array containing the gpios needed to control
58 * @nr_gpios: Number of gpios
77 struct gpio *gpios; member
/linux-3.3/drivers/mtd/maps/
Dgpio-addr-flash.c5 * line and supplemented by GPIOs. This way you can hook up say a 8MiB flash
6 * to a 2MiB memory range and use the GPIOs to select a particular range.
38 * @gpio_count: number of GPIOs used to address
39 * @gpio_addrs: array of GPIOs to twiddle
41 * @win_size: dedicated memory size (if no GPIOs)
103 * will not cross a window size. This allows us to only wiggle the GPIOs once
193 struct resource *gpios; in gpio_flash_probe() local
198 gpios = platform_get_resource(pdev, IORESOURCE_IRQ, 0); in gpio_flash_probe()
200 if (!memory || !gpios || !gpios->end) in gpio_flash_probe()
203 arr_size = sizeof(int) * gpios->end; in gpio_flash_probe()
[all …]
/linux-3.3/drivers/regulator/
Dgpio-regulator.c45 struct gpio *gpios; member
98 if (data->states[ptr].gpios == data->state) in gpio_regulator_get_value()
114 target = data->states[ptr].gpios; in gpio_regulator_set_value()
121 gpio_set_value(data->gpios[ptr].gpio, state); in gpio_regulator_set_value()
190 drvdata->gpios = kmemdup(config->gpios, in gpio_regulator_probe()
193 if (drvdata->gpios == NULL) { in gpio_regulator_probe()
271 ret = gpio_request_array(drvdata->gpios, drvdata->nr_gpios); in gpio_regulator_probe()
274 "Could not obtain regulator setting GPIOs: %d\n", ret); in gpio_regulator_probe()
281 if (config->gpios[ptr].flags & GPIOF_OUT_INIT_HIGH) in gpio_regulator_probe()
299 gpio_free_array(drvdata->gpios, drvdata->nr_gpios); in gpio_regulator_probe()
[all …]
/linux-3.3/arch/mips/include/asm/mach-au1x00/
Dgpio.h17 /* On Au1000, Au1500 and Au1100 GPIOs won't work as inputs before
19 * register enables use of GPIOs as wake source.
31 * 4 use cases of Alchemy GPIOS:
35 * A gpiochip for the 75 GPIOs is registered.
42 * Au1300 gpios only by using the numbers straight out of the data-
46 * GPIO namespace and -operations (i.e. for example you have 8 GPIOs
69 /* using gpiolib to provide up to 2 gpio_chips for on-chip gpios */
/linux-3.3/Documentation/devicetree/bindings/input/
Dsamsung-keypad.txt28 - row-gpios: List of gpios used as row lines. The gpio specifier for
32 - col-gpios: List of gpios used as column lines. The gpio specifier for
59 row-gpios = <&gpx2 0 3 3 0
62 col-gpios = <&gpx1 0 3 0 0
/linux-3.3/drivers/of/
Dgpio.c44 pr_debug("%s: can't parse gpios property\n", __func__); in of_get_named_gpio_flags()
81 * of_gpio_count - Count GPIOs for a device
82 * @np: device node to count GPIOs for
84 * The function returns the count of GPIOs specified for a node.
88 * gpios = <0
93 * defines four GPIOs (so this function will return 4), two of which
103 ret = of_parse_phandle_with_args(np, "gpios", "#gpio-cells", in of_gpio_count()
105 /* A hole in the gpios = <> counts anyway. */ in of_gpio_count()
169 * to manage GPIOs from the callbacks.

12345678910>>...20