All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Cercueil <paul@crapouillou.net>
To: neil.armstrong@linaro.org,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Sam Ravnborg <sam@ravnborg.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/panel: ld9040: Register a backlight device
Date: Wed, 05 Jul 2023 16:38:05 +0200	[thread overview]
Message-ID: <8e81dd5d9f62139e740ea123aa2087cb1bbcb04b.camel@crapouillou.net> (raw)
In-Reply-To: <194ac047-b20e-04c1-1d96-67cc483bb4a1@linaro.org>

Hi Neil,

Le mercredi 05 juillet 2023 à 15:57 +0200, Neil Armstrong a écrit :
> On 03/07/2023 23:47, Paul Cercueil wrote:
> > Register a backlight device to be able to switch between all the
> > gamma
> > levels.
> > 
> > Signed-off-by: Paul Cercueil <paul@crapouillou.net>
> > ---
> >   drivers/gpu/drm/panel/panel-samsung-ld9040.c | 40
> > ++++++++++++++++++++
> >   1 file changed, 40 insertions(+)
> > 
> > diff --git a/drivers/gpu/drm/panel/panel-samsung-ld9040.c
> > b/drivers/gpu/drm/panel/panel-samsung-ld9040.c
> > index 7fd9444b42c5..b4f87d6244cb 100644
> > --- a/drivers/gpu/drm/panel/panel-samsung-ld9040.c
> > +++ b/drivers/gpu/drm/panel/panel-samsung-ld9040.c
> > @@ -8,6 +8,7 @@
> >    * Andrzej Hajda <a.hajda@samsung.com>
> >   */
> >   
> > +#include <linux/backlight.h>
> >   #include <linux/delay.h>
> >   #include <linux/gpio/consumer.h>
> >   #include <linux/module.h>
> > @@ -311,8 +312,40 @@ static int ld9040_parse_dt(struct ld9040 *ctx)
> >         return 0;
> >   }
> >   
> > +static int ld9040_bl_update_status(struct backlight_device *dev)
> > +{
> > +       struct ld9040 *ctx = dev_get_drvdata(&dev->dev);
> > +
> > +       ctx->brightness = dev->props.brightness;
> > +       ld9040_brightness_set(ctx);
> > +
> > +       return 0;
> > +}
> > +
> > +static int ld9040_bl_get_intensity(struct backlight_device *dev)
> > +{
> > +       if (dev->props.fb_blank == FB_BLANK_UNBLANK &&
> > +                       dev->props.power == FB_BLANK_UNBLANK)
> > +               return dev->props.brightness;
> > +
> > +       return 0;
> > +}
> 
> You can totally drop the _get_brightness.

The current behaviour is to return 0 when the framebuffer is blanked. A
few drivers do that so I thought it was the norm; and the backlight
core doesn't do that by default (and just uses dev->props.brightness).

It is not clear to me if that's the preferred behaviour. The
"backlight_get_brightness" function in backlight.h seems to suggest
that the current behaviour is correct, unless it is not supposed to be
used in the backlight_ops.get_brightness() callback. Then in that case
some other drivers get it wrong too.

Cheers,
-Paul

