From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: Benoit Cousson <benoit.cousson@linaro.org>
Cc: Tony Lindgren <tony@atomide.com>,
Enric Balletbo <eballetbo@gmail.com>,
Ezequiel Garcia <elezegarcia@gmail.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: dts: AM33XX: node definition cleanups
Date: Sat, 10 Aug 2013 19:05:09 +0200 [thread overview]
Message-ID: <1376154311-10184-1-git-send-email-javier.martinez@collabora.co.uk> (raw)
Hi,
While reviewing the submission of a DT file for a new board
based on the am3352 SoC, I noticed that am33xx*.dts files needed
some cleanups. All am33xx based board files redefine device nodes
that are already defined in the included am33xx.dtsi file.
This not only makes the DTS harder to maintain without any benefit
but also leaks SoC internal details to board files such as how the
OCP interconnect is modeled (currently just a flat representation)
and the addresses of some IP modules that are part of the SoC and
are not going to change from board to board.
This patch-set cleans these board files and is composed of the
following patches:
[PATCH 1/2] ARM: dts: AM33XX: use pinmux node defined in included
[PATCH 2/2] ARM: dts: AM33XX: don't redefine OCP bus and device
NOTE: I don't own any of these am33xx based boards so I was only
able to build test the changes. However I compared the generated
dtb before and after the changes and the disassembled DTS with
dtc -I dtb -O dts foo.dtb > bar.dts are identical.
Even though the binary dtb is the same and there shouldn't be
any visible changes, boot testing will be highly appreciated.
Thanks a lot and best regards,
Javier
next reply other threads:[~2013-08-10 17:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-10 17:05 Javier Martinez Canillas [this message]
2013-08-10 17:05 ` [PATCH 1/2] ARM: dts: AM33XX: use pinmux node defined in included file Javier Martinez Canillas
2013-08-10 17:05 ` [PATCH 2/2] ARM: dts: AM33XX: don't redefine OCP bus and device nodes Javier Martinez Canillas
2013-08-13 11:45 ` [PATCH 0/2] ARM: dts: AM33XX: node definition cleanups Benoit Cousson
2013-08-14 10:21 ` Mohammed, Afzal
2013-08-16 9:25 ` Rajendra Nayak
2013-08-16 10:47 ` Benoit Cousson
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=1376154311-10184-1-git-send-email-javier.martinez@collabora.co.uk \
--to=javier.martinez@collabora.co.uk \
--cc=benoit.cousson@linaro.org \
--cc=eballetbo@gmail.com \
--cc=elezegarcia@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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