From: Ray Jui <rjui@broadcom.com>
To: Jon Mason <jonmason@broadcom.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Florian Fainelli <f.fainelli@gmail.com>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
Scott Branden <sbranden@broadcom.com>,
<linux-clk@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [RFC 4/5] clk: iproc: define Broadcom NS2 iProc clock binding
Date: Wed, 14 Oct 2015 09:53:59 -0700 [thread overview]
Message-ID: <561E88A7.2090808@broadcom.com> (raw)
In-Reply-To: <20151014154410.GF15160@broadcom.com>
On 10/14/2015 8:44 AM, Jon Mason wrote:
> On Tue, Oct 13, 2015 at 03:24:52PM -0700, Ray Jui wrote:
>> Same as this patch. I thought device tree binding document should go
>> with the clock driver changes.
>>
>> Strictly speaking, device tree binding document should always go before
>> the driver changes. In the binding document the DT interface is defined,
>> then changes are implemented in the driver.
>
> I split them off this way due to the clk maintainer not wanting to
> pull in any device tree changes. Since the documentation is for the
> device tree enties, it makes logical sense to me that they be in the
> same device tree series. If Stephen will pull these in with the clk
> changes, I am more than happy to have it done by him :)
>
> Thanks,
> Jon
Yeah the clock maintainers do not pull in device tree changes like
*.dtsi and *.dts. But they do take changes including the binding
documents and clock driver changes. You can confirm with Stephen.
Thanks,
Ray
WARNING: multiple messages have this Message-ID (diff)
From: rjui@broadcom.com (Ray Jui)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 4/5] clk: iproc: define Broadcom NS2 iProc clock binding
Date: Wed, 14 Oct 2015 09:53:59 -0700 [thread overview]
Message-ID: <561E88A7.2090808@broadcom.com> (raw)
In-Reply-To: <20151014154410.GF15160@broadcom.com>
On 10/14/2015 8:44 AM, Jon Mason wrote:
> On Tue, Oct 13, 2015 at 03:24:52PM -0700, Ray Jui wrote:
>> Same as this patch. I thought device tree binding document should go
>> with the clock driver changes.
>>
>> Strictly speaking, device tree binding document should always go before
>> the driver changes. In the binding document the DT interface is defined,
>> then changes are implemented in the driver.
>
> I split them off this way due to the clk maintainer not wanting to
> pull in any device tree changes. Since the documentation is for the
> device tree enties, it makes logical sense to me that they be in the
> same device tree series. If Stephen will pull these in with the clk
> changes, I am more than happy to have it done by him :)
>
> Thanks,
> Jon
Yeah the clock maintainers do not pull in device tree changes like
*.dtsi and *.dts. But they do take changes including the binding
documents and clock driver changes. You can confirm with Stephen.
Thanks,
Ray
WARNING: multiple messages have this Message-ID (diff)
From: Ray Jui <rjui-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
To: Jon Mason <jonmason-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
Cc: Michael Turquette
<mturquette-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>,
Stephen Boyd <sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
Florian Fainelli
<f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Hauke Mehrtens <hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>,
Scott Branden <sbranden-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
bcm-kernel-feedback-list-dY08KVG/lbpWk0Htik3J/w@public.gmane.org
Subject: Re: [RFC 4/5] clk: iproc: define Broadcom NS2 iProc clock binding
Date: Wed, 14 Oct 2015 09:53:59 -0700 [thread overview]
Message-ID: <561E88A7.2090808@broadcom.com> (raw)
In-Reply-To: <20151014154410.GF15160-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
On 10/14/2015 8:44 AM, Jon Mason wrote:
> On Tue, Oct 13, 2015 at 03:24:52PM -0700, Ray Jui wrote:
>> Same as this patch. I thought device tree binding document should go
>> with the clock driver changes.
>>
>> Strictly speaking, device tree binding document should always go before
>> the driver changes. In the binding document the DT interface is defined,
>> then changes are implemented in the driver.
>
> I split them off this way due to the clk maintainer not wanting to
> pull in any device tree changes. Since the documentation is for the
> device tree enties, it makes logical sense to me that they be in the
> same device tree series. If Stephen will pull these in with the clk
> changes, I am more than happy to have it done by him :)
>
> Thanks,
> Jon
Yeah the clock maintainers do not pull in device tree changes like
*.dtsi and *.dts. But they do take changes including the binding
documents and clock driver changes. You can confirm with Stephen.
Thanks,
Ray
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-10-14 16:53 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 21:22 [PATCH 0/5] ARM: dts: add device tree support for NS, NSP, and NS2 clocks Jon Mason
2015-10-13 21:22 ` Jon Mason
2015-10-13 21:22 ` Jon Mason
2015-10-13 21:22 ` [RFC 1/5] clk: iproc: define Broadcom NSP iProc clock binding Jon Mason
2015-10-13 21:22 ` Jon Mason
2015-10-13 21:22 ` Jon Mason
2015-10-13 22:17 ` Ray Jui
2015-10-13 22:17 ` Ray Jui
2015-10-13 22:17 ` Ray Jui
2015-10-14 15:40 ` Jon Mason
2015-10-14 15:40 ` Jon Mason
2015-10-14 15:40 ` Jon Mason
2015-10-13 21:22 ` [RFC 2/5] ARM: dts: enable clock support for Broadcom NSP Jon Mason
2015-10-13 21:22 ` Jon Mason
2015-10-13 21:22 ` Jon Mason
2015-10-13 21:22 ` [RFC 3/5] ARM: dts: enable clock support for BCM5301X Jon Mason
2015-10-13 21:22 ` Jon Mason
2015-10-13 21:22 ` Jon Mason
2015-10-18 22:34 ` Hauke Mehrtens
2015-10-18 22:34 ` Hauke Mehrtens
2015-10-18 22:34 ` Hauke Mehrtens
2015-10-13 21:22 ` [RFC 4/5] clk: iproc: define Broadcom NS2 iProc clock binding Jon Mason
2015-10-13 21:22 ` Jon Mason
2015-10-13 21:22 ` Jon Mason
2015-10-13 22:24 ` Ray Jui
2015-10-13 22:24 ` Ray Jui
2015-10-13 22:24 ` Ray Jui
2015-10-14 15:44 ` Jon Mason
2015-10-14 15:44 ` Jon Mason
2015-10-14 15:44 ` Jon Mason
2015-10-14 16:53 ` Ray Jui [this message]
2015-10-14 16:53 ` Ray Jui
2015-10-14 16:53 ` Ray Jui
2015-10-16 22:11 ` Stephen Boyd
2015-10-16 22:11 ` Stephen Boyd
2015-10-13 21:22 ` [RFC 5/5] ARM: dts: enable clock support for Broadcom NS2 Jon Mason
2015-10-13 21:22 ` Jon Mason
2015-10-13 21:22 ` Jon Mason
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=561E88A7.2090808@broadcom.com \
--to=rjui@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=jonmason@broadcom.com \
--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=sbranden@broadcom.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.