[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151202161331.GE23396@atomide.com>
Date: Wed, 2 Dec 2015 08:13:31 -0800
From: Tony Lindgren <tony@...mide.com>
To: Matthijs van Duin <matthijsvanduin@...il.com>
Cc: lkml <linux-kernel@...r.kernel.org>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Brian Hutchinson <b.hutchman@...il.com>,
Delio Brignoli <dbrignoli@...ioscience.com>,
Neil Armstrong <narmstrong@...libre.com>,
Philipp Rosenberger <ilu@...utronix.de>
Subject: Re: [PATCH 10/10] ARM: dts: Fix dm814x pinctrl address and mask
* Matthijs van Duin <matthijsvanduin@...il.com> [151201 17:23]:
> On 2 December 2015 at 01:46, Tony Lindgren <tony@...mide.com> wrote:
> > We should probably have separate PIN_INPUT_3V3 and PIN_OUTPUT_3V3
> > dts macros that ensure that?
>
> I'm in general no fan of such macros: it feels really awkward to have
> to make that distinction in dts when doing pin config.
>
> Note that if you're feeling really enthausiastic about putting in
> effort to allow inputs to be disabled while staying clear of the
> erratum, I think you can detect at runtime which I/O supplies are 3.3V
> by inspecting this register:
>
> #define CTRL_CQDETECT_STATUS 0x48140e00
OK and if really needed needed the SoC revision information can be
passed to pinctrl-singl.c in it's platform_data that we already have
in addition to the dts configuration. And then pinctrl-single.c could
modify the mask based on IO voltage and SoC revision.
I think we're already covered as the boards can override the pinctrl
function-mask in the board specific dts file if really needed :)
Regards,
Tony
--
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