From: Stephan Gerhold <stephan@gerhold.net>
To: u-boot@lists.denx.de
Subject: [RFC PATCH 0/5] arm: Restore minimal support for ST-Ericsson U8500 SoC
Date: Thu, 23 Jan 2020 18:56:10 +0100 [thread overview]
Message-ID: <20200123175610.GA922@gerhold.net> (raw)
In-Reply-To: <20200122180350.GK26536@bill-the-cat>
On Wed, Jan 22, 2020 at 01:03:50PM -0500, Tom Rini wrote:
> On Wed, Jan 22, 2020 at 05:47:07PM +0100, Stephan Gerhold wrote:
> > Hi Tom,
> >
> > On Sat, Jan 04, 2020 at 06:45:14PM +0100, Stephan Gerhold wrote:
> > > This patch series restores minimal U-Boot support for
> > > the ST-Ericsson NovaThor U8500 SoC.
> > >
> > > Previous support for U8500 was removed in
> > > commit 68282f55b846 ("arm: Remove unused ST-Ericsson u8500 arch")
> > > since none of the boards were converted to generic boards
> > > before the deadline.
> > >
> > > The motivation for adding the SoC and board is explained in
> > > - Patch 3 ("arm: Add support for ST-Ericsson U8500 SoC") and
> > > - Patch 5 ("board: Add new Samsung "stemmy" board based on ST-Ericsson U8500")
> > >
> > > I have additional patches for MMC, USB, display and the "stemmy"
> > > board, that configure it to provide an Android fastboot interface
> > > with similar functionality as the original Samsung bootloader.
> > > Some of the patches require some additional work, so I thought
> > > it is easier to start with some minimal changes first (only UART).
> > >
> > > I think this makes the patch series quite straightforward,
> > > with only ~225 new lines of C code, plus device tree and documentation.
> > > The only patch that stands out with ~1.8k lines is the device tree
> > > import, directly copied (without modification) from the Linux kernel.
> > >
> >
> > Since we are approaching the end of the merge window,
> > I was wondering if there is anything I can do to get this patch set
> > applied for v2020.04?
>
> Since you had marked it as RFC, I had marked it as such in patchwork and
> overlooked it. I'll take a look soon, thanks.
Thank you! I thought marking it as RFC is appropriate since I'm adding a
new SoC and this is my first U-Boot patch. But it is working fine,
so unless there are comments it should be good to go :)
Thanks,
Stephan
prev parent reply other threads:[~2020-01-23 17:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 17:45 [RFC PATCH 0/5] arm: Restore minimal support for ST-Ericsson U8500 SoC Stephan Gerhold
2020-01-04 17:45 ` [RFC PATCH 1/5] timer: Add driver for Nomadik Multi Timer Unit (MTU) Stephan Gerhold
2020-01-06 1:48 ` Linus Walleij
2020-01-23 21:58 ` Tom Rini
2020-01-04 17:45 ` [RFC PATCH 2/5] arm: dts: Import device tree for ST-Ericsson Ux500 Stephan Gerhold
2020-01-06 1:48 ` Linus Walleij
2020-01-23 21:58 ` Tom Rini
2020-01-04 17:45 ` [RFC PATCH 3/5] arm: Add support for ST-Ericsson U8500 SoC Stephan Gerhold
2020-01-06 1:49 ` Linus Walleij
2020-01-23 21:58 ` Tom Rini
2020-01-04 17:45 ` [RFC PATCH 4/5] MAINTAINERS: Add ARM U8500 Stephan Gerhold
2020-01-06 1:50 ` Linus Walleij
2020-01-23 21:58 ` Tom Rini
2020-01-04 17:45 ` [RFC PATCH 5/5] board: Add new Samsung "stemmy" board based on ST-Ericsson U8500 Stephan Gerhold
2020-01-06 1:50 ` Linus Walleij
2020-01-23 21:58 ` Tom Rini
2020-01-22 16:47 ` [RFC PATCH 0/5] arm: Restore minimal support for ST-Ericsson U8500 SoC Stephan Gerhold
2020-01-22 18:03 ` Tom Rini
2020-01-23 17:56 ` Stephan Gerhold [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=20200123175610.GA922@gerhold.net \
--to=stephan@gerhold.net \
--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