From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH v2 05/13] tegra: dts: Bring in GPIO bindings from linux
Date: Tue, 13 May 2014 13:05:06 -0600 [thread overview]
Message-ID: <53726CE2.9040001@wwwdotorg.org> (raw)
In-Reply-To: <1399656509-28082-6-git-send-email-sjg@chromium.org>
On 05/09/2014 11:28 AM, Simon Glass wrote:
> These files are taken from Linux 3.14.
> diff --git a/arch/arm/dts/tegra124.dtsi b/arch/arm/dts/tegra124.dtsi
> - gpio: gpio at 6000d000 {
> + gpio: gpio at 0,6000d000 {
> compatible = "nvidia,tegra124-gpio", "nvidia,tegra30-gpio";
> - reg = <0x6000d000 0x1000>;
...
> + reg = <0x0 0x6000d000 0x0 0x1000>;
That reg value and node name are for #address-cells=<2>,
#size-cells=<2>. However, those properties are both =<1> in the U-Boot
tegra124.dtsi, and I'm not sure whether U-Boot even supports 64-bit DT
address values yet?
It'd probably be simplest to just use 32-bit address/size values in
tegra124.dtsi now, and import the conversion to 64-bit later?
Aside from that, this patch looks, so assuming the change to those two
lines above is reverted:
Acked-by: Stephen Warren <swarren@nvidia.com>
next prev parent reply other threads:[~2014-05-13 19:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 17:28 [U-Boot] [RFC PATCH v2 0/13] Enable driver model for GPIOs on Tegra Simon Glass
2014-05-09 17:28 ` [U-Boot] [RFC PATCH v2 01/13] Add an I/O tracing feature Simon Glass
2014-05-09 17:28 ` [U-Boot] [RFC PATCH v2 02/13] arm: Support iotrace feature Simon Glass
2014-05-09 17:28 ` [U-Boot] [RFC PATCH v2 03/13] sandbox: " Simon Glass
2014-05-13 4:46 ` Rommel G Custodio
2014-05-24 1:43 ` Simon Glass
2014-05-09 17:28 ` [U-Boot] [RFC PATCH v2 04/13] Makefile: Support include files for .dts files Simon Glass
2014-05-12 3:36 ` Masahiro Yamada
2014-05-13 19:01 ` Stephen Warren
2014-05-09 17:28 ` [U-Boot] [RFC PATCH v2 05/13] tegra: dts: Bring in GPIO bindings from linux Simon Glass
2014-05-13 19:05 ` Stephen Warren [this message]
2014-05-09 17:28 ` [U-Boot] [RFC PATCH v2 06/13] dm: Update README to encourage conversion to driver model Simon Glass
2014-05-09 17:28 ` [U-Boot] [RFC PATCH v2 07/13] dm: Use case-insensitive comparison for GPIO banks Simon Glass
2014-05-09 17:28 ` [U-Boot] [RFC PATCH v2 08/13] dm: Add missing header files in lists and root Simon Glass
2014-05-09 17:28 ` [U-Boot] [RFC PATCH v2 09/13] dm: Cast away the const-ness of the global_data pointer Simon Glass
2014-05-09 17:28 ` [U-Boot] [RFC PATCH v2 10/13] dm: Allow driver model tests only for sandbox Simon Glass
2014-05-09 17:28 ` [U-Boot] [RFC PATCH v2 11/13] dm: Fix printf() strings in the 'dm' command Simon Glass
2014-05-09 17:28 ` [U-Boot] [RFC PATCH v2 12/13] tegra: Enable driver model Simon Glass
2014-05-13 19:07 ` Stephen Warren
2014-05-09 17:28 ` [U-Boot] [RFC PATCH v2 13/13] tegra: Convert tegra GPIO driver to use " Simon Glass
2014-05-13 19:30 ` Stephen Warren
2014-05-22 1:25 ` Simon Glass
2014-05-09 17:31 ` [U-Boot] [RFC PATCH v2 0/13] Enable driver model for GPIOs on Tegra Simon Glass
-- strict thread matches above, loose matches on Subject: below --
2014-05-05 16:08 Simon Glass
2014-05-05 16:09 ` [U-Boot] [RFC PATCH v2 05/13] tegra: dts: Bring in GPIO bindings from linux Simon Glass
2014-05-05 16:57 ` Stephen Warren
2014-05-07 23:11 ` Simon Glass
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=53726CE2.9040001@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