From: Allen Martin <amartin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [tegra-pinmux-scripts] [PATCH] Add support for Norrin
Date: Mon, 4 Aug 2014 22:28:32 -0700 [thread overview]
Message-ID: <20140805052832.GA21844@nvidia.com> (raw)
In-Reply-To: <53DFD556.3010707-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
On Mon, Aug 04, 2014 at 11:47:50AM -0700, Stephen Warren wrote:
> On 08/04/2014 12:35 PM, Allen Martin wrote:
> > On Fri, Aug 01, 2014 at 12:45:21PM -0700, Stephen Warren wrote:
> >> On 07/31/2014 05:17 PM, Stephen Warren wrote:
> >>> On 07/31/2014 04:42 PM, Allen Martin wrote:
> >>>> Add support for Tegra124 Norrin FFD reference board (PM370). Pinmux
> >>>> is based on PM370_T124_customer_pinmux_1.1 spreadsheet.
> >>>
> >>> Oh good; I guess the Excel spreadsheet format was similar enough to
> >>> Jetson TK1 and Venice2 so no changes were required to
> >>> csv-to-board-tegra124-xlsx.py other than adding the board name. That's
> >>> good news:-)
> >>
> >> Oh, I see I have the changes below in my local tree from when I was
> >> fiddling with adding Norrin to tegra-pinmux-scripts. Are you sure you
> >> don't need those?
> >
> > Not any more, I filed a bug on the original pinmux spreadsheet because
> > it was more than just the GPIOs that were wrong, when that got fixed
> > the spreadsheet works fine without any of the other changes to the
> > script.
>
> Ah great! I've applied the patch upstream.
I just noticed some more errors in the checked in Excel spreadsheet.
I'm filing a bug on them now, but there will probably be another patch
when it gets fixed.
-Allen
nvpublic
next prev parent reply other threads:[~2014-08-05 5:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 22:42 [tegra-pinmux-scripts] [PATCH] Add support for Norrin Allen Martin
[not found] ` <1406846532-12611-1-git-send-email-amartin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-07-31 23:17 ` Stephen Warren
[not found] ` <53DACE72.2060602-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-08-01 19:45 ` Stephen Warren
[not found] ` <53DBEE51.1060102-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-08-04 18:35 ` Allen Martin
[not found] ` <20140804183544.GA30474-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-08-04 18:47 ` Stephen Warren
[not found] ` <53DFD556.3010707-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-08-05 5:28 ` Allen Martin [this message]
2014-08-04 19:02 ` Allen Martin
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=20140805052832.GA21844@nvidia.com \
--to=amartin-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@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).