From: Lucas Stach <l.stach@pengutronix.de>
To: Daniel Thompson <daniel.thompson@linaro.org>,
Lee Jones <lee.jones@linaro.org>,
Jingoo Han <jingoohan1@gmail.com>
Cc: linux-fbdev@vger.kernel.org, kernel@pengutronix.de,
dri-devel@lists.freedesktop.org, patchwork-lst@pengutronix.de
Subject: Re: [PATCH] backlight: rave-sp: don't touch initial state and register with correct device
Date: Thu, 02 May 2019 12:01:45 +0000 [thread overview]
Message-ID: <1556798505.2590.7.camel@pengutronix.de> (raw)
In-Reply-To: <c23ecabd-c2ee-8c23-9ee3-13290bc4da35@linaro.org>
Hi Daniel,
Am Donnerstag, den 02.05.2019, 11:33 +0100 schrieb Daniel Thompson:
> On 29/04/2019 16:29, Lucas Stach wrote:
> > This way the backlight can be referenced through its device node and
> > enabling/disabling can be managed through the panel driver.
>
> Is it possible to implement something similar to
> pwm_backlight_initial_power_state() to handle this?
I'm not aware of any protocol to the RAVE-SP that would allow to read
back the backlight state. AFAICS the backlight is implemented as a
unidirectional protocol.
Regards,
Lucas
> backlight drivers already suffer from too much diversity so I prefer
> things like this to align behaviour with the (fairly heavilyly used) PWM
> driver if possible.
>
>
> Daniel.
>
>
> > > > Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> > ---
> > drivers/video/backlight/rave-sp-backlight.c | 4 +---
> > 1 file changed, 1 insertion(+), 3 deletions(-)
> >
> > diff --git a/drivers/video/backlight/rave-sp-backlight.c b/drivers/video/backlight/rave-sp-backlight.c
> > index 462f14a1b19d..d296bfcf4396 100644
> > --- a/drivers/video/backlight/rave-sp-backlight.c
> > +++ b/drivers/video/backlight/rave-sp-backlight.c
> > @@ -48,15 +48,13 @@ static int rave_sp_backlight_probe(struct platform_device *pdev)
> > > > struct device *dev = &pdev->dev;
> > > > struct backlight_device *bd;
> >
> > > > - bd = devm_backlight_device_register(dev, pdev->name, dev->parent,
> > > > + bd = devm_backlight_device_register(dev, pdev->name, dev,
> > > > dev_get_drvdata(dev->parent),
> > > > &rave_sp_backlight_ops,
> > > > &rave_sp_backlight_props);
> > > > if (IS_ERR(bd))
> > > > return PTR_ERR(bd);
> >
> > > > - backlight_update_status(bd);
> > -
> > > > return 0;
> > }
> >
> >
>
>
next prev parent reply other threads:[~2019-05-02 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 15:29 [PATCH] backlight: rave-sp: don't touch initial state and register with correct device Lucas Stach
2019-05-02 10:33 ` Daniel Thompson
2019-05-02 12:01 ` Lucas Stach [this message]
2019-05-03 13:29 ` Daniel Thompson
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=1556798505.2590.7.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=daniel.thompson@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jingoohan1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=lee.jones@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=patchwork-lst@pengutronix.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).