public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH  0/6] Basic SoC support for r8a7743/r8a7745
Date: Wed, 19 Jul 2017 14:54:27 +0100	[thread overview]
Message-ID: <1500472467.1935.124.camel@codethink.co.uk> (raw)
In-Reply-To: <KL1PR06MB1702DE0CA0C499B831FFC8F4B8A60@KL1PR06MB1702.apcprd06.prod.outlook.com>

On Wed, 2017-07-19 at 08:24 +0000, Biju Das wrote:
[...]
> > Actually, there's something not quite right here.  With just
> > CONFIG_ARCH_R8A7743 and CONFIG_ARCH_R8A7745 enabled (but no other R-
> > Car
> > platforms) I get:
> 
> The patches are for Basic SoC support. Next I am planning Clock driver, then DT support for SoC, then Board DTS
> and then Enabling the config option(CONFIG_ARCH_R8A7743 and CONFIG_ARCH_R8A7745) .
> >
> > arch/arm/mach-shmobile/built-in.o: In function `rcar_gen2_timer_init':
> > /home/bwh/ln001-cip/kernel/arch/arm/mach-shmobile/setup-rcar-gen2.c:131:
> > undefined reference to `rcar_gen2_clocks_init'
> >
> > There seems to have been a lot of refactoring of drivers/clk/{shmobile,renesas}
> > since 4.4 so I'm not sure how this should be fixed.
> 
> Current upstreamed RZ/G1M clock driver uses the new Renesas CPG/MSSR clock  driver frame work.
> Backporting requires lot of refactoring of drivers/clk/{shmobile,renesas}.
> So I don't think backporting the RZ/G1M clock driver is the right choice.

OK.

> However r8a7743( RZ/G1M) is identical to r8a7791(RCar-M2) platform. We ported r8a7743( RZ/G1M) clk driver based on this.
> The current patch series, which I submitted is tested with this clk driver.

Then I think I should just make this change:

Subject: CIP: Build essential clock driver for Renesas RZ/G1 platforms

In mainline, clk-rcar-gen2 is selected by CONFIG_CLK_RCAR_GEN2 but
here there is no such common config symbol and we need to select
it for each platform.

Signed-off-by: Ben Hutchings <ben.hutchings@codethink.co.uk>
---
 drivers/clk/shmobile/Makefile | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/clk/shmobile/Makefile b/drivers/clk/shmobile/Makefile
index 97c71c885e4f..b339c0b6bb2f 100644
--- a/drivers/clk/shmobile/Makefile
+++ b/drivers/clk/shmobile/Makefile
@@ -2,6 +2,8 @@ obj-$(CONFIG_ARCH_EMEV2)		+= clk-emev2.o
 obj-$(CONFIG_ARCH_R7S72100)		+= clk-rz.o
 obj-$(CONFIG_ARCH_R8A73A4)		+= clk-r8a73a4.o
 obj-$(CONFIG_ARCH_R8A7740)		+= clk-r8a7740.o
+obj-$(CONFIG_ARCH_R8A7743)		+= clk-rcar-gen2.o
+obj-$(CONFIG_ARCH_R8A7745)		+= clk-rcar-gen2.o
 obj-$(CONFIG_ARCH_R8A7778)		+= clk-r8a7778.o
 obj-$(CONFIG_ARCH_R8A7779)		+= clk-r8a7779.o
 obj-$(CONFIG_ARCH_R8A7790)		+= clk-rcar-gen2.o
--- END ---

Right?

Ben.

-- 
Ben Hutchings
Software Developer, Codethink Ltd.

  reply	other threads:[~2017-07-19 13:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12  9:21 [cip-dev] [PATCH 0/6] Basic SoC support for r8a7743/r8a7745 Biju Das
2017-07-12  9:21 ` [cip-dev] [PATCH 1/6] sh_eth: add R8A7743/5 support Biju Das
2017-07-12  9:21 ` [cip-dev] [PATCH 2/6] DT: irqchip: renesas-irqc: document " Biju Das
2017-07-12  9:21 ` [cip-dev] [PATCH 3/6] sh-sci: " Biju Das
2017-07-12  9:21 ` [cip-dev] [PATCH 4/6] ARM: shmobile: r8a7743: basic SoC support Biju Das
2017-07-12  9:21 ` [cip-dev] [PATCH 5/6] ARM: shmobile: Consolidate R8A7743 and R8A779[234] machine definitions Biju Das
2017-07-12  9:21 ` [cip-dev] [PATCH 6/6] ARM: shmobile: r8a7745: basic SoC support Biju Das
2017-07-18 15:30 ` [cip-dev] [PATCH 0/6] Basic SoC support for r8a7743/r8a7745 Ben Hutchings
2017-07-18 15:58   ` Ben Hutchings
2017-07-19  8:24     ` Biju Das
2017-07-19 13:54       ` Ben Hutchings [this message]
2017-07-19 13:59         ` Biju Das
2017-07-19 14:23           ` Ben Hutchings

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=1500472467.1935.124.camel@codethink.co.uk \
    --to=ben.hutchings@codethink.co.uk \
    --cc=cip-dev@lists.cip-project.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