From: Krzysztof Kozlowski <krzk@kernel.org>
To: Andi Shyti <andi.shyti@samsung.com>
Cc: Javier Martinez Canillas <javier@osg.samsung.com>,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Andi Shyti <andi@etezian.org>
Subject: Re: [PATCH v2] arm64: dts: Enable ir-spi in the tm2 and tm2e boards
Date: Fri, 10 Feb 2017 15:43:45 +0200 [thread overview]
Message-ID: <20170210134345.okrgdxckrl3vilnw@kozik-lap> (raw)
In-Reply-To: <20170210022238.12401-1-andi.shyti@samsung.com>
On Fri, Feb 10, 2017 at 11:22:38AM +0900, Andi Shyti wrote:
> Add the device tree node for the ir-spi driver which enable the
> ir led for remote controlling.
>
> This patch sets first the GPR3[3] gpio line as a regulator-fixed
> for enabling an external regulator which powers the IR LED.
>
> Removes also the default assignment of GPG3[7] related to the
> MOSI line of the SPI3 bus.
>
> Signed-off-by: Andi Shyti <andi.shyti@samsung.com>
> ---
> Changelog v1 -> v2
> ==================
> v1: https://marc.info/?l=linux-kernel&m=148645523229894&w=2
>
> - used 'GPIO_ACTIVE_HIGH' instead of '0'
> - added back the gpg3-5 gpio initialization related to the SPI3
> CS line that was erroneously removed
>
> .../boot/dts/exynos/exynos5433-tm2-common.dtsi | 26 +++++++++++++++++++++-
> 1 file changed, 25 insertions(+), 1 deletion(-)
>
Looks fine. I'll apply after v4.11-rc1 merge window.
Best regards,
Krzysztof
next prev parent reply other threads:[~2017-02-10 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170210022252epcas1p2cad2a32fb74a5ecc17ed73387579c6ab@epcas1p2.samsung.com>
2017-02-10 2:22 ` [PATCH v2] arm64: dts: Enable ir-spi in the tm2 and tm2e boards Andi Shyti
2017-02-10 13:43 ` Krzysztof Kozlowski [this message]
2017-02-10 14:04 ` Javier Martinez Canillas
2017-02-11 4:44 ` Andi Shyti
2017-02-13 11:55 ` Javier Martinez Canillas
2017-03-07 19:22 ` Krzysztof Kozlowski
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=20170210134345.okrgdxckrl3vilnw@kozik-lap \
--to=krzk@kernel.org \
--cc=andi.shyti@samsung.com \
--cc=andi@etezian.org \
--cc=javier@osg.samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.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).