From: Arun Parameswaran <arun.parameswaran@broadcom.com>
To: Rob Herring <robh@kernel.org>, davem@davemloft.net
Cc: Richard Cochran <richardcochran@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH v1 1/2] dt-binding: ptp: add bindings document for dte based ptp clock
Date: Mon, 19 Jun 2017 09:50:27 -0700 [thread overview]
Message-ID: <8a45ea64-5a0e-6ecf-1e1d-ab8e85aa3115@broadcom.com> (raw)
In-Reply-To: <20170618140449.aek7vag22i5lnbhl@rob-hp-laptop>
Hi David, Rob,
I will address all of Rob's comments below.
Since a part of the patch was applied to 'net-next', would you like me to
send a new patch (based on the applied one), or a 'V2' of this patch ?
Thanks
Arun
On 17-06-18 07:04 AM, Rob Herring wrote:
> On Mon, Jun 12, 2017 at 01:26:00PM -0700, Arun Parameswaran wrote:
>> Add device tree binding documentation for the Broadcom DTE
>> PTP clock driver.
>>
>> Signed-off-by: Arun Parameswaran <arun.parameswaran@broadcom.com>
>> ---
>> Documentation/devicetree/bindings/ptp/brcm,ptp-dte.txt | 13 +++++++++++++
>> 1 file changed, 13 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/ptp/brcm,ptp-dte.txt
>>
>> diff --git a/Documentation/devicetree/bindings/ptp/brcm,ptp-dte.txt b/Documentation/devicetree/bindings/ptp/brcm,ptp-dte.txt
>> new file mode 100644
>> index 0000000..07590bc
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/ptp/brcm,ptp-dte.txt
>> @@ -0,0 +1,13 @@
>> +* Broadcom Digital Timing Engine(DTE) based PTP clock driver
>
> Bindings describe h/w, not drivers.
>
>> +
>> +Required properties:
>> +- compatible: should be "brcm,ptp-dte"
>
> Looks too generic. You need SoC specific compatible strings.
>
>> +- reg: address and length of the DTE block's NCO registers
>> +
>> +Example:
>> +
>> +ptp_dte: ptp_dte@180af650 {
>
> Don't use '_' in node names.
>
>> + compatible = "brcm,ptp-dte";
>> + reg = <0x180af650 0x10>;
>> + status = "okay";
>> +};
>> --
>> 1.9.1
>>
next prev parent reply other threads:[~2017-06-19 16:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 20:25 [PATCH v1 0/2] Add support for Broadcom DTE based PTP clock Arun Parameswaran
2017-06-12 20:26 ` [PATCH v1 1/2] dt-binding: ptp: add bindings document for dte based ptp clock Arun Parameswaran
2017-06-13 5:09 ` Richard Cochran
2017-06-13 17:46 ` Arun Parameswaran
2017-06-14 18:18 ` Ray Jui
2017-06-14 18:33 ` Arun Parameswaran
2017-06-14 18:39 ` Arun Parameswaran
2017-06-18 14:04 ` Rob Herring
2017-06-19 16:50 ` Arun Parameswaran [this message]
2017-06-20 20:48 ` Scott Branden
2017-06-22 3:19 ` Rob Herring
2017-06-23 0:42 ` Scott Branden
2017-06-23 1:04 ` Florian Fainelli
2017-06-27 5:10 ` Scott Branden
2017-06-29 22:40 ` Rob Herring
2017-06-30 1:05 ` Scott Branden
2017-06-12 20:26 ` [PATCH v1 2/2] ptp: Add a ptp clock driver for Broadcom DTE Arun Parameswaran
2017-06-15 16:07 ` [PATCH v1 0/2] Add support for Broadcom DTE based PTP clock David Miller
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=8a45ea64-5a0e-6ecf-1e1d-ab8e85aa3115@broadcom.com \
--to=arun.parameswaran@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox