netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helmut Buchsbaum <helmut.buchsbaum@gmail.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
	"David S. Miller" <davem@davemloft.net>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v2 6/6] dt-bindings: net: ks8995: add bindings documentation for ks8995
Date: Tue, 9 Feb 2016 09:07:21 +0100	[thread overview]
Message-ID: <56B99E39.1000207@gmail.com> (raw)
In-Reply-To: <56B8E205.1010807@cogentembedded.com>

On 02/08/2016 07:44 PM, Sergei Shtylyov wrote:
> Hello.
>
> On 02/08/2016 08:35 PM, Helmut Buchsbaum wrote:
>
>> Signed-off-by: Helmut Buchsbaum <helmut.buchsbaum@gmail.com>
>> ---
>>   .../devicetree/bindings/net/micrel-ks8995.txt        | 20
>> ++++++++++++++++++++
>>   1 file changed, 20 insertions(+)
>>   create mode 100644
>> Documentation/devicetree/bindings/net/micrel-ks8995.txt
>>
>> diff --git a/Documentation/devicetree/bindings/net/micrel-ks8995.txt
>> b/Documentation/devicetree/bindings/net/micrel-ks8995.txt
>> new file mode 100644
>> index 0000000..7f11ca6
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/net/micrel-ks8995.txt
>> @@ -0,0 +1,20 @@
>> +Micrel KS8995 SPI controlled Ethernet Switch families
>> +
>> +Required properties (according to spi-bus.txt):
>> +- compatible: either "micrel,ks8995", "micrel,ksz8864" or
>> "micrel,ksz8795"
>> +
>> +Optional properties:
>> +- reset-gpios : phandle of gpio that will be used to reset chip
>> during probe
>> +
>> +Example:
>> +
>> +spi-master {
>> +    ...
>> +    ksz8795 {
>
>     ePAPR tells to name the nodes generically, according to their function.
>
>> +        compatible = "micrel,ksz8795";
>> +
>> +        reg = <0>;
>> +        spi-max-frequency = <50000000>;
>> +        reset-gpios = <&gpio0 46 1>;
>> +    };
>> +};
>
> MBR, Sergei
>
Hello Sergei,

just to avoid any misunderstandings: you refer to ePAPR, ch. 2.2.1 Node 
Names. Your definitely right, I'll correct the naming in my example!

Thanks,
Helmut

  reply	other threads:[~2016-02-09  8:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 17:35 [PATCH v2 0/6] Add support for MICREL KSZ8795CLX 5-port switch Helmut Buchsbaum
2016-02-08 17:35 ` [PATCH v2 1/6] net: phy: spi_ks8995: introduce spi_device_id table Helmut Buchsbaum
2016-02-08 17:35 ` [PATCH v2 2/6] net: phy: spi_ks8995: verify chip and determine revision Helmut Buchsbaum
2016-02-08 17:35 ` [PATCH v2 3/6] net: phy: spi_ks8995: add support for resetting switch using GPIO Helmut Buchsbaum
2016-02-09  8:32   ` Andrew Lunn
2016-02-08 17:35 ` [PATCH v2 4/6] net: phy: spi_ks8995: generalize creation of SPI commands Helmut Buchsbaum
2016-02-08 17:35 ` [PATCH v2 5/6] net: phy: spi_ks8995: add support for MICREL KSZ8795CLX Helmut Buchsbaum
2016-02-08 17:35 ` [PATCH v2 6/6] dt-bindings: net: ks8995: add bindings documentation for ks8995 Helmut Buchsbaum
2016-02-08 18:44   ` Sergei Shtylyov
2016-02-09  8:07     ` Helmut Buchsbaum [this message]
2016-02-09 10:43       ` Sergei Shtylyov

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=56B99E39.1000207@gmail.com \
    --to=helmut.buchsbaum@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=sergei.shtylyov@cogentembedded.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).