All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime@cerno.tech>
To: Marek Vasut <marex@denx.de>
Cc: Christoph Niedermaier <cniedermaier@dh-electronics.com>,
	Max Krummenacher <max.krummenacher@toradex.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Max Krummenacher <max.oss.09@gmail.com>,
	David Airlie <airlied@linux.ie>, Sam Ravnborg <sam@ravnborg.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	dri-devel@lists.freedesktop.org,
	DenysDrozdov <denys.drozdov@toradex.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Shawn Guo <shawnguo@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	NXP Linux Team <linux-imx@nxp.com>
Subject: Re: [RFC PATCH] drm/panel: simple: panel-dpi: use bus-format to set bpc and bus_format
Date: Wed, 23 Feb 2022 14:47:57 +0100	[thread overview]
Message-ID: <20220223134757.f5upi2iun27op5w5@houat> (raw)
In-Reply-To: <b5f471f4-0712-b798-efb8-b5b481cdb898@denx.de>

[-- Attachment #1: Type: text/plain, Size: 3272 bytes --]

On Wed, Feb 23, 2022 at 02:45:30PM +0100, Marek Vasut wrote:
> On 2/23/22 14:41, Maxime Ripard wrote:
> > Hi,
> > 
> > On Tue, Feb 22, 2022 at 09:47:23AM +0100, Max Krummenacher wrote:
> > > Use the new property bus-format to set the enum bus_format and bpc.
> > > Completes: commit 4a1d0dbc8332 ("drm/panel: simple: add panel-dpi support")
> > > 
> > > Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
> > > 
> > > ---
> > > 
> > >   drivers/gpu/drm/panel/panel-simple.c | 32 ++++++++++++++++++++++++++++
> > >   1 file changed, 32 insertions(+)
> > > 
> > > Relates to the discussion: https://lore.kernel.org/all/20220201110717.3585-1-cniedermaier@dh-electronics.com/
> > > 
> > > Max
> > > 
> > > diff --git a/drivers/gpu/drm/panel/panel-simple.c b/drivers/gpu/drm/panel/panel-simple.c
> > > index c5f133667a2d..5c07260de71c 100644
> > > --- a/drivers/gpu/drm/panel/panel-simple.c
> > > +++ b/drivers/gpu/drm/panel/panel-simple.c
> > > @@ -453,6 +453,7 @@ static int panel_dpi_probe(struct device *dev,
> > >   	struct panel_desc *desc;
> > >   	unsigned int bus_flags;
> > >   	struct videomode vm;
> > > +	const char *format = "";
> > >   	int ret;
> > >   	np = dev->of_node;
> > > @@ -477,6 +478,37 @@ static int panel_dpi_probe(struct device *dev,
> > >   	of_property_read_u32(np, "width-mm", &desc->size.width);
> > >   	of_property_read_u32(np, "height-mm", &desc->size.height);
> > > +	of_property_read_string(np, "bus-format", &format);
> > > +	if (!strcmp(format, "BGR888_1X24")) {
> > > +		desc->bpc = 8;
> > > +		desc->bus_format = MEDIA_BUS_FMT_BGR888_1X24;
> > > +	} else if (!strcmp(format, "GBR888_1X24")) {
> > > +		desc->bpc = 8;
> > > +		desc->bus_format = MEDIA_BUS_FMT_GBR888_1X24;
> > > +	} else if (!strcmp(format, "RBG888_1X24")) {
> > > +		desc->bpc = 8;
> > > +		desc->bus_format = MEDIA_BUS_FMT_RBG888_1X24;
> > > +	} else if (!strcmp(format, "RGB444_1X12")) {
> > > +		desc->bpc = 6;
> > > +		desc->bus_format = MEDIA_BUS_FMT_RGB444_1X12;
> > > +	} else if (!strcmp(format, "RGB565_1X16")) {
> > > +		desc->bpc = 6;
> > > +		desc->bus_format = MEDIA_BUS_FMT_RGB565_1X16;
> > > +	} else if (!strcmp(format, "RGB666_1X18")) {
> > > +		desc->bpc = 6;
> > > +		desc->bus_format = MEDIA_BUS_FMT_RGB666_1X18;
> > > +	} else if (!strcmp(format, "RGB666_1X24_CPADHI")) {
> > > +		desc->bpc = 6;
> > > +		desc->bus_format = MEDIA_BUS_FMT_RGB666_1X24_CPADHI;
> > > +	} else if (!strcmp(format, "RGB888_1X24")) {
> > > +		desc->bpc = 8;
> > > +		desc->bus_format = MEDIA_BUS_FMT_RGB888_1X24;
> > > +	} else {
> > > +		dev_err(dev, "%pOF: missing or unknown bus-format property\n",
> > > +			np);
> > > +		return -EINVAL;
> > > +	}
> > > +
> > 
> > It doesn't seem right, really. We can't the bus format / bpc be inferred
> > from the compatible? I'd expect two panels that don't have the same bus
> > format to not be claimed as compatible.
> 
> Which compatible ?
> 
> Note that this is for panel-dpi compatible, i.e. the panel which has timings
> specified in DT (and needs bus format specified there too).

panel-dpi is supposed to have two compatibles, the panel-specific one
and panel-dpi. This would obviously be tied to the panel-specific one.

Maxime

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Maxime Ripard <maxime@cerno.tech>
To: Marek Vasut <marex@denx.de>
Cc: Max Krummenacher <max.oss.09@gmail.com>,
	dri-devel@lists.freedesktop.org,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Fabio Estevam <festevam@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	DenysDrozdov <denys.drozdov@toradex.com>,
	David Airlie <airlied@linux.ie>,
	Christoph Niedermaier <cniedermaier@dh-electronics.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Sam Ravnborg <sam@ravnborg.org>, Shawn Guo <shawnguo@kernel.org>,
	Daniel Vetter <daniel@ffwll.ch>,
	NXP Linux Team <linux-imx@nxp.com>,
	Max Krummenacher <max.krummenacher@toradex.com>
Subject: Re: [RFC PATCH] drm/panel: simple: panel-dpi: use bus-format to set bpc and bus_format
Date: Wed, 23 Feb 2022 14:47:57 +0100	[thread overview]
Message-ID: <20220223134757.f5upi2iun27op5w5@houat> (raw)
In-Reply-To: <b5f471f4-0712-b798-efb8-b5b481cdb898@denx.de>


[-- Attachment #1.1: Type: text/plain, Size: 3272 bytes --]

On Wed, Feb 23, 2022 at 02:45:30PM +0100, Marek Vasut wrote:
> On 2/23/22 14:41, Maxime Ripard wrote:
> > Hi,
> > 
> > On Tue, Feb 22, 2022 at 09:47:23AM +0100, Max Krummenacher wrote:
> > > Use the new property bus-format to set the enum bus_format and bpc.
> > > Completes: commit 4a1d0dbc8332 ("drm/panel: simple: add panel-dpi support")
> > > 
> > > Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
> > > 
> > > ---
> > > 
> > >   drivers/gpu/drm/panel/panel-simple.c | 32 ++++++++++++++++++++++++++++
> > >   1 file changed, 32 insertions(+)
> > > 
> > > Relates to the discussion: https://lore.kernel.org/all/20220201110717.3585-1-cniedermaier@dh-electronics.com/
> > > 
> > > Max
> > > 
> > > diff --git a/drivers/gpu/drm/panel/panel-simple.c b/drivers/gpu/drm/panel/panel-simple.c
> > > index c5f133667a2d..5c07260de71c 100644
> > > --- a/drivers/gpu/drm/panel/panel-simple.c
> > > +++ b/drivers/gpu/drm/panel/panel-simple.c
> > > @@ -453,6 +453,7 @@ static int panel_dpi_probe(struct device *dev,
> > >   	struct panel_desc *desc;
> > >   	unsigned int bus_flags;
> > >   	struct videomode vm;
> > > +	const char *format = "";
> > >   	int ret;
> > >   	np = dev->of_node;
> > > @@ -477,6 +478,37 @@ static int panel_dpi_probe(struct device *dev,
> > >   	of_property_read_u32(np, "width-mm", &desc->size.width);
> > >   	of_property_read_u32(np, "height-mm", &desc->size.height);
> > > +	of_property_read_string(np, "bus-format", &format);
> > > +	if (!strcmp(format, "BGR888_1X24")) {
> > > +		desc->bpc = 8;
> > > +		desc->bus_format = MEDIA_BUS_FMT_BGR888_1X24;
> > > +	} else if (!strcmp(format, "GBR888_1X24")) {
> > > +		desc->bpc = 8;
> > > +		desc->bus_format = MEDIA_BUS_FMT_GBR888_1X24;
> > > +	} else if (!strcmp(format, "RBG888_1X24")) {
> > > +		desc->bpc = 8;
> > > +		desc->bus_format = MEDIA_BUS_FMT_RBG888_1X24;
> > > +	} else if (!strcmp(format, "RGB444_1X12")) {
> > > +		desc->bpc = 6;
> > > +		desc->bus_format = MEDIA_BUS_FMT_RGB444_1X12;
> > > +	} else if (!strcmp(format, "RGB565_1X16")) {
> > > +		desc->bpc = 6;
> > > +		desc->bus_format = MEDIA_BUS_FMT_RGB565_1X16;
> > > +	} else if (!strcmp(format, "RGB666_1X18")) {
> > > +		desc->bpc = 6;
> > > +		desc->bus_format = MEDIA_BUS_FMT_RGB666_1X18;
> > > +	} else if (!strcmp(format, "RGB666_1X24_CPADHI")) {
> > > +		desc->bpc = 6;
> > > +		desc->bus_format = MEDIA_BUS_FMT_RGB666_1X24_CPADHI;
> > > +	} else if (!strcmp(format, "RGB888_1X24")) {
> > > +		desc->bpc = 8;
> > > +		desc->bus_format = MEDIA_BUS_FMT_RGB888_1X24;
> > > +	} else {
> > > +		dev_err(dev, "%pOF: missing or unknown bus-format property\n",
> > > +			np);
> > > +		return -EINVAL;
> > > +	}
> > > +
> > 
> > It doesn't seem right, really. We can't the bus format / bpc be inferred
> > from the compatible? I'd expect two panels that don't have the same bus
> > format to not be claimed as compatible.
> 
> Which compatible ?
> 
> Note that this is for panel-dpi compatible, i.e. the panel which has timings
> specified in DT (and needs bus format specified there too).

panel-dpi is supposed to have two compatibles, the panel-specific one
and panel-dpi. This would obviously be tied to the panel-specific one.

Maxime

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

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

  reply	other threads:[~2022-02-23 13:48 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22  8:47 [RFC PATCH] drm/panel: simple: panel-dpi: use bus-format to set bpc and bus_format Max Krummenacher
2022-02-22  8:47 ` Max Krummenacher
2022-02-23 13:41 ` Maxime Ripard
2022-02-23 13:41   ` Maxime Ripard
2022-02-23 13:45   ` Marek Vasut
2022-02-23 13:45     ` Marek Vasut
2022-02-23 13:47     ` Maxime Ripard [this message]
2022-02-23 13:47       ` Maxime Ripard
2022-02-23 14:09       ` Marek Vasut
2022-02-23 14:09         ` Marek Vasut
2022-02-23 14:37         ` Maxime Ripard
2022-02-23 14:37           ` Maxime Ripard
2022-02-23 14:38           ` Marek Vasut
2022-02-23 14:38             ` Marek Vasut
2022-02-23 16:39             ` Maxime Ripard
2022-02-23 16:39               ` Maxime Ripard
2022-02-23 16:57               ` Marek Vasut
2022-02-23 16:57                 ` Marek Vasut
2022-02-23 15:25     ` Max Krummenacher
2022-02-23 15:25       ` Max Krummenacher
2022-03-02 14:21       ` Maxime Ripard
2022-03-02 14:21         ` Maxime Ripard
2022-03-02 16:22         ` Marek Vasut
2022-03-02 16:22           ` Marek Vasut
2022-03-07 15:26           ` Max Krummenacher
2022-03-07 15:26             ` Max Krummenacher
2022-03-18 16:35             ` Maxime Ripard
2022-03-18 16:35               ` Maxime Ripard
2022-03-18 17:05               ` Dave Stevenson
2022-03-18 17:05                 ` Dave Stevenson
2022-03-18 17:16                 ` Maxime Ripard
2022-03-18 17:16                   ` Maxime Ripard
2022-03-18 17:53                   ` Dave Stevenson
2022-03-18 17:53                     ` Dave Stevenson
2022-03-23  8:42                     ` Max Krummenacher
2022-03-23  8:42                       ` Max Krummenacher
2022-03-23 15:58                       ` Maxime Ripard
2022-03-23 15:58                         ` Maxime Ripard
2022-03-23 20:06                         ` Max Krummenacher
2022-03-23 20:06                           ` Max Krummenacher
2022-03-24  8:15                           ` Francesco Dolcini
2022-03-24  8:15                             ` Francesco Dolcini
2022-04-08 18:01                             ` Laurent Pinchart
2022-04-08 18:01                               ` Laurent Pinchart
2022-04-08 18:15                           ` Laurent Pinchart
2022-04-08 18:15                             ` Laurent Pinchart
2022-04-19 11:50                             ` Max Krummenacher
2022-04-19 11:50                               ` Max Krummenacher

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=20220223134757.f5upi2iun27op5w5@houat \
    --to=maxime@cerno.tech \
    --cc=airlied@linux.ie \
    --cc=cniedermaier@dh-electronics.com \
    --cc=denys.drozdov@toradex.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel@pengutronix.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=marex@denx.de \
    --cc=max.krummenacher@toradex.com \
    --cc=max.oss.09@gmail.com \
    --cc=s.hauer@pengutronix.de \
    --cc=sam@ravnborg.org \
    --cc=shawnguo@kernel.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.