From: Wolfram Sang <wsa@the-dreams.de>
To: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
Cc: Andy Yan <andy.yan@rock-chips.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Shawn Guo <shawn.guo@linaro.org>,
devicetree@vger.kernel.org, linux-media@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH 1/3] staging: imx-drm: document internal HDMI I2C master controller DT binding
Date: Tue, 2 Dec 2014 14:21:59 +0100 [thread overview]
Message-ID: <20141202132158.GD4072@katana> (raw)
In-Reply-To: <547DBA99.1010703@mentor.com>
[-- Attachment #1: Type: text/plain, Size: 803 bytes --]
> Thank you for references.
Yes, thank you all. Really great to see this consolidation effort going
on!
> I'll try to review all out of i2c/busses/* registered i2c adapters, may
> be there is something in common between all of them.
Yay, cool! Thanks!
> I'll prepare the change of the HDMI DDC support for review (will be able
> to test it only on iMX6), Wolfram, please skip from your consideration
> the published version of the i2c bus driver.
Okay, will do.
> Wolfram, by the way is I2C_CLASS_DDC adapter class in operational use or
> deprecated?
Class based instantiation is NOT deprecated and will stay as far as I
can see. Many platform bus drivers did set the class flag needlessly, so
we had a deprecation mechanism to get rid of those flags in drivers in
order to speed up boot time.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-12-02 13:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1416073759-19939-1-git-send-email-vladimir_zapolskiy@mentor.com>
2014-11-15 17:49 ` [PATCH 1/3] staging: imx-drm: document internal HDMI I2C master controller DT binding Vladimir Zapolskiy
2014-12-01 14:54 ` Vladimir Zapolskiy
2014-12-01 15:11 ` Philipp Zabel
2014-12-01 15:39 ` Vladimir Zapolskiy
2014-12-01 16:22 ` Philipp Zabel
2014-12-02 6:36 ` Andy Yan
2014-12-02 13:11 ` Vladimir Zapolskiy
2014-12-02 13:21 ` Wolfram Sang [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=20141202132158.GD4072@katana \
--to=wsa@the-dreams.de \
--cc=andy.yan@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=shawn.guo@linaro.org \
--cc=vladimir_zapolskiy@mentor.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