From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL v2] Renesas ARM-based SoC board updates for v3.10
Date: Wed, 27 Mar 2013 11:37:45 +0000 [thread overview]
Message-ID: <201303271137.45652.arnd@arndb.de> (raw)
In-Reply-To: <CANqRtoT2gi4vObPwkRNkXkuCLWy0=otRqXedk32Wdgp+WS4vRg@mail.gmail.com>
On Wednesday 27 March 2013, Magnus Damm wrote:
> On Sat, Mar 23, 2013 at 12:39 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Friday 22 March 2013, Simon Horman wrote:
> > I expect that in 3.10, we will have all ARMv6 and ARMv7 platforms converted,
> > with the exception of realview, mmp, s5p, msm, and shmobile. I'm sure we
> > can do realview and mmp for 3.11, possibly also s5p. For shmobile, I think
> > most of the work would be changing drivers/sh/clk to integrate into the common
> > clk framework, and you need to find a way to enable ARM_PATCH_PHYS_VIRT and
> > AUTO_ZRELADDR. Are those things you think can be done for 3.11?
>
> Good to hear that most ARM platforms will be converted by v3.10. This
> is definitely something that I want to make happen for mach-shmobile
> as well.
>
> Our biggest challenge now is the move to common clocks. I suspect that
> moving all our boards and SoCs to common clocks will take much longer
> than v3.11 I'm afraid.
Ok, I see. If you think it's not likely to be ready for 3.12, we might
need to discuss again whether there is another way of making the
common clk and the sh-clk code coexist. For instance, we could rename
all if the sh/shmobile specific clk functions and their users from
clk_* to shclk_*, and provide a thin wrapper around them that integrates
into common clk.
> Starting with something smaller like EMEV2 may be a good first step.
> So somehow I'd like to start converting them one by one, perhaps also
> moving over the converted SoCs/boards to CONFIG_ARCH_MULTIPLATFORM in
> an incremental fashion. Do you happen to have any example subarch that
> has been migrated in an increment fashion already?
We have had a few that were able to do both multiplatform and
single-platform for some time, but then changed to multiplatform-only.
I think mvebu and vt8500 are in this category.
> Regarding ARM_PATCH_PHYS_VIRT and AUTO_ZRELADDR, I believe those
> should be enabled for the mach-shmobile bits that are used with
> CONFIG_ARCH_MULTIPLATFORM. Best way forward there is TBD, any
> recommendations would be very welcome!
Yes, makes sense.
What I think you should do is rename CONFIG_ARCH_SHMOBILE to
CONFIG_ARCH_SHMOBILE_SINGLE, and add a new symbol in
arch/arm/mach-shmobile/Kconfig like
config ARCH_SHMOBILE
bool "Renesas SH-Mobile / R-Mobile" if ARCH_MULTI_V6_V7
default CONFIG_ARCH_SHMOBILE_SINGLE
help
Support for Renesas's SH-Mobile and R-Mobile ARM platforms.
This way, the platform is a non-exclusive option for the multiplatform
case, and a hidden enabled option when building CONFIG_ARCH_SHMOBILE_SINGLE.
Every machine that is not ready for multiplatform can then add "depends on
CONFIG_ARCH_SHMOBILE_SINGLE".
Arnd
next prev parent reply other threads:[~2013-03-27 11:37 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 2:26 [GIT PULL v2] Renesas ARM-based SoC boards for v3.8 Simon Horman
2012-10-28 2:26 ` [PATCH 01/12] ARM: shmobile: r8a7740: Enable PMU Simon Horman
2012-10-28 11:28 ` Sergei Shtylyov
2012-10-29 5:11 ` Simon Horman
2012-10-28 2:26 ` [PATCH 02/12] ARM: shmobile: kzm9g: enable magnetometer ak8975 Simon Horman
2012-10-28 2:26 ` [PATCH 03/12] ARM: shmobile: kzm9g: enable three-axis digital accelerometer ADXL345 Simon Horman
2012-10-28 2:26 ` [PATCH 04/12] ARM: shmobile: kzm9g: enable DMAEngine on SHDI0 and SDHI2 Simon Horman
2012-10-28 2:26 ` [PATCH 05/12] ARM: mach-shmobile: add FLCTL DMA slave definitions for sh7372 Simon Horman
2012-10-28 2:26 ` [PATCH 06/12] ARM: shmobile: armadillo800eva: enable restart Simon Horman
2012-10-28 2:26 ` [PATCH 07/12] ARM: shmobile: r8a7779: add HSPI clock support Simon Horman
2012-10-28 2:26 ` [PATCH 08/12] ARM: shmobile: r8a7779: add I2C " Simon Horman
2012-10-28 2:26 ` [PATCH 09/12] ARM: shmobile: r8a7779: add I2C driver support Simon Horman
2012-10-28 2:26 ` [PATCH 10/12] ARM: shmobile: marzen: add HSPI support Simon Horman
2012-10-28 2:26 ` [PATCH 11/12] ARM: shmobile: r8a7740: fixup DT machine desc name typo Simon Horman
2012-10-28 2:26 ` [PATCH 12/12] ARM: mach-shmobile: Use DT_MACHINE for mackerel Simon Horman
2012-10-28 9:37 ` Thomas Petazzoni
2012-10-28 10:44 ` Simon Horman
2012-10-28 10:57 ` Thomas Petazzoni
2012-11-08 1:27 ` [GIT PULL v2] Renesas ARM-based SoC boards for v3.8 #2 Simon Horman
2012-11-08 1:27 ` [PATCH 1/7] ARM: shmobile: marzen: add USB phy support Simon Horman
2012-11-08 1:27 ` [PATCH 2/7] ARM: shmobile: marzen: add USB EHCI driver support Simon Horman
2012-11-08 1:27 ` [PATCH 3/7] ARM: shmobile: marzen: add USB OHCI " Simon Horman
2012-11-08 1:27 ` [PATCH 4/7] sh: clkfwk: add sh_clk_fsidiv_register() Simon Horman
2012-11-08 1:27 ` [PATCH 5/7] ARM: shmobile: sh7372: sh7372_fsidivX_clk become non-global Simon Horman
2012-11-08 1:27 ` [PATCH 6/7] ARM: shmobile: sh7372: use sh_clk_fsidiv_register() for FSI-DIV clocks Simon Horman
2012-11-08 1:27 ` [PATCH 7/7] ARM: shmobile: r8a7740: add FSI-DVI clocks Simon Horman
2012-11-08 6:29 ` [GIT PULL v2] Renesas ARM-based SoC boards for v3.8 #2 Simon Horman
2012-11-20 0:43 ` [GIT PULL v2] Renesas ARM-based SoC boards for v3.8 #3 Simon Horman
2012-11-20 0:43 ` [PATCH] ARM: shmobile: mackerel: Add FLCTL IRQ resource Simon Horman
2012-11-21 7:21 ` [GIT PULL v2] Renesas ARM-based SoC boards for v3.8 #3 Olof Johansson
2013-03-19 2:17 ` [GIT PULL v2] Renesas ARM-based SoC board updates for v3.10 Simon Horman
2013-03-19 2:17 ` [PATCH 01/13] ARM: shmobile: use GPIO SD-card detection on armadillo800eva Simon Horman
2013-03-19 2:17 ` [PATCH 02/13] ARM: shmobile: switch SDHI0 to GPIO regulator " Simon Horman
2013-03-19 2:17 ` [PATCH 03/13] ARM: shmobile: streamline mackerel SD and MMC devices Simon Horman
2013-03-19 2:17 ` [PATCH 04/13] ARM: shmobile: mark mackerel sh_mmcif_device __maybe_unused Simon Horman
2013-03-19 2:17 ` [PATCH 05/13] ARM: shmobile: marzen: Reference DT implementation Simon Horman
2013-03-19 2:17 ` [PATCH 06/13] ARM: shmobile: kzm9g: " Simon Horman
2013-03-19 2:17 ` [PATCH 07/13] ARM: shmobile: parse DT and configure pinmux early on kzm9g-reference Simon Horman
2013-03-19 2:17 ` [PATCH 08/13] ARM: shmobile: SDHI and MMCIF interfaces to kzm9g-reference Simon Horman
2013-03-19 2:17 ` [PATCH 09/13] ARM: shmobile: simplify kzm9g Kconfig dependencies Simon Horman
2013-03-19 2:17 ` [PATCH 10/13] ARM: shmobile: kzm9g: Remove warning about SMP Simon Horman
2013-03-19 2:17 ` [PATCH 11/13] ARM: shmobile: kzm9g: Trim reference DT_MACHINE_START Simon Horman
2013-03-19 2:18 ` [PATCH 12/13] ARM: shmobile: marzen: Use gic_iid macro for ICCIAR / interrupt ID Simon Horman
2013-03-19 2:18 ` [PATCH 13/13] ARM: shmobile: kzm9g: correct smsc regulator registration Simon Horman
2013-03-21 17:18 ` [GIT PULL v2] Renesas ARM-based SoC board updates for v3.10 Arnd Bergmann
2013-03-21 19:22 ` Arnd Bergmann
2013-03-22 0:32 ` Simon Horman
2013-03-22 0:58 ` Simon Horman
2013-03-22 12:40 ` Arnd Bergmann
2013-03-22 13:52 ` Simon Horman
2013-03-22 15:39 ` Arnd Bergmann
2013-03-27 5:30 ` Simon Horman
2013-03-27 9:54 ` Magnus Damm
2013-03-27 11:37 ` Arnd Bergmann [this message]
2013-04-01 9:15 ` Magnus Damm
2013-04-02 10:09 ` Arnd Bergmann
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=201303271137.45652.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).