All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	ch@denx.de, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/bridge: lvds-codec: Add support for LVDS data mapping select
Date: Tue, 25 May 2021 12:38:47 +0200	[thread overview]
Message-ID: <cd0e358b-9d8e-9005-0889-346e2b7b722c@denx.de> (raw)
In-Reply-To: <YKL2SAfonHJcoTw/@pendragon.ideasonboard.com>

On 5/18/21 1:03 AM, Laurent Pinchart wrote:

Hi,

[...]

>> @@ -69,10 +70,33 @@ static void lvds_codec_disable(struct drm_bridge *bridge)
>>   			"Failed to disable regulator \"vcc\": %d\n", ret);
>>   }
>>   
>> +static bool lvds_codec_mode_fixup(struct drm_bridge *bridge,
>> +				const struct drm_display_mode *mode,
>> +				struct drm_display_mode *adj)
>> +{
>> +	struct lvds_codec *lvds_codec = to_lvds_codec(bridge);
>> +	struct drm_encoder *encoder = bridge->encoder;
>> +	struct drm_device *ddev = encoder->dev;
>> +	struct drm_connector *connector;
>> +
>> +	/* If 'data-mapping' was not specified, do nothing. */
>> +	if (!lvds_codec->bus_format)
>> +		return true;
>> +
>> +	/* Patch in the LVDS format */
>> +	list_for_each_entry(connector, &ddev->mode_config.connector_list, head) {
>> +		drm_display_info_set_bus_formats(&connector->display_info,
>> +						 &lvds_codec->bus_format, 1);
>> +	}
> 
> This part bothers me, as the format at the input of the LVDS decoder
> doesn't match the format on the connector. Shouldn't you implement
> .atomic_get_output_bus_fmts() instead ?

No, I tried that option before this solution and that didn't work. The 
atomic stuff seems to be separate from what I need to pass here, i.e. 
without this, e.g. the mxsfb scanout engine still receives the wrong format.

[...]

  reply	other threads:[~2021-05-25 10:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-15 20:46 [PATCH 1/2] dt-bindings: display: bridge: lvds-codec: Document LVDS data mapping select Marek Vasut
2021-05-15 20:46 ` Marek Vasut
2021-05-15 20:46 ` [PATCH 2/2] drm/bridge: lvds-codec: Add support for " Marek Vasut
2021-05-17 23:03   ` Laurent Pinchart
2021-05-25 10:38     ` Marek Vasut [this message]
2021-06-14 18:02       ` Laurent Pinchart
2021-05-17 23:02 ` [PATCH 1/2] dt-bindings: display: bridge: lvds-codec: Document " Laurent Pinchart
2021-05-17 23:02   ` Laurent Pinchart
2021-05-17 23:03   ` Laurent Pinchart
2021-05-17 23:03     ` Laurent Pinchart
2021-05-25 10:33     ` Marek Vasut
2021-05-25 10:33       ` Marek Vasut
2021-05-25 10:31   ` Marek Vasut
2021-05-25 10:31     ` Marek Vasut

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=cd0e358b-9d8e-9005-0889-346e2b7b722c@denx.de \
    --to=marex@denx.de \
    --cc=ch@denx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --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.