> Neil
> 
> > +
> > +static const struct backlight_ops ld9040_bl_ops = {
> > +       .get_brightness = ld9040_bl_get_intensity,
> > +       .update_status  = ld9040_bl_update_status,
> > +};
> > +
> > +static const struct backlight_properties ld9040_bl_props = {
> > +       .type = BACKLIGHT_RAW,
> > +       .scale = BACKLIGHT_SCALE_NON_LINEAR,
> > +       .max_brightness = ARRAY_SIZE(ld9040_gammas) - 1,
> > +       .brightness = ARRAY_SIZE(ld9040_gammas) - 1,
> > +};
> > +
> >   static int ld9040_probe(struct spi_device *spi)
> >   {
> > +       struct backlight_device *bldev;
> >         struct device *dev = &spi->dev;
> >         struct ld9040 *ctx;
> >         int ret;
> > @@ -354,6 +387,13 @@ static int ld9040_probe(struct spi_device
> > *spi)
> >         drm_panel_init(&ctx->panel, dev, &ld9040_drm_funcs,
> >                        DRM_MODE_CONNECTOR_DPI);
> >   
> > +
> > +       bldev = devm_backlight_device_register(dev, dev_name(dev),
> > dev,
> > +                                              ctx, &ld9040_bl_ops,
> > +                                              &ld9040_bl_props);
> > +       if (IS_ERR(bldev))
> > +               return PTR_ERR(bldev);
> > +
> >         drm_panel_add(&ctx->panel);
> >   
> >         return 0;
> 


WARNING: multiple messages have this Message-ID (diff)
From: Paul Cercueil <paul@crapouillou.net>
To: neil.armstrong@linaro.org,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Sam Ravnborg <sam@ravnborg.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	 linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
	 dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/panel: ld9040: Register a backlight device
Date: Wed, 05 Jul 2023 16:38:05 +0200	[thread overview]
Message-ID: <8e81dd5d9f62139e740ea123aa2087cb1bbcb04b.camel@crapouillou.net> (raw)
In-Reply-To: <194ac047-b20e-04c1-1d96-67cc483bb4a1@linaro.org>

Hi Neil,

Le mercredi 05 juillet 2023 à 15:57 +0200, Neil Armstrong a écrit :
> On 03/07/2023 23:47, Paul Cercueil wrote:
> > Register a backlight device to be able to switch between all the
> > gamma
> > levels.
> > 
> > Signed-off-by: Paul Cercueil <paul@crapouillou.net>
> > ---
> >   drivers/gpu/drm/panel/panel-samsung-ld9040.c | 40
> > ++++++++++++++++++++
> >   1 file changed, 40 insertions(+)
> > 
> > diff --git a/drivers/gpu/drm/panel/panel-samsung-ld9040.c
> > b/drivers/gpu/drm/panel/panel-samsung-ld9040.c
> > index 7fd9444b42c5..b4f87d6244cb 100644
> > --- a/drivers/gpu/drm/panel/panel-samsung-ld9040.c
> > +++ b/drivers/gpu/drm/panel/panel-samsung-ld9040.c
> > @@ -8,6 +8,7 @@
> >    * Andrzej Hajda <a.hajda@samsung.com>
> >   */
> >   
> > +#include <linux/backlight.h>
> >   #include <linux/delay.h>
> >   #include <linux/gpio/consumer.h>
> >   #include <linux/module.h>
> > @@ -311,8 +312,40 @@ static int ld9040_parse_dt(struct ld9040 *ctx)
> >         return 0;
> >   }
> >   
> > +static int ld9040_bl_update_status(struct backlight_device *dev)
> > +{
> > +       struct ld9040 *ctx = dev_get_drvdata(&dev->dev);
> > +
> > +       ctx->brightness = dev->props.brightness;
> > +       ld9040_brightness_set(ctx);
> > +
> > +       return 0;
> > +}
> > +
> > +static int ld9040_bl_get_intensity(struct backlight_device *dev)
> > +{
> > +       if (dev->props.fb_blank == FB_BLANK_UNBLANK &&
> > +                       dev->props.power == FB_BLANK_UNBLANK)
> > +               return dev->props.brightness;
> > +
> > +       return 0;
> > +}
> 
> You can totally drop the _get_brightness.

The current behaviour is to return 0 when the framebuffer is blanked. A
few drivers do that so I thought it was the norm; and the backlight
core doesn't do that by default (and just uses dev->props.brightness).

It is not clear to me if that's the preferred behaviour. The
"backlight_get_brightness" function in backlight.h seems to suggest
that the current behaviour is correct, unless it is not supposed to be
used in the backlight_ops.get_brightness() callback. Then in that case
some other drivers get it wrong too.

Cheers,
-Paul

