From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Marek Belisko <marek.belisko@gmail.com>
Cc: mturquette@linaro.org, grant.likely@secretlab.ca,
rob.herring@calxeda.com, rob@landley.net, daniel@zonque.org,
vladimir.koutny@streamunlimited.com,
devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Marek Belisko <marek.belisko@streamunlimited.com>
Subject: Re: [PATCH v2] clk: si5351: Allow user to define disabled state for every clock output
Date: Fri, 03 May 2013 12:02:02 +0200 [thread overview]
Message-ID: <51838B1A.4010803@gmail.com> (raw)
In-Reply-To: <1367559207-20086-1-git-send-email-marek.belisko@streamunlimited.com>
On 05/03/2013 07:33 AM, Marek Belisko wrote:
> From: Sebastian Hesselbarth<sebastian.hesselbarth@gmail.com>
>
> This patch adds platform data and DT bindings to allow to overwrite
> the stored disabled state for each clock output.
>
> Signed-off-by: Marek Belisko<marek.belisko@streamunlimited.com>
> Signed-off-by: Sebastian Hesselbarth<sebastian.hesselbarth@gmail.com>
> ---
> Changes from v1->v2:
> Sebastian Hesselbarth send me updated version of patch which was based
> on v1. Resending with updates.
Marek,
it is ok to be a little bit more noisy about changes. But as I took
your v1 and did it, here is the Changelog:
- add helper to set disabled state for clkout
- make disabled-state property behave like other properties, i.e.
only overwrite disabled state when set through platform_data or DT
Sebastian
next prev parent reply other threads:[~2013-05-03 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 5:33 [PATCH v2] clk: si5351: Allow user to define disabled state for every clock output Marek Belisko
2013-05-03 10:02 ` Sebastian Hesselbarth [this message]
[not found] ` <1367559207-20086-1-git-send-email-marek.belisko-6oiIBCxl0MMjD8S081q9vkEOCMrvLtNR@public.gmane.org>
2013-05-14 19:13 ` Mike Turquette
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=51838B1A.4010803@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=daniel@zonque.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.belisko@gmail.com \
--cc=marek.belisko@streamunlimited.com \
--cc=mturquette@linaro.org \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=vladimir.koutny@streamunlimited.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).