From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/4] arm: rmobile: Add support R8A7791
Date: Tue, 5 Nov 2013 09:12:16 +0100 [thread overview]
Message-ID: <20131105091216.265885cd@lilith> (raw)
In-Reply-To: <CABMQnVJRCQG-BDCNRiM5TNvOsRDawHAwc-tirOyPEM2Gm8D8Cg@mail.gmail.com>
Hi Nobuhiro,
On Thu, 31 Oct 2013 17:18:54 +0900, Nobuhiro Iwamatsu
<nobuhiro.iwamatsu.yj@renesas.com> wrote:
> Hi, again.
>
> 2013/10/31 Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>:
> > Hi, Albert.
> >
> > Sorry, I dont notice your mail.
> >
> > 2013/10/30 Albert ARIBAUD <albert.u.boot@aribaud.net>:
> >> On Thu, 17 Oct 2013 13:04:06 +0200, Albert ARIBAUD
> >> <albert.u.boot@aribaud.net> wrote:
> >>
> >>> Hi Nobuhiro,
> >>>
> >>> On Tue, 24 Sep 2013 15:38:34 +0900, Nobuhiro Iwamatsu
> >>> <nobuhiro.iwamatsu.yj@renesas.com> wrote:
> >>>
> >>> > Renesas R8A7791 is CPU with Cortex-A7 and A15.
> >>> > This supports the basic register definition and GPIO and
> >>> > framework of PFC.
> >>> >
> >>> > Signed-off-by: Hisashi Nakamura <hisashi.nakamura.ak@renesas.com>
> >>> > Signed-off-by: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>
> >>> > CC: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
> >>> > CC: Albert Aribaud <albert.u.boot@aribaud.net>
> >>> > ---
> >>> > arch/arm/cpu/armv7/rmobile/Makefile | 2 +
> >>> > arch/arm/cpu/armv7/rmobile/cpu_info-r8a7791.c | 29 +
> >>> > arch/arm/cpu/armv7/rmobile/cpu_info.c | 5 +
> >>> > arch/arm/cpu/armv7/rmobile/pfc-r8a7791.c | 3415 ++++++++++++++++++++++
> >>>
> >>> Is there no way to make this big file common between R8A7790 and
> >>> R8A7791?
> >
> > Thanks for your comment.
> >
> > Sorry, do you mean that "Can you common the PFC of r8a7790 and
> > r8a7791?", because this file is large and
> > these can be used in common.
> > Right?
> >
> > If this is right, I will merge these file and re-send.
> >
>
> I tried common between R8A7790 and R8A7791.
> But these files have register infomation of Pin Function Controller.
> Register configuration is different from these, there is almost no common parts.
> However, I found a common part of some. It is possible to separate them.
If this can reduce the overall source code size, please do so.
> Best regards,
> Nobuhiro
Amicalement,
--
Albert.
next prev parent reply other threads:[~2013-11-05 8:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 6:38 [U-Boot] [PATCH 1/4] serial: sh: Add support R8A7791 Nobuhiro Iwamatsu
2013-09-24 6:38 ` [U-Boot] [PATCH 2/4] net: sh-eth: " Nobuhiro Iwamatsu
2013-09-24 6:38 ` [U-Boot] [PATCH 3/4] arm: rmobile: " Nobuhiro Iwamatsu
2013-10-17 11:04 ` Albert ARIBAUD
2013-10-30 9:04 ` Albert ARIBAUD
2013-10-31 6:05 ` Nobuhiro Iwamatsu
2013-10-31 8:18 ` Nobuhiro Iwamatsu
2013-11-05 8:12 ` Albert ARIBAUD [this message]
2013-11-11 1:56 ` Nobuhiro Iwamatsu
2013-09-24 6:38 ` [U-Boot] [PATCH 4/4] arm: rmobile: Add support Koelsch board Nobuhiro Iwamatsu
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=20131105091216.265885cd@lilith \
--to=albert.u.boot@aribaud.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