[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAGXv+5HcU6paJJzm4nLe6mmSYUaR-pp5LBsy9aev0RRX+FKmcg@mail.gmail.com>
Date: Tue, 12 Jul 2022 17:41:00 +0800
From: Chen-Yu Tsai <wenst@...omium.org>
To: Robert Foss <robert.foss@...aro.org>
Cc: allen <allen.chen@....com.tw>,
Kenneth Hung <Kenneth.Hung@....com.tw>,
Jau-Chih Tseng <Jau-Chih.Tseng@....com.tw>,
David Airlie <airlied@...ux.ie>,
"open list:DRM DRIVERS" <dri-devel@...ts.freedesktop.org>,
Pin-yen Lin <treapking@...gle.com>,
open list <linux-kernel@...r.kernel.org>,
Jernej Skrabec <jernej.skrabec@...il.com>,
Neil Armstrong <narmstrong@...libre.com>,
Pin-Yen Lin <treapking@...omium.org>,
Hermes Wu <Hermes.Wu@....com.tw>,
Laurent Pinchart <Laurent.pinchart@...asonboard.com>,
Andrzej Hajda <andrzej.hajda@...el.com>,
Jonas Karlman <jonas@...boo.se>
Subject: Re: [PATCH 1/3] drm/bridge: it6505: Modified power sequence
On Tue, Jul 12, 2022 at 4:08 PM Robert Foss <robert.foss@...aro.org> wrote:
>
> Hi Allen,
>
> On Thu, 7 Jul 2022 at 10:06, allen <allen.chen@....com.tw> wrote:
> >
> > From: allen chen <allen.chen@....com.tw>
> >
> > Change power sequence to meet it6505 data sheet requirement when boot on.
> >
> > Signed-off-by: Pin-Yen Lin <treapking@...omium.org>
> > Signed-off-by: Allen Chen <allen.chen@....com.tw>
> >
> > ---
> > drivers/gpu/drm/bridge/ite-it6505.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/bridge/ite-it6505.c b/drivers/gpu/drm/bridge/ite-it6505.c
> > index 2d119e3016b3..aa5e0aa1af85 100644
> > --- a/drivers/gpu/drm/bridge/ite-it6505.c
> > +++ b/drivers/gpu/drm/bridge/ite-it6505.c
> > @@ -3029,7 +3029,7 @@ static int it6505_init_pdata(struct it6505 *it6505)
> > return PTR_ERR(pdata->ovdd);
> > }
> >
> > - pdata->gpiod_reset = devm_gpiod_get(dev, "reset", GPIOD_OUT_HIGH);
> > + pdata->gpiod_reset = devm_gpiod_get(dev, "reset", GPIOD_OUT_LOW);
>
> Making this change is problematic since it requires a corresponding
> change in all of the device trees that use this device. It's against
> policy to change this interface after it has been introduced.
>
> Unless anyone thinks otherwise, I would like to see this patch dropped.
I think you're confusing GPIO_ACTIVE_{LOW,HIGH} flags in the device tree
vs GPIOD_OUT_{LOW,HIGH}, which just sets the "default" state the GPIO
should be in when it is requested.
This change doesn't impact the device tree.
Regards
ChenYu
> > if (IS_ERR(pdata->gpiod_reset)) {
> > dev_err(dev, "gpiod_reset gpio not found");
> > return PTR_ERR(pdata->gpiod_reset);
> > --
> > 2.25.1
> >
Powered by blists - more mailing lists