> Neil
> 
> > +
> > +static const struct backlight_ops ld9040_bl_ops = {
> > +       .get_brightness = ld9040_bl_get_intensity,
> > +       .update_status  = ld9040_bl_update_status,
> > +};
> > +
> > +static const struct backlight_properties ld9040_bl_props = {
> > +       .type = BACKLIGHT_RAW,
> > +       .scale = BACKLIGHT_SCALE_NON_LINEAR,
> > +       .max_brightness = ARRAY_SIZE(ld9040_gammas) - 1,
> > +       .brightness = ARRAY_SIZE(ld9040_gammas) - 1,
> > +};
> > +
> >   static int ld9040_probe(struct spi_device *spi)
> >   {
> > +       struct backlight_device *bldev;
> >         struct device *dev = &spi->dev;
> >         struct ld9040 *ctx;
> >         int ret;
> > @@ -354,6 +387,13 @@ static int ld9040_probe(struct spi_device
> > *spi)
> >         drm_panel_init(&ctx->panel, dev, &ld9040_drm_funcs,
> >                        DRM_MODE_CONNECTOR_DPI);
> >   
> > +
> > +       bldev = devm_backlight_device_register(dev, dev_name(dev),
> > dev,
> > +                                              ctx, &ld9040_bl_ops,
> > +                                              &ld9040_bl_props);
> > +       if (IS_ERR(bldev))
> > +               return PTR_ERR(bldev);
> > +
> >         drm_panel_add(&ctx->panel);
> >   
> >         return 0;
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Paul Cercueil <paul@crapouillou.net>
To: neil.armstrong@linaro.org,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Sam Ravnborg <sam@ravnborg.org>
Cc: devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] drm/panel: ld9040: Register a backlight device
Date: Wed, 05 Jul 2023 16:38:05 +0200	[thread overview]
Message-ID: <8e81dd5d9f62139e740ea123aa2087cb1bbcb04b.camel@crapouillou.net> (raw)
In-Reply-To: <194ac047-b20e-04c1-1d96-67cc483bb4a1@linaro.org>

Hi Neil,

Le mercredi 05 juillet 2023 à 15:57 +0200, Neil Armstrong a écrit :
> On 03/07/2023 23:47, Paul Cercueil wrote:
> > Register a backlight device to be able to switch between all the
> > gamma
> > levels.
> > 
> > Signed-off-by: Paul Cercueil <paul@crapouillou.net>
> > ---
> >   drivers/gpu/drm/panel/panel-samsung-ld9040.c | 40
> > ++++++++++++++++++++
> >   1 file changed, 40 insertions(+)
> > 
> > diff --git a/drivers/gpu/drm/panel/panel-samsung-ld9040.c
> > b/drivers/gpu/drm/panel/panel-samsung-ld9040.c
> > index 7fd9444b42c5..b4f87d6244cb 100644
> > --- a/drivers/gpu/drm/panel/panel-samsung-ld9040.c
> > +++ b/drivers/gpu/drm/panel/panel-samsung-ld9040.c
> > @@ -8,6 +8,7 @@
> >    * Andrzej Hajda <a.hajda@samsung.com>
> >   */
> >   
> > +#include <linux/backlight.h>
> >   #include <linux/delay.h>
> >   #include <linux/gpio/consumer.h>
> >   #include <linux/module.h>
> > @@ -311,8 +312,40 @@ static int ld9040_parse_dt(struct ld9040 *ctx)
> >         return 0;
> >   }
> >   
> > +static int ld9040_bl_update_status(struct backlight_device *dev)
> > +{
> > +       struct ld9040 *ctx = dev_get_drvdata(&dev->dev);
> > +
> > +       ctx->brightness = dev->props.brightness;
> > +       ld9040_brightness_set(ctx);
> > +
> > +       return 0;
> > +}
> > +
> > +static int ld9040_bl_get_intensity(struct backlight_device *dev)
> > +{
> > +       if (dev->props.fb_blank == FB_BLANK_UNBLANK &&
> > +                       dev->props.power == FB_BLANK_UNBLANK)
> > +               return dev->props.brightness;
> > +
> > +       return 0;
> > +}
> 
> You can totally drop the _get_brightness.

The current behaviour is to return 0 when the framebuffer is blanked. A
few drivers do that so I thought it was the norm; and the backlight
core doesn't do that by default (and just uses dev->props.brightness).

It is not clear to me if that's the preferred behaviour. The
"backlight_get_brightness" function in backlight.h seems to suggest
that the current behaviour is correct, unless it is not supposed to be
used in the backlight_ops.get_brightness() callback. Then in that case
some other drivers get it wrong too.

