From: "Paweł Chmiel" <pawel.mikolaj.chmiel@gmail.com>
To: mchehab@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com
Cc: hverkuil@xs4all.nl, fischerdouglasc@gmail.com,
	keescook@chromium.org, linux-media@vger.kernel.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	"Paweł Chmiel" <pawel.mikolaj.chmiel@gmail.com>
Subject: [PATCH v2 0/4] media: radio-si470x-i2c: Add device tree and reset gpio support
Date: Fri,  7 Dec 2018 14:58:08 +0100	[thread overview]
Message-ID: <20181207135812.12842-1-pawel.mikolaj.chmiel@gmail.com> (raw)
This patchset adds support for device tree and reset-gpios
to si470x i2c radio driver.
First two patches adds and documents device tree support.
Third patch simplifies code by using managed resource helpers.
Last two patches adds and documents new optional reset gpios support.
It was tested on Samsung Galaxy S (i9000) phone.
Changes from v1:
  - squashed patches adding/modifying dt-bindings into one patch
Paweł Chmiel (4):
  si470x-i2c: Add device tree support
  si470x-i2c: Use managed resource helpers
  si470x-i2c: Add optional reset-gpio support
  media: dt-bindings: Add binding for si470x radio
 .../devicetree/bindings/media/si470x.txt      | 26 ++++++++++
 drivers/media/radio/si470x/radio-si470x-i2c.c | 52 ++++++++++++-------
 drivers/media/radio/si470x/radio-si470x.h     |  1 +
 3 files changed, 61 insertions(+), 18 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/media/si470x.txt
-- 
2.17.1
next             reply	other threads:[~2018-12-07 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-07 13:58 Paweł Chmiel [this message]
2018-12-07 13:58 ` [PATCH v2 1/4] si470x-i2c: Add device tree support Paweł Chmiel
2018-12-07 13:58 ` [PATCH v2 2/4] si470x-i2c: Use managed resource helpers Paweł Chmiel
2018-12-07 13:58 ` [PATCH v2 3/4] si470x-i2c: Add optional reset-gpio support Paweł Chmiel
2018-12-07 13:58 ` [PATCH v2 4/4] media: dt-bindings: Add binding for si470x radio Paweł Chmiel
2018-12-18 16:13   ` 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=20181207135812.12842-1-pawel.mikolaj.chmiel@gmail.com \
    --to=pawel.mikolaj.chmiel@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fischerdouglasc@gmail.com \
    --cc=hverkuil@xs4all.nl \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mchehab@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).