From: Nikhil Devshatwar <nikhil.nd@ti.com>
To: <dri-devel@lists.freedesktop.org>,
Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Sekhar Nori <nsekhar@ti.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Swapnil Jakhade <sjakhade@cadence.com>
Subject: [PATCH 3/5] drm: bridge: Propagate the bus flags from bridge->timings
Date: Fri, 16 Oct 2020 16:09:15 +0530 [thread overview]
Message-ID: <20201016103917.26838-4-nikhil.nd@ti.com> (raw)
In-Reply-To: <20201016103917.26838-1-nikhil.nd@ti.com>
When the next bridge does not specify any bus flags, use the
bridge->timings->input_bus_flags as fallback when propagating
bus flags from next bridge to current bridge.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
---
drivers/gpu/drm/drm_bridge.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/gpu/drm/drm_bridge.c b/drivers/gpu/drm/drm_bridge.c
index 64f0effb52ac..8353723323ab 100644
--- a/drivers/gpu/drm/drm_bridge.c
+++ b/drivers/gpu/drm/drm_bridge.c
@@ -975,6 +975,13 @@ drm_atomic_bridge_propagate_bus_flags(struct drm_bridge *bridge,
* duplicate the "dummy propagation" logic.
*/
bridge_state->input_bus_cfg.flags = output_flags;
+
+ /*
+ * Use the bridge->timings->input_bus_flags as fallback if the next bridge
+ * does not specify the flags
+ */
+ if (!bridge_state->input_bus_cfg.flags)
+ bridge_state->input_bus_cfg.flags = bridge->timings->input_bus_flags;
}
/**
--
2.17.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-10-16 10:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 10:39 [PATCH 0/5] drm/tidss: Use new connector model for tidss Nikhil Devshatwar
2020-10-16 10:39 ` [PATCH 1/5] drm/tidss: Move to newer connector model Nikhil Devshatwar
2020-10-21 7:47 ` Tomi Valkeinen
2020-10-29 22:54 ` Laurent Pinchart
2020-10-16 10:39 ` [PATCH 2/5] drm/tidss: Set bus_format correctly from bridge/connector Nikhil Devshatwar
2020-10-29 22:57 ` Laurent Pinchart
2020-11-09 11:40 ` Nikhil Devshatwar
2020-10-16 10:39 ` Nikhil Devshatwar [this message]
2020-10-21 11:31 ` [PATCH 3/5] drm: bridge: Propagate the bus flags from bridge->timings Tomi Valkeinen
2020-10-28 14:34 ` Nikhil Devshatwar
2020-10-29 22:48 ` Laurent Pinchart
2020-10-30 7:30 ` Tomi Valkeinen
2020-10-30 8:08 ` Boris Brezillon
2020-10-30 8:40 ` Tomi Valkeinen
2020-10-30 8:50 ` Boris Brezillon
2020-10-16 10:39 ` [PATCH 4/5] drm/bridge: tfp410: Support format negotiation Nikhil Devshatwar
2020-10-29 22:31 ` Laurent Pinchart
2020-10-16 10:39 ` [PATCH 5/5] drm/bridge: mhdp8564: " Nikhil Devshatwar
2020-10-28 14:40 ` Swapnil Kashinath Jakhade
2020-10-29 22:39 ` Laurent Pinchart
2020-11-02 7:25 ` Tomi Valkeinen
2020-10-19 12:11 ` [PATCH 0/5] drm/tidss: Use new connector model for tidss Tomi Valkeinen
2020-10-28 14:19 ` Nikhil Devshatwar
2020-10-29 7:14 ` 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=20201016103917.26838-4-nikhil.nd@ti.com \
--to=nikhil.nd@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=nsekhar@ti.com \
--cc=sjakhade@cadence.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 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.