lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130815215004.GC4035@joshc.qualcomm.com>
Date:	Thu, 15 Aug 2013 16:50:05 -0500
From:	Josh Cartwright <joshc@...eaurora.org>
To:	Hanumant Singh <hanumant@...eaurora.org>
Cc:	Linus Walleij <linus.walleij@...aro.org>,
	Bjorn Andersson <bjorn@...o.se>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH] pinctrl: msm: Add support for MSM TLMM pinmux

On Thu, Aug 15, 2013 at 10:44:03AM -0700, Hanumant Singh wrote:
> On 8/14/2013 12:29 PM, Linus Walleij wrote:
> >On Tue, Jul 30, 2013 at 1:39 AM, Bjorn Andersson <bjorn@...o.se> wrote:
> >>On Wed, Jul 24, 2013 at 1:41 PM, Hanumant Singh <hanumant@...eaurora.org> wrote:
> >
> >>As a general note on the patch, the pins and pin groups are defined by
> >>the soc, I'm therefore not convinced that these should be configured
> >>from the devicetree. It's at least not how it's done in other
> >>platforms.
> >
> >Now we are three people sayin the same thing so it should
> >be a good hint to the implementer :-)
> >
> 
> Ok i can switch to using pin groups defined in per soc files.
> But in our case we have one soc going into different types of boards.
> (atleast 3). In each of the boards the same external devices end up using
> different pins. For ex camera on board 1 uses different pin group
> then the same camera on board 2. Both having the same SOC.
> So in this case the design would be to have all possible pin groups
> for different boards enumerated in the same soc-pinctrl.c file?
> 
> Also in this implementation I will have.
> 1) pinctrl-msm.c => DT parsing and interface to framework.
> 2) pinctrl-msm-tlmm<version>.c => Register programming and pin types
> supported by a particular TLMM pinmux version.

It isn't clear to me what you are trying to separate out between 1) and
2).  Seems like there should only be pinctrl-msm-tlmm<version>.c.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