linux-kernel - Re: [RFC PATCH v2 0/4] pinctrl: imx: add pinnmux support

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: <CACRpkdbNOLBxsbAnnYSNiPaQ3EAj6eQ9=C8jJDb+jKP3GdjRcg@mail.gmail.com>
Date:	Wed, 14 Dec 2011 18:40:51 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Dong Aisheng <b29396@...escale.com>
Cc:	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linus.walleij@...ricsson.com, s.hauer@...gutronix.de,
	shawn.guo@...escale.com, kernel@...gutronix.de,
	grant.likely@...retlab.ca, rob.herring@...xeda.com
Subject: Re: [RFC PATCH v2 0/4] pinctrl: imx: add pinnmux support

On Wed, Dec 14, 2011 at 5:03 PM, Dong Aisheng <b29396@...escale.com> wrote:

> For DT support, there's still one issue that for pinmux_map,
> since it's board specific, i wonder if it can be parsed by pinctrl
> subsystem via dt rather than by each driver.

That is definately how it should be done. Seems like a good
idea to me.

> but pinctrl still does not supported that, i still only called
> it in mach-imx6q.c which seems not a correct place.

Don't worry that pinctrl does not support it - patch pinctrl core!

Just make a separate patch which patches drivers/pinctrl/pinmux.c
to ass the device tree parsing you need from the core, and we'll
review it.

I am by far too incompetent in device tree mechanisms to do
that myself, I have never worked much on device tree.

Thanks,
Linus Walleij
--
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/