[lkml]   [2011]   [Aug]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [RFC PATCH v2 00/13] arm/tegra: Initialize GPIO & pinmux from DT
    On Tue, Aug 16, 2011 at 7:12 PM, Stephen Warren <> wrote:

    > One issue here: There isn't always a single gpio/pinmux parent; as a
    > concrete example, the ALSA/ASoC driver for Tegra+WM8903 uses GPIOs both
    > from Tegra itself, and from the WM8903 audio codec.

    The Ux500 have pinmuxing on the DB8500 and AB8500 - the latter
    is a PMIC (&misc) connected to the DB8500 via I2C.

    In the pincontrol subsystem I'm brewing, each of these will have
    their own pin controller instance and their own struct gpio_chip as
    well, so:

    DB8500: pinctrl.0, gpio.0
    AB8500: pinctrl.1, gpio.1

    Each GPIO chip may have it's respective pin controller as parent
    I guess, or they may simply be the same struct device * whatdoIknow.

    I know this is vaporware, but does this reasoning hold also to
    the Tegra+WM8903 combo?

    Linus Walleij

     \ /
      Last update: 2011-08-23 14:53    [W:0.018 / U:138.760 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site