public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: dts: am33xx: Sync dts with Linux 4.20.0
Date: Wed, 5 Dec 2018 20:32:00 -0500	[thread overview]
Message-ID: <20181206013200.GR32109@bill-the-cat> (raw)
In-Reply-To: <20181205135342.4388-1-fb@ltec.ch>

On Wed, Dec 05, 2018 at 02:53:42PM +0100, Felix Brack wrote:

> This patch synchronizes the am33xx SoC specific files with those from
> Linux 4.20.0. Hence all board maintainers of am33xx based boards are
> on the cc list.
> The main purpose of this patch is to prevent further diverging of the
> dts files from U-Boot and those from Linux. It aims to set the stage
> for the synchronization of board specific dts files. Example: I'm the
> maintainer of the PDU001 board: once this patch is applied successfully
> I will make changes to the board specific dts file in Linux only and
> then post a patch with a copy of this exact dts file to U-Boot. This
> will make U-Boot and Linux remain in sync.
> The stumbling block of https://patchwork.ozlabs.org/patch/943627 was
> removed by the patch https://patchwork.ozlabs.org/patch/962428 from
> Lokesh Vutla (many thanks!). This omap-serial driver allows using the
> Linux am33xx.dtsi file in U-Boot.
> Other changes to dts and dtsi files made by this patch are mainly to
> prevent _new_ warnings during the build process. Especially the warning
> at pinmux at 800 stating 'unnecessary #address-cells/#size-cells without
> "ranges" or child "reg"' was not removed. This warning is a good example
> showing the benefit of the synchronization: if it needs to be fixed it
> will be fixed in Linux and ported back to U-Boot.
> Buildman reports all 46 am33xx SoC based boards to build fine, with
> warnings of course. Nevertheless this patch should be tested thoroughly
> on as many boards as possible to prevent any collateral damage.
> 
> Signed-off-by: Felix Brack <fb@ltec.ch>

Reviewed-by: Tom Rini <trini@konsulko.com>

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20181205/e8596088/attachment.sig>

  reply	other threads:[~2018-12-06  1:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-05 13:53 [U-Boot] [PATCH] arm: dts: am33xx: Sync dts with Linux 4.20.0 Felix Brack
2018-12-06  1:32 ` Tom Rini [this message]
2018-12-07 20:35 ` [U-Boot] " Tom Rini

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=20181206013200.GR32109@bill-the-cat \
    --to=trini@konsulko.com \
    --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