From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Walleij Subject: Re: [RFC PATCH v3 3/5] pinctrl: imx: add pinctrl imx driver Date: Wed, 11 Jan 2012 10:28:43 +0100 Message-ID: References: <1324402840-32451-1-git-send-email-b29396@freescale.com> <1324402840-32451-4-git-send-email-b29396@freescale.com> <20120108130542.GC2203@richard-laptop> <20120109020848.GF1835@S2101-09.ap.freescale.net> <20120109021702.GV2414@b20223-02.ap.freescale.net> <20120109063136.GI1835@S2101-09.ap.freescale.net> <20120110083842.GA2414@b20223-02.ap.freescale.net> <20120110135147.GB26599@S2101-09.ap.freescale.net> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20120110135147.GB26599-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org Sender: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org To: Shawn Guo Cc: linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org, devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org, s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org, rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Richard Zhao , linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org, cjb-2X9k7bc8m7Mdnm+yROfE0A@public.gmane.org, Richard Zhao List-Id: devicetree@vger.kernel.org On Tue, Jan 10, 2012 at 2:51 PM, Shawn Guo wrote: > On Tue, Jan 10, 2012 at 11:43:28AM +0100, Linus Walleij wrote: >> 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. OK that's more or less what Stephen said too so I'm cooking a config table ala pinmux with string identifiers. >> 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. =A0(For example, I'm interested in pinctrl, but I do > not track LKML as close as I do for LAKML). True. I'll fix that. >> 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. I'll fix something, please review when it appears! Thanks, Linus Walleij