mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Aradhya Bhatia <a-bhatia1@ti.com>,
	neil.armstrong@linaro.org, Jyri Sarha <jyri.sarha@iki.fi>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Andrzej Hajda <andrzej.hajda@intel.com>,
	Robert Foss <rfoss@kernel.org>, Jonas Karlman <jonas@kwiboo.se>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	Rahul T R <r-ravikumar@ti.com>,
	Swapnil Jakhade <sjakhade@cadence.com>,
	Boris Brezillon <boris.brezillon@collabora.com>,
	Francesco Dolcini <francesco@dolcini.it>
Cc: DRI Development List <dri-devel@lists.freedesktop.org>,
	Linux Kernel List <linux-kernel@vger.kernel.org>,
	Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
	Devarsh Thakkar <devarsht@ti.com>,
	Jayesh Choudhary <j-choudhary@ti.com>
Subject: Re: [PATCH v6 3/8] drm/bridge: mhdp8546: Add minimal format negotiation
Date: Mon, 29 May 2023 14:12:23 +0300	[thread overview]
Message-ID: <5d207be0-c8f0-7c68-91b2-d5ef873ca6cc@ideasonboard.com> (raw)
In-Reply-To: <c8712ef7-c0bc-e6e7-7319-68238d011dd9@ti.com>

On 29/05/2023 08:37, Aradhya Bhatia wrote:
>> Btw, we seem to be missing get-output-fmt from the mdhp driver.
> Yes, we are.
> 
> With the drm_bridge_attach call added, the display-connector bridge will
> assign MEDIA_BUS_FMT_FIXED as the default output format. And most
> bridges support only their primary output bus format in their
> get-output-fmt hooks. I suppose it would be RGB121212_1X36 in mhdp8546's
> case.
> 
> Do we require this when there is no comprehensive way to determine if
> another bus format may be more suitable (depending on the hardware
> configurations)?

If I recall right, mhdp supports other formats than RGB121212_1X36 on 
the input side (different bit depths and also yuv). On the output side, 
even if the input is 12 bits per component, when connected to a normal 
monitor, the output bpc would be 8.

I'm not sure if any of that matters, as nobody (?) will use the output 
format of mhdp, as it just goes "outside" to the monitor, and it is the 
mhdp driver that negotiates a suitable output format with the monitor.

  Tomi


  reply	other threads:[~2023-05-29 11:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09  9:30 [PATCH v6 0/8] drm/tidss: Use new connector model for tidss Aradhya Bhatia
2023-05-09  9:30 ` [PATCH v6 1/8] drm/bridge: tfp410: Support format negotiation hooks Aradhya Bhatia
2023-05-09  9:30 ` [PATCH v6 2/8] drm/bridge: tfp410: Set input_bus_flags in atomic_check Aradhya Bhatia
2023-05-16  7:25   ` Neil Armstrong
2023-05-16 14:27     ` Aradhya Bhatia
2023-05-09  9:30 ` [PATCH v6 3/8] drm/bridge: mhdp8546: Add minimal format negotiation Aradhya Bhatia
2023-05-12  9:15   ` Tomi Valkeinen
2023-05-15 15:59     ` Aradhya Bhatia
2023-05-16  7:21       ` Neil Armstrong
2023-05-16 14:25         ` Aradhya Bhatia
2023-05-26  9:29           ` Tomi Valkeinen
2023-05-29  5:37             ` Aradhya Bhatia
2023-05-29 11:12               ` Tomi Valkeinen [this message]
2023-05-09  9:30 ` [PATCH v6 4/8] drm/bridge: mhdp8546: Set input_bus_flags from atomic_check Aradhya Bhatia
2023-05-16  7:24   ` Neil Armstrong
2023-05-17  5:48     ` Aradhya Bhatia
2023-05-22  8:05       ` neil.armstrong
2023-05-23  5:57         ` Aradhya Bhatia
2023-05-09  9:30 ` [PATCH v6 5/8] drm/bridge: sii902x: Support format negotiation hooks Aradhya Bhatia
2023-05-16  7:16   ` Neil Armstrong
2023-05-09  9:30 ` [PATCH v6 6/8] drm/bridge: sii902x: Set input_bus_flags in atomic_check Aradhya Bhatia
2023-05-16  7:24   ` Neil Armstrong
2023-05-09  9:30 ` [PATCH v6 7/8] drm/tidss: Update encoder/bridge chain connect model Aradhya Bhatia
2023-05-09  9:30 ` [PATCH v6 8/8] drm/bridge: cdns-mhdp8546: Fix the interrupt enable/disable Aradhya Bhatia
2023-05-12  9:20 ` [PATCH v6 0/8] drm/tidss: Use new connector model for tidss Tomi Valkeinen

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=5d207be0-c8f0-7c68-91b2-d5ef873ca6cc@ideasonboard.com \
    --to=tomi.valkeinen@ideasonboard.com \
    --cc=a-bhatia1@ti.com \
    --cc=airlied@gmail.com \
    --cc=andrzej.hajda@intel.com \
    --cc=boris.brezillon@collabora.com \
    --cc=daniel@ffwll.ch \
    --cc=devarsht@ti.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=francesco@dolcini.it \
    --cc=j-choudhary@ti.com \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=jyri.sarha@iki.fi \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=nm@ti.com \
    --cc=r-ravikumar@ti.com \
    --cc=rfoss@kernel.org \
    --cc=sjakhade@cadence.com \
    --cc=vigneshr@ti.com \
    /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

all inboxes | Powered by JetHome®