From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3] media: i2c/adp1653: devicetree support for adp1653
Date: Sun, 18 Jan 2015 23:02:10 +0100 [thread overview]
Message-ID: <20150118220210.GA7481@amd> (raw)
In-Reply-To: <20150104094352.GA3790@amd>
On Sun 2015-01-04 10:43:52, Pavel Machek wrote:
>
> We are moving to device tree support on OMAP3, but that currently
> breaks ADP1653 driver. This adds device tree support, plus required
> documentation.
>
> Signed-off-by: Pavel Machek <pavel@ucw.cz>
Sakari? You are listed as adp1653 maintainer. Did you apply the patch?
Is it going to be in 3.20?
Thanks,
Pavel
> ---
>
> Please apply,
> Pavel
>
> diff --git a/Documentation/devicetree/bindings/media/i2c/adp1653.txt b/Documentation/devicetree/bindings/media/i2c/adp1653.txt
> new file mode 100644
> index 0000000..0fc28a9
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/i2c/adp1653.txt
> @@ -0,0 +1,37 @@
> +* Analog Devices ADP1653 flash LED driver
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-01-18 22:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 21:46 [PATCH] media: i2c/adp1653: devicetree support for adp1653 Pavel Machek
2014-12-23 17:23 ` Mauro Carvalho Chehab
2014-12-23 20:49 ` Pavel Machek
2014-12-24 22:35 ` Pavel Machek
2014-12-24 22:34 ` [PATCHv2] " Pavel Machek
2014-12-26 19:02 ` Rob Herring
2014-12-26 20:33 ` Pavel Machek
2014-12-26 20:52 ` Rob Herring
2014-12-30 13:57 ` Sakari Ailus
2015-01-04 9:00 ` Pavel Machek
2015-01-04 9:43 ` [PATCHv3] " Pavel Machek
2015-01-18 22:02 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-04-02 14:38 Pavel Machek
2015-04-02 16:14 ` Sakari Ailus
2015-04-02 20:30 ` Pavel Machek
2015-04-02 23:48 ` Sakari Ailus
2015-04-03 8:23 ` Pavel Machek
2015-04-03 11:23 ` Sakari Ailus
2015-04-03 20:29 ` Pavel Machek
2015-04-03 21:35 ` Sakari Ailus
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=20150118220210.GA7481@amd \
--to=pavel@ucw.cz \
--cc=linux-arm-kernel@lists.infradead.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).