[lkml]   [2012]   [Jan]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [RFC PATCH v3 3/5] pinctrl: imx: add pinctrl imx driver
    On Tue, Jan 10, 2012 at 11:43:28AM +0100, Linus Walleij wrote:
    > On Tue, Jan 10, 2012 at 9:38 AM, Richard Zhao
    > <> wrote:
    > > On Mon, Jan 09, 2012 at 02:32:12PM +0800, Shawn Guo wrote:
    > >> As I was educated by Linus.W, we can not drink ocean and we need to
    > >> split big chunk of work into pieces and achieve it step by step.
    > > Sure, we can not drink out the ocean :). But if people can not use it
    > > in real case, how do we verify the driver? How do we know the driver
    > > goes in the right way?
    > If you prefer to do a big upfront design of the entire driver then please
    > by all means do that.
    > What we need to know right now is what you need from the pin
    > controller core to do that. We have a (custom) pinconf API now,
    > does it fit the bill?
    Hmm, I do not think it fits right away, as I do not think it's sensible
    to have pinctrl client drivers call pin_config_set() directly.

    > I have spent some time on generic pin config, it was not much
    > commented so if it helps you please ACK the patches.
    Since the ARM community is the one who is most interested in pinctrl
    subsystem so far, I guess copying LAKML will help collect more comments
    and various tags. (For example, I'm interested in pinctrl, but I do
    not track LKML as close as I do for LAKML).

    > Next from discussions with Stpehen I've sort of figured out that
    > we need a config mapping table of sorts and then a means to activate
    > entries of that table at runtime. I'm trying to come up with something
    > for this.
    That's something we are waiting for pinconf being usable for imx.


     \ /
      Last update: 2012-01-10 14:43    [W:2.564 / U:0.876 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site