From: Wolfram Sang <wsa@the-dreams.de>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Tristan Bastian <tristan-c.bastian@gmx.de>,
Vlado Plaga <rechner@vlado-do.de>,
dri-devel@lists.freedesktop.org, Rob Herring <robh+dt@kernel.org>,
linux-i2c@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v2] i2c: of: Try to find an I2C adapter matching the parent
Date: Tue, 5 Feb 2019 13:44:44 +0100 [thread overview]
Message-ID: <20190205124443.GF1045@kunai> (raw)
In-Reply-To: <20190125131142.26837-1-thierry.reding@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1160 bytes --]
On Fri, Jan 25, 2019 at 02:11:42PM +0100, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> If an I2C adapter doesn't match the provided device tree node, also try
> matching the parent's device tree node. This allows finding an adapter
> based on the device node of the parent device that was used to register
> it.
>
> This fixes a regression on Tegra124-based Chromebooks (Nyan) where the
> eDP controller registers an I2C adapter that is used to read to EDID.
> After commit 993a815dcbb2 ("dt-bindings: panel: Add missing .txt
> suffix") this stopped working because the I2C adapter could no longer
> be found. The approach in this patch fixes the regression without
> introducing the issues that the above commit solved.
>
> Fixes: 17ab7806de0c ("drm: don't link DP aux i2c adapter to the hardware device node")
> Signed-off-by: Thierry Reding <treding@nvidia.com>
Removed the duplicated Tested-by and applied to for-next, thanks!
I applied to -next because I want this core change more regression
testing in next. If this goes good, I will do a cleanup series to not
use the of_node of the parent twice.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-02-05 12:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 13:11 [PATCH v2] i2c: of: Try to find an I2C adapter matching the parent Thierry Reding
2019-01-26 12:37 ` Tristan Bastian
2019-01-28 8:08 ` Thierry Reding
2019-01-28 8:10 ` Thierry Reding
2019-01-28 9:19 ` Tristan Bastian
2019-01-28 9:26 ` Tristan Bastian
2019-02-05 12:44 ` Wolfram Sang [this message]
2019-02-06 9:38 ` Wolfram Sang
2019-02-06 9:49 ` Wolfram Sang
2019-02-06 12:07 ` Thierry Reding
2019-02-08 18:35 ` Wolfram Sang
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=20190205124443.GF1045@kunai \
--to=wsa@the-dreams.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rechner@vlado-do.de \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=tristan-c.bastian@gmx.de \
/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).