Cheers,
-Paul

> Neil
> 
> > +
> > +static const struct backlight_ops ld9040_bl_ops = {
> > +       .get_brightness = ld9040_bl_get_intensity,
> > +       .update_status  = ld9040_bl_update_status,
> > +};
> > +
> > +static const struct backlight_properties ld9040_bl_props = {
> > +       .type = BACKLIGHT_RAW,
> > +       .scale = BACKLIGHT_SCALE_NON_LINEAR,
> > +       .max_brightness = ARRAY_SIZE(ld9040_gammas) - 1,
> > +       .brightness = ARRAY_SIZE(ld9040_gammas) - 1,
> > +};
> > +
> >   static int ld9040_probe(struct spi_device *spi)
> >   {
> > +       struct backlight_device *bldev;
> >         struct device *dev = &spi->dev;
> >         struct ld9040 *ctx;
> >         int ret;
> > @@ -354,6 +387,13 @@ static int ld9040_probe(struct spi_device
> > *spi)
> >         drm_panel_init(&ctx->panel, dev, &ld9040_drm_funcs,
> >                        DRM_MODE_CONNECTOR_DPI);
> >   
> > +
> > +       bldev = devm_backlight_device_register(dev, dev_name(dev),
> > dev,
> > +                                              ctx, &ld9040_bl_ops,
> > +                                              &ld9040_bl_props);
> > +       if (IS_ERR(bldev))
> > +               return PTR_ERR(bldev);
> > +
> >         drm_panel_add(&ctx->panel);
> >   
> >         return 0;
> 


  reply	other threads:[~2023-07-05 14:38 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03 21:47 [PATCH 0/3] Galaxy S2 (i9100) panel updates Paul Cercueil
2023-07-03 21:47 ` Paul Cercueil
2023-07-03 21:47 ` Paul Cercueil
2023-07-03 21:47 ` [PATCH 1/3] drm/panel: ld9040: Use better magic values Paul Cercueil
2023-07-03 21:47   ` Paul Cercueil
2023-07-03 21:47   ` Paul Cercueil
2023-07-05 13:55   ` Neil Armstrong
2023-07-05 13:55     ` Neil Armstrong
2023-07-05 13:55     ` Neil Armstrong
2023-07-03 21:47 ` [PATCH 2/3] drm/panel: ld9040: Register a backlight device Paul Cercueil
2023-07-03 21:47   ` Paul Cercueil
2023-07-03 21:47   ` Paul Cercueil
2023-07-03 23:49   ` 대인기/Tizen Platform Lab(SR)/삼성전자
2023-07-03 23:49     ` 대인기/Tizen Platform Lab(SR)/삼성전자
2023-07-03 23:49     ` 대인기/Tizen Platform Lab(SR)/삼성전자
2023-07-05  9:38     ` Paul Cercueil
2023-07-05  9:38       ` Paul Cercueil
2023-07-05  9:38       ` Paul Cercueil
2023-07-05 13:57   ` Neil Armstrong
2023-07-05 13:57     ` Neil Armstrong
2023-07-05 13:57     ` Neil Armstrong
2023-07-05 14:38     ` Paul Cercueil [this message]
2023-07-05 14:38       ` Paul Cercueil
2023-07-05 14:38       ` Paul Cercueil
2023-07-05 17:39       ` Sam Ravnborg
2023-07-05 17:39         ` Sam Ravnborg
2023-07-05 17:39         ` Sam Ravnborg
2023-07-05 17:45   ` Sam Ravnborg
2023-07-05 17:45     ` Sam Ravnborg
2023-07-05 17:45     ` Sam Ravnborg
2023-07-03 21:47 ` [PATCH 3/3] ARM: dts: exynos/i9100: Fix LCD screen's physical size Paul Cercueil
2023-07-03 21:47   ` Paul Cercueil
2023-07-03 21:47   ` Paul Cercueil

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=8e81dd5d9f62139e740ea123aa2087cb1bbcb04b.camel@crapouillou.net \
    --to=paul@crapouillou.net \
    --cc=alim.akhtar@samsung.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=sam@ravnborg.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.