From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH] clk: meson-gxbb: Export PWM related clocks for DT
Date: Wed, 07 Sep 2016 12:51:31 -0700 [thread overview]
Message-ID: <7ha8fjtrng.fsf@baylibre.com> (raw)
In-Reply-To: <20160907005208.GS12510@codeaurora.org> (Stephen Boyd's message of "Tue, 6 Sep 2016 17:52:08 -0700")
Stephen Boyd <sboyd@codeaurora.org> writes:
> On 08/22, Neil Armstrong wrote:
>> Add the PWM related clocks in order to be referenced as PWM source
>> clocks.
>>
>> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
>> ---
>
> Acked-by: Stephen Boyd <sboyd@codeaurora.org>
>
> With some more thought, it should go through whatever tree takes
> the dts changes. Conflicts in these header files should be
> managed by the same person and that person is the platform
> maintainer.
OK, I'll pick this up and take it through the amlogic -> arm-soc path.
Thanks,
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: devicetree@vger.kernel.org,
Neil Armstrong <narmstrong@baylibre.com>,
linux-kernel@vger.kernel.org, carlo@caione.org,
linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] clk: meson-gxbb: Export PWM related clocks for DT
Date: Wed, 07 Sep 2016 12:51:31 -0700 [thread overview]
Message-ID: <7ha8fjtrng.fsf@baylibre.com> (raw)
In-Reply-To: <20160907005208.GS12510@codeaurora.org> (Stephen Boyd's message of "Tue, 6 Sep 2016 17:52:08 -0700")
Stephen Boyd <sboyd@codeaurora.org> writes:
> On 08/22, Neil Armstrong wrote:
>> Add the PWM related clocks in order to be referenced as PWM source
>> clocks.
>>
>> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
>> ---
>
> Acked-by: Stephen Boyd <sboyd@codeaurora.org>
>
> With some more thought, it should go through whatever tree takes
> the dts changes. Conflicts in these header files should be
> managed by the same person and that person is the platform
> maintainer.
OK, I'll pick this up and take it through the amlogic -> arm-soc path.
Thanks,
Kevin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: meson-gxbb: Export PWM related clocks for DT
Date: Wed, 07 Sep 2016 12:51:31 -0700 [thread overview]
Message-ID: <7ha8fjtrng.fsf@baylibre.com> (raw)
In-Reply-To: <20160907005208.GS12510@codeaurora.org> (Stephen Boyd's message of "Tue, 6 Sep 2016 17:52:08 -0700")
Stephen Boyd <sboyd@codeaurora.org> writes:
> On 08/22, Neil Armstrong wrote:
>> Add the PWM related clocks in order to be referenced as PWM source
>> clocks.
>>
>> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
>> ---
>
> Acked-by: Stephen Boyd <sboyd@codeaurora.org>
>
> With some more thought, it should go through whatever tree takes
> the dts changes. Conflicts in these header files should be
> managed by the same person and that person is the platform
> maintainer.
OK, I'll pick this up and take it through the amlogic -> arm-soc path.
Thanks,
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Neil Armstrong <narmstrong@baylibre.com>,
carlo@caione.org, devicetree@vger.kernel.org,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: meson-gxbb: Export PWM related clocks for DT
Date: Wed, 07 Sep 2016 12:51:31 -0700 [thread overview]
Message-ID: <7ha8fjtrng.fsf@baylibre.com> (raw)
In-Reply-To: <20160907005208.GS12510@codeaurora.org> (Stephen Boyd's message of "Tue, 6 Sep 2016 17:52:08 -0700")
Stephen Boyd <sboyd@codeaurora.org> writes:
> On 08/22, Neil Armstrong wrote:
>> Add the PWM related clocks in order to be referenced as PWM source
>> clocks.
>>
>> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
>> ---
>
> Acked-by: Stephen Boyd <sboyd@codeaurora.org>
>
> With some more thought, it should go through whatever tree takes
> the dts changes. Conflicts in these header files should be
> managed by the same person and that person is the platform
> maintainer.
OK, I'll pick this up and take it through the amlogic -> arm-soc path.
Thanks,
Kevin
next prev parent reply other threads:[~2016-09-07 19:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 12:49 [PATCH] clk: meson-gxbb: Export PWM related clocks for DT Neil Armstrong
2016-08-22 12:49 ` Neil Armstrong
2016-08-22 12:49 ` Neil Armstrong
2016-09-02 23:34 ` Michael Turquette
2016-10-11 7:59 ` Michael Turquette
2016-10-11 7:59 ` Michael Turquette
2016-09-02 23:34 ` Michael Turquette
2016-09-02 23:34 ` Michael Turquette
2016-09-03 13:02 ` Neil Armstrong
2016-09-03 13:02 ` Neil Armstrong
2016-09-03 13:02 ` Neil Armstrong
2016-09-03 13:02 ` Neil Armstrong
2016-09-07 0:34 ` Stephen Boyd
2016-09-07 0:34 ` Stephen Boyd
2016-09-07 0:34 ` Stephen Boyd
2016-09-07 0:52 ` Stephen Boyd
2016-09-07 0:52 ` Stephen Boyd
2016-09-07 0:52 ` Stephen Boyd
2016-09-07 19:51 ` Kevin Hilman [this message]
2016-09-07 19:51 ` Kevin Hilman
2016-09-07 19:51 ` Kevin Hilman
2016-09-07 19:51 ` Kevin Hilman
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=7ha8fjtrng.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linus-amlogic@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 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.