From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/3] clk: s2mps11: Add support for S2MPS14 clocks
Date: Thu, 20 Mar 2014 09:33:35 -0700 [thread overview]
Message-ID: <20140320163335.21989.2611@quantum> (raw)
In-Reply-To: <20140320134219.GB6816@lee--X1>
Quoting Lee Jones (2014-03-20 06:42:19)
> > > > > > This patch adds support for S2MPS14 PMIC clocks (BT and AP) to the
> > > > > > s2mps11 clock driver.
> > > > > >
> > > > > > Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> > > > > > Reviewed-by: Yadwinder Singh Brar <yadi.brar@samsung.com>
> > > > > > Reviewed-by: Tomasz Figa <t.figa@samsung.com>
> > > > >
> > > > > This does not apply cleanly to to clk tree trip, nor does it compile
> > > > > after manually merging due to changes introducing
> > > > > linux/mfd/samsung/s2mps14.h.
> > > > >
> > > > > The changes look OK to me so maybe Lee can take it with my Ack?
> > > > >
> > > > > Acked-by: Mike Turquette <mturquette@linaro.org>
> > > > >
> > > >
> > > > Hi,
> > > >
> > > > Thanks for the Ack. The patch depends on Tushar Behera's patches:
> > > > - [PATCH V2 0/2] Add support for clocks in S5M8767
> > > > http://thread.gmane.org/gmane.linux.kernel.samsung-soc/27264
> > > > which are waiting for some time. Both patchsets should be pulled
> > > > together.
> > >
> > > I took those patches in yesterday. So we have three options:
> >
> > Great! Thanks.
> >
> > >
> > > 1) MFD tree can pull a stable commit from the clk tree. I'm happy to
> > > make a topic branch for this. Then these patches can be applied.
> > >
> > > 2) clk tree can pull a stable commit from the mfd tree if the mfd folks
> > > can provide one.
> > >
> > > 3) Wait until after the merge window to apply this one to the clk tree.
> > > I don't currently plan to send 2 PRs during the merge window, so this
> > > could either go in 3.16 or maybe into 3.15 if a split PR is sent.
> >
> > Dear Lee,
> >
> > How do you wish to proceed? The patchset depends on changes in sec-core
> > MFD driver.
>
> The MFD tree is betting pretty complicated with sec-core stuff at the
> minuite. Can I vote for option 3?
Sure. clock tree feels the same way. ;-)
Regards,
Mike
>
> --
> Lee Jones
> Linaro STMicroelectronics Landing Team Lead
> Linaro.org ? Open source software for ARM SoCs
> Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-03-20 16:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 9:19 [PATCH v3 0/3] clk: s2mps11: Add support for S2MPS14 clocks Krzysztof Kozlowski
2014-03-17 9:19 ` [PATCH v3 1/3] " Krzysztof Kozlowski
2014-03-19 0:16 ` Mike Turquette
2014-03-19 7:50 ` Krzysztof Kozlowski
2014-03-19 19:11 ` Mike Turquette
2014-03-20 12:45 ` Krzysztof Kozlowski
2014-03-20 13:42 ` Lee Jones
2014-03-20 16:33 ` Mike Turquette [this message]
2014-03-19 1:09 ` Mike Turquette
2014-03-19 1:11 ` Mike Turquette
2014-03-17 9:19 ` [PATCH v3 2/3] mfd: sec-core: Add of_compatible strings for clock MFD cells Krzysztof Kozlowski
2014-03-18 14:30 ` Tomasz Figa
2014-03-18 20:31 ` Lee Jones
2014-03-19 13:15 ` Krzysztof Kozlowski
2014-03-19 14:36 ` Lee Jones
2014-03-17 9:19 ` [PATCH v3 3/3] Documentation: mfd: s2mps11: Describe S5M8767 and S2MPS14 clocks Krzysztof Kozlowski
2014-03-18 20:33 ` Lee Jones
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=20140320163335.21989.2611@quantum \
--to=mturquette@linaro.org \
--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).