From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: sboyd@codeaurora.org, mturquette@baylibre.com,
xuwei5@hisilicon.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH V2] clk: hi6220: Add the hi655x's pmic clock
Date: Wed, 12 Apr 2017 14:10:31 +0200 [thread overview]
Message-ID: <c1dba250-a60c-febc-a5c3-5ba645a61ce0@linaro.org> (raw)
In-Reply-To: <20170412080038.kk4vrjhvr3eao26q@dell>
On 12/04/2017 10:00, Lee Jones wrote:
> On Tue, 11 Apr 2017, Daniel Lezcano wrote:
>
>> On Tue, Apr 11, 2017 at 03:06:13PM +0100, Lee Jones wrote:
>>> On Sat, 08 Apr 2017, Daniel Lezcano wrote:
>>>
>>>> The hi655x multi function device is a PMIC providing regulators.
>>>>
>>>> The PMIC also provides a clock for the WiFi and the Bluetooth, let's implement
>>>> this clock in order to add it in the hi655x MFD and allow proper wireless
>>>> initialization.
>>>>
>>>> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
[ ... ]
>> Do you want to drop it from your tree or shall I resubmit a V3 without the mfd
>> change?
>
> The latter please.
Ok.
What about the DT binding change?
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2017-04-12 12:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 20:30 [PATCH V2] clk: hi6220: Add the hi655x's pmic clock Daniel Lezcano
2017-04-11 14:06 ` Lee Jones
2017-04-11 21:19 ` Daniel Lezcano
2017-04-12 8:00 ` Lee Jones
2017-04-12 12:10 ` Daniel Lezcano [this message]
2017-04-12 13:34 ` Lee Jones
2017-04-12 15:02 ` Stephen Boyd
2017-04-16 20:57 ` Daniel Lezcano
2017-04-19 16:00 ` Stephen Boyd
2017-04-19 19:47 ` Daniel Lezcano
2017-04-22 2:14 ` Stephen Boyd
2017-04-24 9:31 ` Lee Jones
2017-04-24 9:43 ` Daniel Lezcano
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=c1dba250-a60c-febc-a5c3-5ba645a61ce0@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=xuwei5@hisilicon.com \
/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).