From: Stephen Boyd <sboyd@codeaurora.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: mturquette@baylibre.com, lee.jones@linaro.org,
xuwei5@hisilicon.com, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org
Subject: Re: [PATCH V3 1/2] clk: hi6220: Add the hi655x's pmic clock
Date: Fri, 21 Apr 2017 19:03:45 -0700 [thread overview]
Message-ID: <20170422020345.GB7065@codeaurora.org> (raw)
In-Reply-To: <1492449567-31399-1-git-send-email-daniel.lezcano@linaro.org>
On 04/17, 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>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2017-04-22 2:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 17:19 [PATCH V3 1/2] clk: hi6220: Add the hi655x's pmic clock Daniel Lezcano
2017-04-17 17:19 ` [PATCH V3 2/2] ARM64: dts: hi6220-hikey: Add clock binding for the pmic mfd Daniel Lezcano
2017-04-17 17:19 ` Daniel Lezcano
2017-04-20 14:19 ` Rob Herring
2017-04-20 14:19 ` Rob Herring
2017-04-22 2:02 ` Stephen Boyd
2017-04-22 2:02 ` Stephen Boyd
2017-04-22 14:09 ` Daniel Lezcano
2017-04-22 14:09 ` Daniel Lezcano
2017-04-22 14:09 ` Daniel Lezcano
2017-04-24 8:59 ` Lee Jones
2017-04-24 8:59 ` Lee Jones
2017-04-24 9:16 ` Daniel Lezcano
2017-04-24 9:16 ` Daniel Lezcano
2017-04-24 13:01 ` Lee Jones
2017-04-24 13:01 ` Lee Jones
2017-04-24 13:01 ` Lee Jones
2017-04-24 20:11 ` Daniel Lezcano
2017-04-24 20:11 ` Daniel Lezcano
2017-04-24 20:19 ` Arnd Bergmann
2017-04-24 20:19 ` Arnd Bergmann
2017-04-24 20:19 ` Arnd Bergmann
2017-04-22 2:03 ` Stephen Boyd [this message]
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=20170422020345.GB7065@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=daniel.lezcano@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.