linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: David Lechner <david@lechnology.com>,
	devicetree@vger.kernel.org, linux-bluetooth@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Marcel Holtmann <marcel@holtmann.org>,
	Gustavo Padovan <gustavo@padovan.org>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: Add optional nvmem MAC address bindings to ti,wlink-st
Date: Mon, 4 Dec 2017 12:54:31 +0300	[thread overview]
Message-ID: <2dfb7130-e229-7429-0f30-11d7df553fdf@cogentembedded.com> (raw)
In-Reply-To: <1512357682-8911-2-git-send-email-david@lechnology.com>

Hello!

On 12/4/2017 6:21 AM, David Lechner wrote:

> This adds optional nvmem consumer properties to the ti,wlink-st device tree
> bindings to allow specifying the Bluetooth MAC address.
> 
> Signed-off-by: David Lechner <david@lechnology.com>
> ---
>   Documentation/devicetree/bindings/net/ti,wilink-st.txt | 4 ++++
>   1 file changed, 4 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/net/ti,wilink-st.txt b/Documentation/devicetree/bindings/net/ti,wilink-st.txt
> index 1649c1f..24eb897 100644
> --- a/Documentation/devicetree/bindings/net/ti,wilink-st.txt
> +++ b/Documentation/devicetree/bindings/net/ti,wilink-st.txt
> @@ -32,6 +32,8 @@ Optional properties:
>      See ../clocks/clock-bindings.txt for details.
>    - clock-names : Must include the following entry:
>      "ext_clock" (External clock provided to the TI combo chip).
> + - nvmem-cells: phandle to nvmem data cell that contains a MAC address
> + - nvmem-cell-names: "mac-address" (required when nvmem-cells is specified)
>   
>   Example:
>   
> @@ -43,5 +45,7 @@ Example:
>   		enable-gpios = <&gpio1 7 GPIO_ACTIVE_HIGH>;
>   		clocks = <&clk32k_wl18xx>;
>   		clock-names = "ext_clock";
> +		nvmem-cells: <&mac_address>

    s/:/ = /?

> +		nvmem-cell-names "mac-address"

    Where's =?

[...]

MBR, Sergei

  parent reply	other threads:[~2017-12-04  9:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04  3:21 [PATCH 0/3] bluetooth: hci_ll: Get MAC address from NVMEM David Lechner
2017-12-04  3:21 ` [PATCH 1/3] dt-bindings: Add optional nvmem MAC address bindings to ti,wlink-st David Lechner
2017-12-04  6:50   ` Marcel Holtmann
2017-12-04  9:54   ` Sergei Shtylyov [this message]
2017-12-04 10:09     ` Sergei Shtylyov
2017-12-04  3:21 ` [PATCH 2/3] bluetooth: hci_ll: add constant for vendor-specific command David Lechner
2017-12-04  6:23   ` Marcel Holtmann
2017-12-07 21:29     ` David Lechner
2017-12-07 21:43       ` Marcel Holtmann
2017-12-04  3:21 ` [PATCH 3/3] bluetooth: hci_ll: Add optional nvmem MAC address source David Lechner
2017-12-04  6:48   ` Marcel Holtmann

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=2dfb7130-e229-7429-0f30-11d7df553fdf@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=david@lechnology.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gustavo@padovan.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mark.rutland@arm.com \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).