mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org, Ladislav Michl <ladis@linux-mips.org>
Subject: Re: [PATCH] dts: Revert at91 switch to new PMC clock bindings
Date: Tue, 5 Feb 2019 15:37:08 +0100	[thread overview]
Message-ID: <20190205143708.GA28266@ravnborg.org> (raw)
In-Reply-To: <20190205115927.nyirklt3cz2lw6by@pengutronix.de>

Hi Sasha
> 
> dts/ contains a 1:1 copy from the upstream devicetree-rebasing
> repository. I can't apply any patches to this directory.
> 
> You would have to merge the changes to the changes to the corresponding
> files in arch/arm/dts. I'm not sure how feasible this is in this case
> since not only the clock nodes are changed, but also the references to
> the clocks.

The breakage was anticipated for my part, no suprise.
I just do not have time to look into it at the moment.

The objective for my part is to have all at91 boards moved over to DT,
so we will have to face this.

Or in other words patching all DT files in arch/arm/dts is
not IMO a feasible long term solution.

I got a new at91sam9gxx board from Microchip two weeks ago,
and that is my next DT target.
Then I hope we can maybe mass convert the rest of the
at91 baords with some limited testing.

But this clock issue will need to be fixed first.

	Sam

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2019-02-05 14:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04 10:29 Ladislav Michl
2019-02-05 11:59 ` Sascha Hauer
2019-02-05 13:24   ` Ladislav Michl
2019-02-05 14:37   ` Sam Ravnborg [this message]
2019-02-16 22:14 ` Sam Ravnborg
2019-02-17 16:25   ` Sam Ravnborg

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=20190205143708.GA28266@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=barebox@lists.infradead.org \
    --cc=ladis@linux-mips.org \
    --cc=s.hauer@pengutronix.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