From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/9] ARM: tegra: pinmux: Tegra210 support
Date: Wed, 25 Feb 2015 20:44:07 -0700 [thread overview]
Message-ID: <54EE9687.9010706@wwwdotorg.org> (raw)
In-Reply-To: <CAPnjgZ0JE+v3O2C8AZFuD_H3yQYVX+iQQK5njvLJbuF-cc1_Cw@mail.gmail.com>
On 02/25/2015 05:54 PM, Simon Glass wrote:
> On 24 February 2015 at 17:06, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> On 02/24/2015 04:44 PM, Simon Glass wrote:
>>> On 24 February 2015 at 14:08, Stephen Warren <swarren@wwwdotorg.org>
>>> wrote:
>>>> This series performs a few small cleanups to or parameterizations of the
>>>> existing Tegra pinmux driver, and adds Tegra210 support. The Tegra210
>>>> code isn't actually used yet, since the balance of the Tegra210 support
>>>> is not yet present. However, it should start appearing soon.
...
>>>> Stephen Warren (9):
>>>> ARM: tegra: pinmux: add note re: drive group field defines
>>>> ARM: tegra: pinmux: simplify some defines
>>>> ARM: tegra: pinmux: handle feature removal on newer SoCs
>>>> ARM: tegra: pinmux: move some type definitions
>>>> ARM: tegra: pinmux: partially handle varying register layouts
>>>> ARM: tegra: pinmux: support hsm/schmitt on pins
>>>> ARM: tegra: pinmux: account for different drivegroup base registers
>>>> ARM: tegra: pinmux: support Tegra210's e_io_hv pin option
>>>> ARM: tegra: pinmux: add Tegra210 support
>>>
>>> Does the Linux side look similar to this? The use of #defines seem
>>> like a potential temporary solution but I hope it doesn't stay that
>>> way.
...
>> The Linux side was already a bit more parameterized, so the Tegra210 support
>> series doesn't have as many patches as the U-Boot series. However, that
>> comes at the cost of the per-SoC "drivers" having much larger data tables,
>> so I don't expect we'd want to adopt in U-Boot the same level of driver
>> parameterization as Linux.
>
> I see - do you know how much bigger the tables are?
Kernel per-SoC files:
text data bss dec hex filename
25532 1068 0 26600 67e8 pinctrl-tegra30.o
18744 1032 0 19776 4d40 pinctrl-tegra114.o
19868 1128 0 20996 5204 pinctrl-tegra124.o
16296 972 0 17268 4374 pinctrl-tegra210.o
U-Boot per-SoC files, although these could actually be reduced to zero
if we re-wrote the per-board pinmux tables to use FUNC0..3 enums (i.e.
raw HW register mux values) and hence got rid of the need to map a mux
enum to FUNC0..3 values. Auto-generation of the per-board files would
make pretty easy, if all boards were in tegra-pinmux-scripts.
text data bss dec hex filename
996 4 0 1000 3e8 .../tegra30/pinmux.o
1036 4 0 1040 410 .../tegra114/pinmux.o
1076 4 0 1080 438 .../tegra124/pinmux.o
next prev parent reply other threads:[~2015-02-26 3:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 21:08 [U-Boot] [PATCH 0/9] ARM: tegra: pinmux: Tegra210 support Stephen Warren
2015-02-24 21:08 ` [U-Boot] [PATCH 1/9] ARM: tegra: pinmux: add note re: drive group field defines Stephen Warren
2015-02-24 23:44 ` Simon Glass
2015-02-25 0:08 ` Stephen Warren
2015-02-26 0:55 ` Simon Glass
2015-02-24 21:08 ` [U-Boot] [PATCH 2/9] ARM: tegra: pinmux: simplify some defines Stephen Warren
2015-02-24 21:08 ` [U-Boot] [PATCH 3/9] ARM: tegra: pinmux: handle feature removal on newer SoCs Stephen Warren
2015-02-24 21:08 ` [U-Boot] [PATCH 4/9] ARM: tegra: pinmux: move some type definitions Stephen Warren
2015-02-24 21:08 ` [U-Boot] [PATCH 5/9] ARM: tegra: pinmux: partially handle varying register layouts Stephen Warren
2015-02-24 21:08 ` [U-Boot] [PATCH 6/9] ARM: tegra: pinmux: support hsm/schmitt on pins Stephen Warren
2015-02-24 21:08 ` [U-Boot] [PATCH 7/9] ARM: tegra: pinmux: account for different drivegroup base registers Stephen Warren
2015-02-24 21:08 ` [U-Boot] [PATCH 8/9] ARM: tegra: pinmux: support Tegra210's e_io_hv pin option Stephen Warren
2015-02-24 21:08 ` [U-Boot] [PATCH 9/9] ARM: tegra: pinmux: add Tegra210 support Stephen Warren
2015-02-24 23:44 ` [U-Boot] [PATCH 0/9] ARM: tegra: pinmux: " Simon Glass
2015-02-25 0:06 ` Stephen Warren
2015-02-26 0:54 ` Simon Glass
2015-02-26 3:44 ` Stephen Warren [this message]
2015-02-28 5:12 ` Simon Glass
2015-03-03 20:20 ` Stephen Warren
2015-03-03 20:58 ` Tom 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=54EE9687.9010706@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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