linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Nikolaus Schaller" <hns@goldelico.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, letux-kernel@openphoenux.org,
	kernel@pyra-handheld.com
Subject: Re: [PATCH 2/2] dt-bindings: iio: add Bosch BMG160 gyroscope sensor
Date: Thu, 28 Mar 2019 17:29:15 +0100	[thread overview]
Message-ID: <55464EC0-7031-42BD-A6E0-6E04E3A45FE8@goldelico.com> (raw)
In-Reply-To: <20190324180654.44289894@archlinux>


> Am 24.03.2019 um 19:06 schrieb Jonathan Cameron <jic23@kernel.org>:
> 
> On Mon, 18 Mar 2019 16:14:15 +0100
> "H. Nikolaus Schaller" <hns@goldelico.com> wrote:
> 
>> Define bindings for "bosch,bmg160" and "bosch,bmi055_gyro".
>> 
>> Signed-off-by: H. Nikolaus Schaller <hns@goldelico.com>
> Simple binding so applied to the togreg branch of iio.git and pushed out as
> testing. Still time for a devicetree ack (or to pull it ;) if anyone has
> time to look.

It is more or less an adapation of the bma180 bindings.

> 
> Thanks,
> 
> Jonathan
> 
>> ---
>> .../bindings/iio/gyroscope/bmg160.txt         | 20 +++++++++++++++++++
>> 1 file changed, 20 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/iio/gyroscope/bmg160.txt
>> 
>> diff --git a/Documentation/devicetree/bindings/iio/gyroscope/bmg160.txt b/Documentation/devicetree/bindings/iio/gyroscope/bmg160.txt
>> new file mode 100644
>> index 000000000000..78e18a1e9c1d
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/iio/gyroscope/bmg160.txt
>> @@ -0,0 +1,20 @@
>> +* Bosch BMG160 triaxial rotation sensor (gyroscope)
>> +
>> +Required properties:
>> +
>> +  - compatible : should be "bosch,bmg160" or "bosch,bmi055_gyro"
>> +  - reg : the I2C address of the sensor (0x69)
>> +
>> +Optional properties:
>> +
>> +  - interrupts : interrupt mapping for GPIO IRQ, it should by configured with
>> +		flags IRQ_TYPE_EDGE_RISING
>> +
>> +Example:
>> +
>> +bmg160@69 {
>> +	compatible = "bosch,bmg160";
>> +	reg = <0x69>;
>> +	interrupt-parent = <&gpio6>;
>> +	interrupts = <18 (IRQ_TYPE_EDGE_RISING)>;
>> +};
> 


  reply	other threads:[~2019-03-28 16:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18 15:14 [PATCH 0/2] iio: gyro: bmg160 add device tree support H. Nikolaus Schaller
2019-03-18 15:14 ` [PATCH 1/2] iio: gyro: bmg160: add device tree compatibility table H. Nikolaus Schaller
2019-03-24 18:05   ` Jonathan Cameron
2019-03-28 16:25     ` H. Nikolaus Schaller
2019-03-18 15:14 ` [PATCH 2/2] dt-bindings: iio: add Bosch BMG160 gyroscope sensor H. Nikolaus Schaller
2019-03-24 18:06   ` Jonathan Cameron
2019-03-28 16:29     ` H. Nikolaus Schaller [this message]
2019-03-31  6:40   ` Rob Herring

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=55464EC0-7031-42BD-A6E0-6E04E3A45FE8@goldelico.com \
    --to=hns@goldelico.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=kernel@pyra-handheld.com \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=letux-kernel@openphoenux.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pmeerw@pmeerw.net \
    --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).