From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/7] ARM: shmobile: bockw: MMCIF support on DT
Date: Tue, 08 Oct 2013 02:07:16 +0000 [thread overview]
Message-ID: <20131008020712.GA7179@verge.net.au> (raw)
In-Reply-To: <878uy9259u.wl%kuninori.morimoto.gx@renesas.com>
On Mon, Oct 07, 2013 at 06:32:38PM -0700, Kuninori Morimoto wrote:
>
> Hi Simon
>
> > > > Kuninori Morimoto (7):
> > > > 1) ARM: shmobile: bockw: enable CONFIG_REGULATOR
> > > > 2) ARM: shmobile: bockw: use regulator for MMCIF
> > > > 3) ARM: shmobile: bockw: add default PFC settings on DTS
> > > > 4) ARM: shmobile: bockw: remove manual PFC settings on reference
> > > > 5) ARM: shmobile: r8a7778: add MMCIF clock support for DT
> > > > 6) ARM: shmobile: r8a7778: add MMCIF support on DTSI
> > > > 7) ARM: shmobile: bockw: add MMCIF support on DTS
> > > >
> > > > arch/arm/boot/dts/r8a7778-bockw-reference.dts | 25 ++++++++++++++++++++++++
> > > > arch/arm/boot/dts/r8a7778.dtsi | 8 ++++++++
> > > > arch/arm/configs/bockw_defconfig | 1 +
> > > > arch/arm/mach-shmobile/board-bockw-reference.c | 12 ------------
> > > > arch/arm/mach-shmobile/board-bockw.c | 13 ++++++++----
> > > > arch/arm/mach-shmobile/clock-r8a7778.c | 1 +
> > > > 6 files changed, 44 insertions(+), 16 deletions(-)
> > >
> > > And, these dpends on today's Laurent's
> > >
> > > Subject: [PATCH] ARM: shmobile: r8a7778: Fix pin control device address in DT
> > > Date: Thu, 3 Oct 2013 19:35:41 +0200
> >
> > Thanks Morimoto-san.
> >
> > Could you explain in a little more detail what the dependency is.
> > I am trying to work out if I should apply this series on top
> > of "ARM: shmobile: r8a7778: Fix pin control device address in DT"
> > or if they can be merged in parallel.
>
> "ARM: shmobile: r8a7778: Fix pin control device address in DT"
> is bugfix patch for DT.
> The kernel (especially, pfc settings = #3) doesn't work
> without it.
> Is this explain enough for you ?
Assuming that "ARM: shmobile: r8a7778: Fix pin control device address in
DT" is not applied. When the pfc settings don't work does the kernel still
work as well as it did prior to patch #3 not being applied?
next prev parent reply other threads:[~2013-10-08 2:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 1:28 [PATCH 0/7] ARM: shmobile: bockw: MMCIF support on DT Kuninori Morimoto
2013-10-04 1:30 ` Kuninori Morimoto
2013-10-04 1:35 ` Kuninori Morimoto
2013-10-08 1:11 ` Simon Horman
2013-10-08 1:32 ` Kuninori Morimoto
2013-10-08 2:07 ` Simon Horman [this message]
2013-10-08 2:57 ` Kuninori Morimoto
2013-10-08 4:00 ` Simon Horman
2013-10-08 20:59 ` Laurent Pinchart
2013-10-09 0:11 ` Kuninori Morimoto
2013-10-09 20:20 ` Laurent Pinchart
2013-10-10 11:33 ` Simon Horman
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=20131008020712.GA7179@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;
as well as URLs for NNTP newsgroup(s).