From: Andi Shyti <andi@etezian.org>
To: Rob Herring <robh@kernel.org>
Cc: Andi Shyti <andi.shyti@samsung.com>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, Andi Shyti <andi@etezian.org>
Subject: Re: [PATCH] [media] rc: ir-spi: add support for IR LEDs connected with SPI
Date: Wed, 6 Jul 2016 00:08:26 +0900 [thread overview]
Message-ID: <20160705150826.GG1257@jack.zhora.eu> (raw)
In-Reply-To: <20160705142211.GA19930@rob-hp-laptop>
Hi Rob,
> > The ir-spi is a simple device driver which supports the
> > connection between an IR LED and the MOSI line of an SPI device.
>
> Please split the binding from the driver.
OK!
> > +Device tree bindings for IR LED connected through SPI bus which is used as
> > +remote controller.
>
> Do said devices have part numbers? Seems kind of generic and I've never
> seen such device.
No, it doesn't, this is a simple irled driven by the SPI MOSI
line that works as a remote controller.
It looked strange to me as well when I heard of it the first
time, but it will be present in the upcoming tm2/tm2e patchset
(i.e. Samsung Note 4 and Note 4 edge).
> > +Optional properties:
> > + - irled,switch: specifies the gpio switch which enables the irled
>
> Just "switch-gpios"
OK!
> > + controller-data {
>
> This is part of the controller binding? Omit that from the example.
OK!
Thanks,
Andi
prev parent reply other threads:[~2016-07-05 15:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 8:33 [PATCH] [media] rc: ir-spi: add support for IR LEDs connected with SPI Andi Shyti
2016-07-01 9:44 ` Sean Young
2016-07-01 12:30 ` Andi Shyti
2016-07-01 13:22 ` Sean Young
2016-07-01 14:00 ` Andi Shyti
2016-07-02 4:03 ` kbuild test robot
[not found] ` <1467362022-12704-1-git-send-email-andi.shyti-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2016-07-02 4:50 ` kbuild test robot
2016-07-05 14:22 ` Rob Herring
2016-07-05 15:08 ` Andi Shyti [this message]
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=20160705150826.GG1257@jack.zhora.eu \
--to=andi@etezian.org \
--cc=andi.shyti@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@osg.samsung.com \
--cc=robh@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).