From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: [pinmux scripts PATCH] Support Tegra210
Date: Mon, 09 Mar 2015 10:06:19 -0600 [thread overview]
Message-ID: <54FDC4FB.6000000@wwwdotorg.org> (raw)
In-Reply-To: <1424810874-21783-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
On 02/24/2015 01:47 PM, Stephen Warren wrote:
> From: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>
> Tegra210 changes the pinmux HW in a few ways; at least:
>
> - The set of drive groups is much more 1:1 with the set of pins. Most
> pins have an associated drive group register as well as an associated
> pinmux register, and most drive groups cover a single pin.
> - Some register fields have moved from the drive group registers into
> the pinmux registers.
> - The set of available options for each pin and group varies relative to
> previous chips, and hence the register layouts vary a bit too.
>
> This patch updates tegra-pinmux-scripts minimally to handle these
> changes, to a level equivalent to the support for previous chips. For
> example, some new options such as per-pin schmitt aren't handled since
> the syseng-supplied pinmux spreadsheets don't provide a value for this
> option.
>
> csv-to-board-tegra124-xlsx.py is renamed to csv-to-board.py since it now
> supports boards using different SoCs, and it's not worth encoding all
> supported SoCs in the filename (Tegra30/114 aren't supported by it, hence
> the previous naming).
Both the U-Boot and Linux kernel SoC drivers that this patch generates
are now checked in to those project. Hence, I've applied this.
prev parent reply other threads:[~2015-03-09 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 20:47 [pinmux scripts PATCH] Support Tegra210 Stephen Warren
[not found] ` <1424810874-21783-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2015-03-09 16:06 ` Stephen Warren [this message]
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=54FDC4FB.6000000@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@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).