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>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	"H. Nikolaus Schaller" <hns@goldelico.com>
Cc: 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: [PATCH 0/2] iio: gyro: bmg160 add device tree support
Date: Mon, 18 Mar 2019 16:14:13 +0100	[thread overview]
Message-ID: <cover.1552922054.git.hns@goldelico.com> (raw)

There is no device tree support since the of_device_id table is missing.

H. Nikolaus Schaller (2):
  iio: gyro: bmg160: add device tree compatibility table
  dt-bindings: iio: add Bosch BMG160 gyroscope sensor

 .../bindings/iio/gyroscope/bmg160.txt         | 20 +++++++++++++++++++
 drivers/iio/gyro/bmg160_i2c.c                 |  9 +++++++++
 2 files changed, 29 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/iio/gyroscope/bmg160.txt

-- 
2.19.1


             reply	other threads:[~2019-03-18 15:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18 15:14 H. Nikolaus Schaller [this message]
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
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=cover.1552922054.git.hns@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).