SUPERH platform development
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v3 00/04] ARM: shmobile: r8a7779 Marzen multiplatform cleanup V3
Date: Wed, 15 Jul 2015 06:43:58 +0000	[thread overview]
Message-ID: <20150715064358.GA5071@verge.net.au> (raw)
In-Reply-To: <20150713061450.25534.96315.sendpatchset@little-apple>

On Wed, Jul 15, 2015 at 02:56:33PM +0900, Magnus Damm wrote:
> Hi Simon,
> 
> On Wed, Jul 15, 2015 at 10:16 AM, Simon Horman <horms@verge.net.au> wrote:
> > Hi Magnus,
> >
> > On Wed, Jul 15, 2015 at 09:25:01AM +0900, Simon Horman wrote:
> >> Hi Magnus,
> >>
> >> On Mon, Jul 13, 2015 at 03:14:50PM +0900, Magnus Damm wrote:
> >> > ARM: shmobile: r8a7779 Marzen multiplatform cleanup V3
> >> >
> >> > [PATCH v3 01/04] ARM: shmobile: r8a7779: Generic SMP ops
> >> > [PATCH v3 02/04] ARM: shmobile: marzen-reference: Remove C board code
> >> > [PATCH v3 03/04] ARM: shmobile: Remove Marzen from shmobile_defconfig
> >> > [PATCH v3 04/04] ARM: shmobile: r8a7779: Cleanup header file
> >> >
> >> > This series is simply resending the remaining r8a7779 multiplatform
> >> > cleanup patches. The code has not changed since V2:
> >> >
> >> > [PATCH v2 00/06] ARM: shmobile: r8a7779 IRQ update and Marzen cleanup V2
> >> >
> >> > With these patches applied the r8a7779 SoC gets DT-only multiplatform
> >> > support and old C board code for multiplatform gets removed.
> >> >
> >> > The legacy r8a7779 Marzen code is not touched by this series, but
> >> > with these patches applied basic r8a7779 multiplatform SoC support
> >> > is done and only a few I/O devices are legacy-only.
> >>
> >> Thanks, I have queued these up.
> >>
> >> Please send a follow-up patch to address Geert's observation that
> >> CONFIG_MACH_MARZEN should be removed from multi_v7_defconfig.
> >
> > Unfortunately I have noticed a problem with patch 02/04,
> > and in particular the following portion of it:
> >
> > --- a/arch/arm/mach-shmobile/Kconfig
> > +++ b/arch/arm/mach-shmobile/Kconfig
> > @@ -89,13 +89,6 @@ config ARCH_SH73A0
> >         select ARCH_RMOBILE
> >         select RENESAS_INTC_IRQPIN
> >
> > -comment "Renesas ARM SoCs Board Type"
> > -
> > -config MACH_MARZEN
> > -       bool "MARZEN board"
> > -       depends on ARCH_R8A7779
> > -       select REGULATOR_FIXED_VOLTAGE if REGULATOR
> > -
> >
> > It appears that with the above applied REGULATOR_FIXED_VOLTAGE is
> > no longer set after make shmobile_defconfig which causes all sorts of
> > trouble as the fixed regulator is used by many devices on many boards.
> 
> Right, the regulator portion is indeed troublesome. And like you say,
> it is needed for many boards including Gen2.
> 
> > I wonder if the best way forwards would be to simply enable
> > REGULATOR_FIXED_VOLTAGE in shmobile_defconfig (and probably
> > multi_v7_defconfig too).
> 
> Yeah, I think so.

Thanks, I have sent a patch.
Review would be much appreciated.

  parent reply	other threads:[~2015-07-15  6:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13  6:14 [PATCH v3 00/04] ARM: shmobile: r8a7779 Marzen multiplatform cleanup V3 Magnus Damm
2015-07-15  0:25 ` Simon Horman
2015-07-15  1:16 ` Simon Horman
2015-07-15  5:56 ` Magnus Damm
2015-07-15  6:43 ` Simon Horman [this message]
2015-07-15  7:41 ` Geert Uytterhoeven

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=20150715064358.GA5071@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-sh@vger.kernel.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