mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Ladislav Michl <ladis@linux-mips.org>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH v2 0/9] at91: Support PMC clock bindings
Date: Sun, 17 Feb 2019 22:53:47 +0100	[thread overview]
Message-ID: <20190217215347.GA12408@ravnborg.org> (raw)
In-Reply-To: <20190217213255.GA5986@lenoch>

Hi Ladislav

On Sun, Feb 17, 2019 at 10:32:55PM +0100, Ladislav Michl wrote:
> Hi Sam,
> 
> On Sun, Feb 17, 2019 at 07:44:15PM +0100, Sam Ravnborg wrote:
> > Hi all.
> > 
> > > Sam Ravnborg (9):
> > >       clocksource: Do not mix depends and select for ATMEL_PIT
> > >       arm: at91: fix at91_configure_usart6 warning
> > >       arm: at91: add SOC_SAMA5{D3,D4}
> > >       clk: at91: add at91sam9260
> > >       clk: at91: add at91sam9rl
> > >       clk: at91: add at91sam9x5
> > >       clk: at91: add sama5d2
> > 
> > >       clk: at91: add sama5d4
> > This patch is bogus, fails to build.
> > 
> > >       clk: at91: update to new bindings
> > Likewise, at least part of it.
> 
> Well, it builds for at91sam9260 (at91sam9g20) and is runtime tested now.
> So for that configuration here is my
> Tested-by: Ladislav Michl <ladis@linux-mips.org>
Thanks, very good to know it works for others.

The build failure started when I pulled in clk-h32mx and sama5d4.
They are not used by SAM9 so you are safe.

> Besides, current master plus your patches is about 1,3kB bigger, so
> it does not fit Dataflash anymore, but that is separate issue to solve :)
The current patch pulls in at91sam9260 + at91sam9rl + at91sam9x5
for the SAM9 targets. This is like done in the kernel today.
We may have to look at splitting this up.

The patchset also enabled some clocks that was not enabled before.
Maybe we can avoid them as they may not be required in the bootloader.
This is also something inherited from the kernel.

	Sam

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

  reply	other threads:[~2019-02-17 21:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-17 16:16 Sam Ravnborg
2019-02-17 16:16 ` [PATCH v2 1/9] clocksource: Do not mix depends and select for ATMEL_PIT Sam Ravnborg
2019-02-17 16:16 ` [PATCH v2 2/9] arm: at91: fix at91_configure_usart6 warning Sam Ravnborg
2019-02-17 16:16 ` [PATCH v2 3/9] arm: at91: add SOC_SAMA5{D3,D4} Sam Ravnborg
2019-02-17 16:16 ` [PATCH v2 4/9] clk: at91: add at91sam9260 Sam Ravnborg
2019-02-17 16:16 ` [PATCH v2 5/9] clk: at91: add at91sam9rl Sam Ravnborg
2019-02-17 16:16 ` [PATCH v2 6/9] clk: at91: add at91sam9x5 Sam Ravnborg
2019-02-17 16:16 ` [PATCH v2 7/9] clk: at91: add sama5d2 Sam Ravnborg
2019-02-17 16:16 ` [PATCH v2 8/9] clk: at91: add sama5d4 Sam Ravnborg
2019-02-17 16:16 ` [PATCH v2 9/9] clk: at91: update to new bindings Sam Ravnborg
2019-02-17 18:44 ` [PATCH v2 0/9] at91: Support PMC clock bindings Sam Ravnborg
2019-02-17 21:32   ` Ladislav Michl
2019-02-17 21:53     ` Sam Ravnborg [this message]
2019-02-18  8:10 ` Sascha Hauer
2019-02-18 19:59   ` Sam Ravnborg
2019-02-19  9:05     ` Sascha Hauer
2019-02-19 10:01       ` Sam Ravnborg
2019-02-19 10:53         ` Sascha Hauer
2019-02-19 10:05       ` Ladislav Michl

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=20190217215347.GA12408@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=barebox@lists.infradead.org \
    --cc=ladis@linux-mips.org \
    /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