From: Lucas Stach <l.stach@pengutronix.de>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Vladimir Zapolskiy <vz@mleia.com>,
patchwork-lst@pengutronix.de, linux-i2c@vger.kernel.org,
kernel@pengutronix.de
Subject: Re: [PATCH] i2c: core: don't try to OF populate DDC i2c buses
Date: Fri, 13 Jan 2017 11:14:46 +0100 [thread overview]
Message-ID: <1484302486.30810.26.camel@pengutronix.de> (raw)
In-Reply-To: <20161211221622.GJ2552@katana>
Am Sonntag, den 11.12.2016, 23:16 +0100 schrieb Wolfram Sang:
> Lucas,
>
> > Shallow review of DTS files and dpaux drivers let me say that the change
> > below has no regressions (the change is untested):
> >
> > diff --git a/drivers/gpu/drm/drm_dp_helper.c b/drivers/gpu/drm/drm_dp_helper.c
> > index 3e6fe82..f91ade1 100644
> > --- a/drivers/gpu/drm/drm_dp_helper.c
> > +++ b/drivers/gpu/drm/drm_dp_helper.c
> > @@ -1020,7 +1020,6 @@ int drm_dp_aux_register(struct drm_dp_aux *aux)
> > aux->ddc.class = I2C_CLASS_DDC;
> > aux->ddc.owner = THIS_MODULE;
> > aux->ddc.dev.parent = aux->dev;
> > - aux->ddc.dev.of_node = aux->dev->of_node;
> >
> > strlcpy(aux->ddc.name, aux->name ? aux->name : dev_name(aux->dev),
> > sizeof(aux->ddc.name));
>
> Is this an acceptable approach? It makes sense to me from an I2C PoV.
>
> I have to say that I second Vladimir's arguments. There shouldn't be any
> other I2C devices on DDC, but surely there is somebody somewhere hacking
> this bus to do something.
Yes, I've convinced myself that this is the better way.
Please drop this patch.
Regards,
Lucas
prev parent reply other threads:[~2017-01-13 10:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 11:50 [PATCH] i2c: core: don't try to OF populate DDC i2c buses Lucas Stach
2016-11-30 13:21 ` Uwe Kleine-König
2016-11-30 13:54 ` Vladimir Zapolskiy
2016-11-30 14:06 ` Lucas Stach
2016-11-30 20:18 ` Vladimir Zapolskiy
2016-12-01 10:07 ` Lucas Stach
2016-12-01 12:23 ` Vladimir Zapolskiy
2016-12-11 22:16 ` Wolfram Sang
2017-01-13 10:14 ` Lucas Stach [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=1484302486.30810.26.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=linux-i2c@vger.kernel.org \
--cc=patchwork-lst@pengutronix.de \
--cc=vz@mleia.com \
--cc=wsa@the-dreams.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).