dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Pascal Roeleven <dev@pascalroeleven.nl>
To: laurent.pinchart@ideasonboard.com
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, David Airlie <airlied@linux.ie>,
	Mark Brown <broonie@kernel.org>,
	linux-sunxi@googlegroups.com, linux-kernel@vger.kernel.org,
	Chen-Yu Tsai <wens@csie.org>, Rob Herring <robh+dt@kernel.org>,
	Thierry Reding <thierry.reding@gmail.com>,
	dri-devel@lists.freedesktop.org, Sam Ravnborg <sam@ravnborg.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [linux-sunxi] Re: [PATCH v2 2/5] drm: panel: Add Starry KR070PE2T
Date: Mon, 29 Jun 2020 12:59:02 +0200	[thread overview]
Message-ID: <d43b324fa26638c179650e3c52adbf32@pascalroeleven.nl> (raw)
In-Reply-To: <20200628072819.GB8391@pendragon.ideasonboard.com>

Hi Laurent,

Good catch. It's actually the connector type which is wrong. The 
connector_type should be DRM_MODE_CONNECTOR_DPI. If you would include 
this in your patch series, you can have my acked-by.

Regards,
Pascal

On 2020-06-28 09:28, Laurent Pinchart wrote:
> Hi Pascal,
> 
> On Fri, Mar 20, 2020 at 12:21:33PM +0100, Pascal Roeleven wrote:
>> The KR070PE2T is a 7" panel with a resolution of 800x480.
>> 
>> KR070PE2T is the marking present on the ribbon cable. As this panel is
>> probably available under different brands, this marking will catch
>> most devices.
>> 
>> As I can't find a datasheet for this panel, the bus_flags are instead
>> from trial-and-error. The flags seem to be common for these kind of
>> panels as well.
>> 
>> Signed-off-by: Pascal Roeleven <dev@pascalroeleven.nl>
>> ---
>>  drivers/gpu/drm/panel/panel-simple.c | 29 
>> ++++++++++++++++++++++++++++
>>  1 file changed, 29 insertions(+)
>> 
>> diff --git a/drivers/gpu/drm/panel/panel-simple.c 
>> b/drivers/gpu/drm/panel/panel-simple.c
>> index e14c14ac6..b3d257257 100644
>> --- a/drivers/gpu/drm/panel/panel-simple.c
>> +++ b/drivers/gpu/drm/panel/panel-simple.c
>> @@ -2842,6 +2842,32 @@ static const struct panel_desc 
>> shelly_sca07010_bfn_lnn = {
>>  	.bus_format = MEDIA_BUS_FMT_RGB666_1X18,
>>  };
>> 
>> +static const struct drm_display_mode starry_kr070pe2t_mode = {
>> +	.clock = 33000,
>> +	.hdisplay = 800,
>> +	.hsync_start = 800 + 209,
>> +	.hsync_end = 800 + 209 + 1,
>> +	.htotal = 800 + 209 + 1 + 45,
>> +	.vdisplay = 480,
>> +	.vsync_start = 480 + 22,
>> +	.vsync_end = 480 + 22 + 1,
>> +	.vtotal = 480 + 22 + 1 + 22,
>> +	.vrefresh = 60,
>> +};
>> +
>> +static const struct panel_desc starry_kr070pe2t = {
>> +	.modes = &starry_kr070pe2t_mode,
>> +	.num_modes = 1,
>> +	.bpc = 8,
>> +	.size = {
>> +		.width = 152,
>> +		.height = 86,
>> +	},
>> +	.bus_format = MEDIA_BUS_FMT_RGB888_1X24,
>> +	.bus_flags = DRM_BUS_FLAG_DE_HIGH | 
>> DRM_BUS_FLAG_PIXDATA_DRIVE_NEGEDGE,
>> +	.connector_type = DRM_MODE_CONNECTOR_LVDS,
> 
> I'm trying to fix inconsistencies in the panel-simple driver, and this
> caught my eyes. MEDIA_BUS_FMT_RGB888_1X24 isn't a correct format for
> LVDS panels. MEDIA_BUS_FMT_RGB666_1X7X3_SPWG,
> MEDIA_BUS_FMT_RGB888_1X7X4_SPWG or MEDIA_BUS_FMT_RGB888_1X7X4_JEIDA
> should be used instead. As I couldn't find documentation for the panel,
> I can't tell which format is correct. Could you please help ?
> 
>> +};
>> +
>>  static const struct drm_display_mode starry_kr122ea0sra_mode = {
>>  	.clock = 147000,
>>  	.hdisplay = 1920,
>> @@ -3474,6 +3500,9 @@ static const struct of_device_id 
>> platform_of_match[] = {
>>  	}, {
>>  		.compatible = "shelly,sca07010-bfn-lnn",
>>  		.data = &shelly_sca07010_bfn_lnn,
>> +	}, {
>> +		.compatible = "starry,kr070pe2t",
>> +		.data = &starry_kr070pe2t,
>>  	}, {
>>  		.compatible = "starry,kr122ea0sra",
>>  		.data = &starry_kr122ea0sra,
> 
> --
> Regards,
> 
> Laurent Pinchart

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-06-30  7:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20 11:21 [PATCH v2 0/5] Add support for Topwise A721 tablet Pascal Roeleven
2020-03-20 11:21 ` [PATCH v2 1/5] dt-bindings: panel: Add binding for Starry KR070PE2T Pascal Roeleven
2020-03-28 20:22   ` Sam Ravnborg
2020-03-20 11:21 ` [PATCH v2 2/5] drm: panel: Add " Pascal Roeleven
2020-03-28 20:23   ` Sam Ravnborg
2020-06-28  7:28   ` Laurent Pinchart
2020-06-29 10:59     ` Pascal Roeleven [this message]
2020-03-20 11:21 ` [PATCH v2 3/5] dt-bindings: vendor-prefixes: Add Topwise Pascal Roeleven
2020-03-28 20:25   ` Sam Ravnborg
2020-03-30 23:26   ` Rob Herring
2020-03-20 11:21 ` [PATCH v2 4/5] dt-bindings: arm: Add Topwise A721 Pascal Roeleven
2020-03-30 23:26   ` Rob Herring
2020-03-20 11:21 ` [PATCH v2 5/5] ARM: dts: sun4i: Add support for Topwise A721 tablet Pascal Roeleven
2020-03-24 15:49 ` [PATCH v2 0/5] " Maxime Ripard

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=d43b324fa26638c179650e3c52adbf32@pascalroeleven.nl \
    --to=dev@pascalroeleven.nl \
    --cc=airlied@linux.ie \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sam@ravnborg.org \
    --cc=thierry.reding@gmail.com \
    --cc=wens@csie.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 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).