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
| ||
|
Date: Tue, 30 Jul 2013 18:08:10 -0600 From: Stephen Warren <swarren@...dotorg.org> To: Hanumant Singh <hanumant@...eaurora.org> CC: Linus Walleij <linus.walleij@...aro.org>, "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Bjorn Andersson <Bjorn.Andersson@...ymobile.com>, "Bird, Tim" <Tim.Bird@...ymobile.com>, ext Tony Lindgren <tony@...mide.com> Subject: Re: [PATCH] pinctrl: msm: Add support for MSM TLMM pinmux On 07/30/2013 06:01 PM, Hanumant Singh wrote: > On 7/30/2013 2:22 PM, Stephen Warren wrote: >> On 07/30/2013 03:10 PM, hanumant wrote: >> ... >>> We actually have the same TLMM pinmux used by several socs of a family. >>> The number of pins on each soc may vary. >>> Also a given soc gets used in a number of boards. >>> The device tree for a given soc is split into the different boards that >>> its in ie the boards inherit a common soc.dtsi but have separate dts. >>> The boards for the same soc may use different pin groups for >>> accomplishing a function, since we have multiple i2c, spi uart etc >>> peripheral instances on a soc. A different instance of each of the above >>> peripherals, can be used in different boards, utilizing different >>> or subset of same pin groups. >>> Thus I would need to have multiple C files for one soc, based on the >>> boards that it goes into. >> >> The pinctrl driver should be exposing the raw capabilities of the HW. >> All the board-specific configuration should be expressed in DT. So, the >> driver shouldn't have to know anything about different boards at >> compile-time. >> > I agree, so I wanted to keep the pin grouping information in DT, we > already have a board based differentiation of dts files in DT, for the > same soc. That's the opposite of what I was saying. Pin groups are a feature of the SoC design, not the board. -- 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