From: "Heiko Stübner" <heiko@sntech.de>
To: Douglas Anderson <dianders@chromium.org>
Cc: linux-rockchip@lists.infradead.org, ykk@rock-chips.com,
mark.yao@rock-chips.com, briannorris@chromium.org,
amstan@chromium.org, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, linux@arm.linux.org.uk,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: Add the hdmi-ddc pinctrl settings for rk3288
Date: Sun, 13 Sep 2015 13:32:34 +0200 [thread overview]
Message-ID: <1460847.PVSDMeWNWs@diego> (raw)
In-Reply-To: <1441230862-17376-1-git-send-email-dianders@chromium.org>
Am Mittwoch, 2. September 2015, 14:54:22 schrieb Douglas Anderson:
> The pins for i2c5 can either be configured as "I2C5" which means that
> they're controlled by the normal RK3288 I2C controller or as "EDP / HDMI
> I2C". It's unclear why EDP is referenced here since apparently setting
> the mux to this position enables I2C communication using the dw_hdmi
> block with a patch like <https://patchwork.kernel.org/patch/7098101/>.
>
> There appear to be some reasons why using the builtin I2C controller in
> dw_hdmi is better than using the normal RK3288 I2C controller, so boards
> based on rk3288 might eventually want to use this pinmux if it's known
> to work.
>
> Once driver support in dw_hdmi lands, boards would use this by selecting
> this pinctrl for the HDMI block and then _not_ specifying a ddc-i2c-bus
> and _not_ setting the status to "okay" for i2c5 (which uses the same
> pins).
>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
applied to my dts branch for 4.4
Thanks
Heiko
prev parent reply other threads:[~2015-09-13 11:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 21:54 [PATCH] ARM: dts: Add the hdmi-ddc pinctrl settings for rk3288 Douglas Anderson
2015-09-13 11:32 ` Heiko Stübner [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=1460847.PVSDMeWNWs@diego \
--to=heiko@sntech.de \
--cc=amstan@chromium.org \
--cc=briannorris@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mark.yao@rock-chips.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=ykk@rock-chips.com \
/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).