From: Nikhil Devshatwar <nikhil.nd@ti.com>
To: <dri-devel@lists.freedesktop.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
Subject: drm: Supporting new connector model in tidss
Date: Tue, 6 Oct 2020 03:01:23 +0530 [thread overview]
Message-ID: <20201005213123.o4qtfazrnexgjq7p@NiksLab> (raw)
Hi all,
I am trying to convert the upstream tidss drm driver to new
connector model.
The connector is getting created by the tidss driver and bridges are
attached with flag DRM_BRIDGE_ATTACH_NO_CONNECTOR
Here are some questions, regarding this:
1) Most of the info regarding bus_format and bus flags is coming from
the bridges. Is it okay to not populate connector->display_info with
bus_format and flags?
2) The "drm_atomic_bridge_chain_select_bus_fmts" does the format
negotiation. So is it okay for the encoder to simply pick the bus_format
from the first bridge's state?
3) What is the meaning of MEDIA_BUS_FMT_FIXED? Does it mean that the
bridge does not change the format from input to output?
4) The bus_flags are available in bridge->timings->input_bus_flags and
also in bridge_state->input_bus_cfg.flags. Which one should be used?
Regards,
Nikhil D
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2020-10-05 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 21:31 Nikhil Devshatwar [this message]
2020-10-05 22:09 ` drm: Supporting new connector model in tidss Daniel Vetter
2020-10-06 7:07 ` Tomi Valkeinen
2020-10-06 7:38 ` Boris Brezillon
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=20201005213123.o4qtfazrnexgjq7p@NiksLab \
--to=nikhil.nd@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=tomi.valkeinen@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;
as well as URLs for NNTP newsgroup(s).