linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	Jon Hunter <jonathanh@nvidia.com>,
	linux-i2c@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: Add Tegra186 BPMP I2C binding
Date: Fri, 27 Jan 2017 17:09:00 +0100	[thread overview]
Message-ID: <20170127160900.GB1928@katana> (raw)
In-Reply-To: <20170127083939.20393-2-thierry.reding@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 492 bytes --]


> +- nvidia,bpmp-bus-id:
> +    Single-cell integer.
> +    Indicates the I2C bus number this DT node represent, as defined by the
> +    BPMP firmware.

I'd like to get an ack from Rob for this one if vendor-specific bindings
are still the way to go to encode firmware data. I simply don't know.

> +
> +Example:
> +
> +bpmp {
> +	...
> +
> +	i2c {
> +		compatible = "nvidia,tegra186-bpmp-i2c";
> +		#address-cells = <1>;
> +		#size-cells = <0>;
> +		nvidia,bpmp-bus-id = <5>;
> +	};
> +};

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2017-01-27 16:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-27  8:39 [PATCH v2 0/2] i2c: Add Tegra BPMP I2C proxy driver Thierry Reding
     [not found] ` <20170127083939.20393-1-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-01-27  8:39   ` [PATCH v2 1/2] dt-bindings: Add Tegra186 BPMP I2C binding Thierry Reding
2017-01-27 16:09     ` Wolfram Sang [this message]
     [not found]     ` <20170127083939.20393-2-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-01-27 22:19       ` Thierry Reding
     [not found]         ` <20170127221857.GA15715-+E7KM1FDEuO2P7RxrfNFTMXXUOn6P5/W@public.gmane.org>
2017-01-27 22:52           ` Rob Herring
     [not found]             ` <CAL_Jsq+Sr=dOw7_9UAL4jO0zXycT7sHoCvUM4C2-9LBgdx=25g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-30  6:47               ` Thierry Reding
2017-01-28  5:42         ` Stephen Warren
     [not found]           ` <8841854b-d058-1a8d-3e40-955bf3546cef-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2017-01-30  6:50             ` Thierry Reding
2017-01-27  8:39   ` [PATCH v2 2/2] i2c: Add Tegra BPMP I2C proxy driver Thierry Reding
2017-02-10 16:37     ` Wolfram Sang
  -- strict thread matches above, loose matches on Subject: below --
2016-11-15 16:23 [PATCH v2 0/2] " Thierry Reding
2016-11-15 16:23 ` [PATCH v2 1/2] dt-bindings: Add Tegra186 BPMP I2C binding Thierry Reding

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=20170127160900.GB1928@katana \
    --to=wsa@the-dreams.de \
    --cc=gnurou@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=swarren@wwwdotorg.org \
    --cc=thierry.reding@gmail.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).