From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/3] sh/ARM: shmobile: add sh_clk_fsidiv_register()
Date: Thu, 08 Nov 2012 05:28:29 +0000 [thread overview]
Message-ID: <20121108052828.GH11568@linux-sh.org> (raw)
In-Reply-To: <87ip9rmjcb.wl%kuninori.morimoto.gx@renesas.com>
On Thu, Nov 08, 2012 at 10:06:31AM +0900, Simon Horman wrote:
> On Wed, Nov 07, 2012 at 04:09:12PM -0800, Kuninori Morimoto wrote:
> >
> > Hi Simon
> >
> > > > > These patches add sh_clk_fsidiv_register() for FSI-DIV clock control.
> > > > > This is 1st step of FSI-DT support.
> > > > > My plan is...
> > > > >
> > > > > 1st : sh/ARM: add FSI-DIV clock control functions
> > > > > 2nd : FSI driver supports audio clock calculation method
> > > > > 3rd : sh/ARM: remove old style .set_rate callback from platform
> > > > > 4th : FSI support DT
> > > > > 5th : platform use DT for FSI
> > > > >
> > > > > Kuninori Morimoto (3):
> > > > > sh: clkfwk: add sh_clk_fsidiv_register()
> > > > > ARM: shmobile: sh7372: sh7372_fsidivX_clk become non-global
> > > > > ARM: shmobile: sh7372: use sh_clk_fsidiv_register() for FSI-DIV clocks
> > > >
> > > > I am slightly confused about why 4 patches, but its not a big deal.
> > > >
> > > > Paul, how do you want to handle merging this? The 1st patch looks like its
> > > > appropriate for your tree while the rest seem to belong in my tree. But I'm
> > > > happy for all the changes to go through one tree if that makes sense.
> > >
> > > It's not such a big deal either way. Once the first patch has been
> > > corrected with the appropriate I/O accessors you're welcome to take it
> > > with the rest with my Acked-by. I don't believe we have anything on the
> > > SH side that depends on it, so there's not a lot of point in decoupling
> > > it from the rest of the patch set.
> >
> > Now ALSA SoC maintainer accepted above 2nd step patch-set of FSI driver,
> > So, I would like to send 3rd step patches to SH-ML.
> > But it needs above (1st step) patch-set.
> > Where can I find ?
>
> Hi Morimoto-san,
>
> sorry for being a bit slow. There seem to be four patches in this series:
>
> [PATCH 1/3] sh: clkfwk: add sh_clk_fsidiv_register()
> [PATCH 2/3] ARM: shmobile: sh7372: sh7372_fsidivX_clk become non-global
> [PATCH 3/3] ARM: shmobile: sh7372: use sh_clk_fsidiv_register() for FSI-DIV clocks
> [PATCH 4/3] ARM: shmobile: r8a7740: add FSI-DVI clocks
>
>
> It seems that the first patch for drivers/sh/clk/cpg.c and
> include/linux/sh_clk.h and thus would normally go through Paul's tree.
> And that it is a dependency of the other three patches.
>
> Paul, I wonder if it would be easiest to try and push all of these changes
> through my tree.
>
Yes, it's fine going through your tree. You can add my acked-by if you
wish.
next prev parent reply other threads:[~2012-11-08 5:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 3:05 [PATCH 0/3] sh/ARM: shmobile: add sh_clk_fsidiv_register() Kuninori Morimoto
2012-10-31 7:08 ` Simon Horman
2012-11-01 0:11 ` Paul Mundt
2012-11-08 0:09 ` Kuninori Morimoto
2012-11-08 1:06 ` Simon Horman
2012-11-08 5:28 ` Paul Mundt [this message]
2012-11-08 5:43 ` 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=20121108052828.GH11568@linux-sh.org \
--to=lethal@linux-sh.org \
--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).