public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Stone <daniels-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
To: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [pinmux scripts PATCH] Update Nyan-Big pinmux from ChromeOS
Date: Mon, 9 Mar 2015 15:39:55 +0000 (UTC)	[thread overview]
Message-ID: <loom.20150309T163859-768@post.gmane.org> (raw)
In-Reply-To: 54FA1231.9000709@wwwdotorg.org

Hi Stephen,

Stephen Warren <swarren@...> writes:
> On 03/06/2015 01:42 PM, Simon Glass wrote:
> > On 6 March 2015 at 13:31, Stephen Warren <swarren@...> wrote:
> >> Can you comment on this change? If the data currently in
> >> tegra-pinmux-scripts is wrong, where did it come from if not the 
ChromeOS
> >> kernel?
> >
> > Sorry, I have no direct knowledge.
> 
> Oh, I see the answer in the patch description:

Thanks for looking at this.

> > commit 4a5373e4bd6477addd3764e25989f74d34eba8c6
> > Author: Simon Glass <sjg@...>
> > Date:   Tue Feb 3 11:29:03 2015 +0100
> >
> >     Add support for Nyan-big
> >
> >     Add support for Tegra124 Nyan-big. Pinmux is based on norrin with a 
single
> >     change for the reset GPIO.
> 
> The need for Daniel's patch seems like a good reason not to base one 
> board's pinmux on another board, assuming they're identical...

Indeed.

> Daniel, have you confirmed that 100% of the data in your patch matches 
> that used by the ChromeOS kernel, such that there shouldn't be any more 
> fixes needed down the line?

Actually, no, I hadn't. The diff is annoying to produce, as the format 
used in chromeos-3.10 is totally different (different pin naming 
scheme, aggregation of one entry to multiple nvidia,pins entries), but 
I managed to get a full diff with a blindingly horrible bit of Perl[0] 
(take chromeos-3.10 entries, map names -> numbers, map back from 
numbers to current upstream names, produce DT fragment), and then 
manually reconcile that back to tegra-pinmux-scripts to remove the 
delta.

There is only a small delta remaining between the two after manually 
harmonising these. First, the nvidia,lock property was set downstream 
but t-p-s doesn't seem to have any facility for handling this - is that 
a problem? Secondly, chromeos-3.10 used TEGRA_PIN_PULL_DOWN for rcv-sel 
being enabled, which just happened to map to 1 (ENABLED). And lastly, 
there are a number of entries in nyan-big.config which aren't present 
in the downstream config. If these entries are unneeded (presumably 
unused ... ?), should they be removed?

These patches are sitting in 
git://git.collabora.com/git/user/daniels/tegra-pinmux-scripts - I'll 
post them after myself & Tomeu have done some more testing on them, as 
there are a rather worrying amount of changes. I can do the same to 
Blaze as well, but that'll have to wait a couple of days as I don't 
actually have one on my desk.

Cheers,
Daniel

[0]: It really is horrible, and is only intended to be throwaway. 
http://people.collabora.com/~daniels/tmp/reconcile-downstream-dt.pl

  reply	other threads:[~2015-03-09 15:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-06 20:07 [PATCH] Update Nyan-Big pinmux from ChromeOS Daniel Stone
     [not found] ` <1425672435-19031-1-git-send-email-daniels-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2015-03-06 20:31   ` [pinmux scripts PATCH] " Stephen Warren
     [not found]     ` <54FA0EBB.3080208-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2015-03-06 20:42       ` Simon Glass
     [not found]         ` <CAPnjgZ0Uir9PZ1RWKCua0q0R6NMgGotqR7+jAkc_aJd1xTx4ew-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-06 20:46           ` Stephen Warren
2015-03-09 15:39             ` Daniel Stone [this message]
     [not found]             ` <1425915411.12254.0@mail.collabora.com>
     [not found]               ` <1425915411.12254.0-u1PCbA9B4pYthqhpMEQ9fNBPR1lH4CV8@public.gmane.org>
2015-03-09 16:23                 ` Stephen Warren
2015-03-09 16:40                   ` Daniel Stone
     [not found]                     ` <loom.20150309T173610-946-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2015-03-10 16:26                       ` Stephen Warren

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=loom.20150309T163859-768@post.gmane.org \
    --to=daniels-zgy8ohtn/8qb+jhodadfcq@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.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