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] [RFC 2/2] sandbox: Update dts files
Date: Mon, 8 Jul 2019 08:15:43 -0400	[thread overview]
Message-ID: <20190708121543.GE8554@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ3hxqaP61YQDewZAXstqSnb34w2mgzTNcYZ5yOeJ_xjgg@mail.gmail.com>

On Sat, Jul 06, 2019 at 11:16:42AM -0600, Simon Glass wrote:
> Hi Tom,
> 
> On Wed, 26 Jun 2019 at 15:33, Tom Rini <trini@konsulko.com> wrote:
> >
> > With a more modern dtc we now get lots of warnings about problems with
> > the sandbox dts files and then in turn the DM tests.  Start addressing
> > these warnings by using, or not using in some cases, addresses on nodes
> > and update tests to match.
> >
> > Cc: Simon Glass <sjg@chromium.org>
> > Signed-off-by: Tom Rini <trini@konsulko.com>
> > ---
> > Please note that this is not enough.  A few tests are still failing for
> > the main test.dtb run and I don't see the obvious correction.  I also
> > largely left sandbox64 untouched but it too needs changes.
> > ---
> >  arch/sandbox/dts/sandbox.dts   | 22 ++++++++++----------
> >  arch/sandbox/dts/sandbox64.dts |  2 +-
> >  arch/sandbox/dts/test.dts      | 46 +++++++++++++++++++++---------------------
> >  include/sandbox-adc.h          |  2 +-
> >  test/dm/pmic.c                 |  2 +-
> >  test/dm/spmi.c                 |  2 +-
> >  6 files changed, 38 insertions(+), 38 deletions(-)
> 
> Thanks for looking at this. Note that dm/next has some updates so you
> should base on that (e.g. a common sandbox.dtsi).
> 
> I wonder what warnings you get with the simple 0/1/2 addresses?

Having more than one device at the same address is a warning about
duplicated addresses, I should have been clearer about that.

-- 
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/20190708/69f9229e/attachment.sig>

      reply	other threads:[~2019-07-08 12:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-26 21:33 [U-Boot] [RFC 1/2] scripts/dtc: Update to upstream version v1.4.7-57-gf267e674d145 Tom Rini
2019-06-26 21:33 ` [U-Boot] [RFC 2/2] sandbox: Update dts files Tom Rini
2019-07-06 17:16   ` Simon Glass
2019-07-08 12:15     ` Tom Rini [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=20190708121543.GE8554@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