linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean-Baptiste Maneyrol <JManeyrol@invensense.com>
To: Stephan Gerhold <stephan@gerhold.net>,
	Jonathan Cameron <jic23@kernel.org>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Brian Masney <masneyb@onstation.org>,
	Jonathan Marek <jonathan@marek.ca>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: iio: imo: mpu6050: add vdd-supply
Date: Fri, 8 Nov 2019 12:11:46 +0000	[thread overview]
Message-ID: <MN2PR12MB33733917812945D0293D9D27C47B0@MN2PR12MB3373.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20191107184342.20361-1-stephan@gerhold.net>

Reviewed-by: Jean-Baptiste Maneyrol <jmaneyrol@invensense.com>

Best regards,
JB

From: linux-iio-owner@vger.kernel.org <linux-iio-owner@vger.kernel.org> on behalf of Stephan Gerhold <stephan@gerhold.net>

Sent: Thursday, November 7, 2019 19:43

To: Jonathan Cameron <jic23@kernel.org>

Cc: Hartmut Knaack <knaack.h@gmx.de>; Lars-Peter Clausen <lars@metafoo.de>; Peter Meerwald-Stadler <pmeerw@pmeerw.net>; Rob Herring <robh+dt@kernel.org>; Mark Rutland <mark.rutland@arm.com>; Linus Walleij <linus.walleij@linaro.org>; Brian Masney <masneyb@onstation.org>;
 Jonathan Marek <jonathan@marek.ca>; Jean-Baptiste Maneyrol <JManeyrol@invensense.com>; linux-iio@vger.kernel.org <linux-iio@vger.kernel.org>; devicetree@vger.kernel.org <devicetree@vger.kernel.org>; linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>;
 Stephan Gerhold <stephan@gerhold.net>

Subject: [PATCH v2 1/2] dt-bindings: iio: imo: mpu6050: add vdd-supply

 


 CAUTION: This email originated from outside of the organization. Please make sure the sender is who they say they are and do not click links or open attachments unless you recognize the sender and know the content is safe.



inv_mpu6050 now supports an additional vdd-supply; document it.







Reviewed-by: Linus Walleij <linus.walleij@linaro.org>



Signed-off-by: Stephan Gerhold <stephan@gerhold.net>



---



Changes in v2:



  - Add Reviewed-by from Linus Walleij







v1: 
https://urldefense.proofpoint.com/v2/url?u=https-3A__lore.kernel.org_linux-2Diio_20191106183536.123070-2D1-2Dstephan-40gerhold.net_&d=DwIDAg&c=WoJWtq5JV8YrKnzRxvD8NxmTP_1wxfE0prPmo0NeZwg&r=4jiDX_1brsSWfCjfA6Ovj1d4h9MF8q7Xk5aBwG28mVk&m=O82MQPnLTvlD0nxDzFW1KS3aZpWiI3qYUZwJUy_qqxc&s=ddvzqy0PywWDCnge7xbJIhpqN9NltbLrzi4EBVdeA_o&e=




---



 Documentation/devicetree/bindings/iio/imu/inv_mpu6050.txt | 1 +



 1 file changed, 1 insertion(+)







diff --git a/Documentation/devicetree/bindings/iio/imu/inv_mpu6050.txt b/Documentation/devicetree/bindings/iio/imu/inv_mpu6050.txt



index 268bf7568e19..c5ee8a20af9f 100644



--- a/Documentation/devicetree/bindings/iio/imu/inv_mpu6050.txt



+++ b/Documentation/devicetree/bindings/iio/imu/inv_mpu6050.txt



@@ -21,6 +21,7 @@ Required properties:



   bindings.



 



 Optional properties:



+ - vdd-supply: regulator phandle for VDD supply



  - vddio-supply: regulator phandle for VDDIO supply



  - mount-matrix: an optional 3x3 mounting rotation matrix



  - i2c-gate node.  These devices also support an auxiliary i2c bus.  This is



-- 



2.23.0








  parent reply	other threads:[~2019-11-08 12:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-07 18:43 [PATCH v2 1/2] dt-bindings: iio: imo: mpu6050: add vdd-supply Stephan Gerhold
2019-11-07 18:43 ` [PATCH v2 2/2] iio: imu: mpu6050: Add support for vdd-supply regulator Stephan Gerhold
2019-11-10 15:31   ` Jonathan Cameron
2019-11-08 12:11 ` Jean-Baptiste Maneyrol [this message]
2019-11-10 15:30   ` [PATCH v2 1/2] dt-bindings: iio: imo: mpu6050: add vdd-supply Jonathan Cameron
2019-11-10 15:28 ` Jonathan Cameron

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=MN2PR12MB33733917812945D0293D9D27C47B0@MN2PR12MB3373.namprd12.prod.outlook.com \
    --to=jmaneyrol@invensense.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=jonathan@marek.ca \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=masneyb@onstation.org \
    --cc=pmeerw@pmeerw.net \
    --cc=robh+dt@kernel.org \
    --cc=stephan@gerhold.net \
    /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).