From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: tegra: remove pinmux setup from Tegra124 boards
Date: Thu, 14 Aug 2014 10:26:00 +0200 [thread overview]
Message-ID: <1408004760.4649.11.camel@weser.hi.pengutronix.de> (raw)
In-Reply-To: <53EB91D4.8050402@wwwdotorg.org>
Am Mittwoch, den 13.08.2014, 10:27 -0600 schrieb Stephen Warren:
> On 08/13/2014 03:19 AM, Lucas Stach wrote:
> > Hi Stephen,
> >
> > sorry for getting on this late, I completely missed this and only now
> > stumbled upon this.
> >
> > I'm not really fond of this change. The barebox bootloader completely
> > probes itself from DT, including the pinmux. We try to stay as close as
> > possible to the upstream kernel DTs and only introduce minimal changes.
> > Removing the pinmux from the DTS will completely break barebox, as we
> > don't have any static pinmux tables there.
>
> Probing bootloaders from DT seems like a huge mistake to me, but that's
> probably a separate discussion.
>
Bringing DT into the bootloader was one the single most important
things for productivity we ever did.
On i.MX (the best supported arch in Barebox) it has brought down bringup
time for boards already supported by Linux to a few hours and enables us
to share effort spent for bootloader development on new boards with
later Linux development. Writing a single DT description for the
hardware to bring up the bootloader greatly reduces the time needed to
bring up Linux later on.
> The pinmux generator scripts spit out DT, so you can easily generate a
> DT representation of the board pinmux, and add that to the DT file in
> Barebox. See https://github.com/NVIDIA/tegra-pinmux-scripts.
>
I could do that, but...
> > In order to not break the bootloader use-case I strongly advocate to
> > keep the static pinmux in the DT. Can't we just rename the the state to
> > something like "initial", so Linux won't try to set it by default?
>
> That doesn't seem like a good idea. There's no reason for the DT to
> contain data that we know has no use.
>
Just because the DTS are still located in the kernel tree doesn't mean
the kernel is the only user. DT is meant to be a hardware description.
IMHO knowing that the kernel isn't using some information contained in
there is no argument for omitting the info.
Regards,
Lucas
--
Pengutronix e.K. | Lucas Stach |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2014-08-14 8:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 22:45 [PATCH] ARM: tegra: remove pinmux setup from Tegra124 boards Stephen Warren
2014-08-13 9:19 ` Lucas Stach
2014-08-13 16:27 ` Stephen Warren
2014-08-14 8:26 ` Lucas Stach [this message]
2014-08-18 16:34 ` Stephen Warren
2014-08-29 6:53 ` Linus Walleij
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=1408004760.4649.11.camel@weser.hi.pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).