From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Where should Renesas RZ/A go under arch/arm/ ????
Date: Tue, 31 Oct 2017 22:09:41 -0400 [thread overview]
Message-ID: <20171101020941.GM4635@bill-the-cat> (raw)
In-Reply-To: <SG2PR06MB1165FBE5701BC48AF13DE3928A5E0@SG2PR06MB1165.apcprd06.prod.outlook.com>
On Tue, Oct 31, 2017 at 03:26:02PM +0000, Chris Brandt wrote:
> Hi Tom,
>
> Thanks for the reply!
>
> On Tuesday, October 31, 2017 1, Tom Rini wrote:
> > On Tue, Oct 31, 2017 at 12:13:22PM +0000, Chris Brandt wrote:
> > > Hello,
> > >
> > > Since I've been supporting a u-boot for the Renesas RZ/A1 SoC for a
> > > while now, I thought I'd start upstreaming the drivers/patches I've
> > acquired
> > > over the years.
> > >
> > > But, where should the core files and Kconfig go?
> > >
> > > The RZ/A1 series has a Cortex-A9.
> > >
> > > At first, I had made a directory under arch/arm/cpu/armv7/
> > >
> > > But, now I see things are moving under arch/arm/mach-xxxx.
> > >
> > > There is a arch/arm/mach-rmobile directory that has the Renesas R-Car
> > > devices. But while the RZ/A1 uses some of the same HW IP blocks, for the
> > > most part it's a different product line.
> > >
> > > So, Where should I put my RZ/A1 (and future RZ/A devices, or future RZ/N
> > > devices)?
> > >
> > > 1. Keep all Renesas parts together like we do in the kernel (arm/mach-
> > shmobile)?
> > >
> > > u-boot/arch/arm/mach-rmobile
> >
> > I would vote for renaming and matching the kernel here and using
> > mach-shmobile. Thanks!
>
>
> Ugh! That shmobile name is going to haunt us forever (even though we
> don't even make SH-Mobile parts anymore....and they are all ARM cores now,
> not SH).
>
> I will say that upstream in the kernel, most everything else has been
> renamed to "renesas" (ie, ARCH_RENESAS, )...except that directory name. I
> asked if/when they would rename it, but at the moment, there is not plan
> as not to break anything.
>
> Maybe we can compromise on everything in mach-renesas??
OK, I can go with mach-renesas, thanks again!
--
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/20171031/9bdecc4f/attachment.sig>
next prev parent reply other threads:[~2017-11-01 2:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 12:13 [U-Boot] Where should Renesas RZ/A go under arch/arm/ ???? Chris Brandt
2017-10-31 15:14 ` Tom Rini
2017-10-31 15:26 ` Chris Brandt
2017-11-01 2:09 ` Tom Rini [this message]
2017-11-13 1:02 ` Nobuhiro Iwamatsu
2017-11-13 15:07 ` Chris Brandt
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=20171101020941.GM4635@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