From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Lucas Stach <dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH tegra-pinmux-scripts 2/2] add support for Beaver board
Date: Fri, 09 Jan 2015 10:16:19 -0700 [thread overview]
Message-ID: <54B00CE3.1060309@wwwdotorg.org> (raw)
In-Reply-To: <1420494447-18510-2-git-send-email-dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
On 01/05/2015 02:47 PM, Lucas Stach wrote:
> This leaves some pins unconfigured, but is all I could work out
> from the existing U-Boot and Kernel code/DTs.
I've applied the series. I added a note to the top of beaver.board:
> # Note that this data was reverse-engineered from current upstream SW; it is
> # not a complete error-checked NVIDIA-supplied data set. That doesn't mean
> # anything is wrong with the data, simply that it was not generated using the
> # normal flow for NVIDIA reference boards (auto-generation from spreadsheets
> # supplied by NVIDIA syseng).
I hope that's OK.
One thing that might be worth doing: Boot the system you have, test that
everything works, then fill in all the missing pins/values based on the
actual register settings in HW (and cross-check the others with what's
already in this file). At least that would eliminate the warnings from
./board-to-*.py re: some pins being unconfigured, without changing
anything about the way the pinmux ends up being programmed.
next prev parent reply other threads:[~2015-01-09 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 21:47 [PATCH tegra-pinmux-scripts 1/2] fix kernel dt generation for Tegra 3 Lucas Stach
[not found] ` <1420494447-18510-1-git-send-email-dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
2015-01-05 21:47 ` [PATCH tegra-pinmux-scripts 2/2] add support for Beaver board Lucas Stach
[not found] ` <1420494447-18510-2-git-send-email-dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
2015-01-09 17:16 ` Stephen Warren [this message]
2015-01-05 22:07 ` [PATCH tegra-pinmux-scripts 1/2] fix kernel dt generation for Tegra 3 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=54B00CE3.1060309@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=dev-8ppwABl0HbeELgA04lAiVw@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;
as well as URLs for NNTP newsgroup(s).