From: Shawn Guo <shawn.guo@linaro.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: "Vincent Stehlé" <vincent.stehle@freescale.com>,
"Sascha Hauer" <kernel@pengutronix.de>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ARM: dts: imx6qdl-sabresd.dtsi: Add red led
Date: Thu, 6 Mar 2014 10:05:16 +0800 [thread overview]
Message-ID: <20140306020514.GC11366@S2101-09.ap.freescale.net> (raw)
In-Reply-To: <20140305193925.GY21483@n2100.arm.linux.org.uk>
On Wed, Mar 05, 2014 at 07:39:26PM +0000, Russell King - ARM Linux wrote:
> On Wed, Mar 05, 2014 at 07:42:28PM +0800, Shawn Guo wrote:
> > It's not a hog pin, so shouldn't be added here. (Right, most of the
> > existing pins shouldn't be here from the beginning)
>
> On the subject of that kind of thing... I have an issue with the existing
> pinmux stuff. This is a wider issue than your discussion above...
>
> I regard the idea of requiring the pinmux to be configured as part of
> the driver probe a rather broken concept - yes, it makes sense in some
> scenarios, but for the vast majority of cases, it doesn't.
>From what I've seen, it's the opposite - the concept works for the
majority, and only some scenarios needs special handling.
>
> Let's take an example. A pin is wired to a SPDIF transceiver. The
> out-of-reset SoC configuration results in the pin turning the LED on
> in the SPDIF transceiver.
>
> With the way stuff is setup, with the driver having the pinmux settings
> for itself, the point at which that pin gets configured is when the
> driver loads, which may be a module - so that can happen quite late in
> the boot sequence. A failure to boot can result in it not happening at
> all.
>
> So, this brings up the obvious question: is this proper behaviour of the
> hardware, or is this something we should do better with - such as where
> we know what the settings should be for a platform, and these settings
> never change, we arrange for that to happen at kernel boot time as a
> once-off.
>
> For example, in the above case, we know it's board XYZ, we know that this
> pin is connected to the SPDIF transceiver, so maybe we should configure
> it early on in the boot sequence whether or not the driver has been
> configured and/or loaded.
For such special case, I'm fine with using hog group to handle it. But
IMO, bootloader is even a better place to correct such unreasonable
out-of-reset SoC configuration for particular board.
Shawn
next prev parent reply other threads:[~2014-03-06 2:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1393943685-32579-1-git-send-email-vincent.stehle@freescale.com>
2014-03-05 6:22 ` [PATCH] ARM: dts: imx6qdl-sabresd.dtsi: Add heartbeat led Shawn Guo
[not found] ` <1394007383-21874-1-git-send-email-vincent.stehle@freescale.com>
2014-03-05 11:42 ` [PATCH v2] ARM: dts: imx6qdl-sabresd.dtsi: Add red led Shawn Guo
2014-03-05 19:39 ` Russell King - ARM Linux
2014-03-06 2:05 ` Shawn Guo [this message]
2014-03-06 10:13 ` Sascha Hauer
[not found] ` <1394045919-1375-1-git-send-email-vincent.stehle@freescale.com>
2014-03-06 2:39 ` [PATCH v3] " Shawn Guo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140306020514.GC11366@S2101-09.ap.freescale.net \
--to=shawn.guo@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=vincent.stehle@freescale.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®