From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Nikhil Devshatwar <nikhil.nd@ti.com>
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>,
Sekhar Nori <nsekhar@ti.com>, Yuti Amonkar <yamonkar@cadence.com>,
dri-devel@lists.freedesktop.org,
Swapnil Jakhade <sjakhade@cadence.com>
Subject: Re: [PATCH v3 1/6] drm: bridge: Propagate the bus flags from bridge->timings
Date: Mon, 30 Nov 2020 11:36:00 +0200 [thread overview]
Message-ID: <20201130093600.GB4141@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20201119160134.9244-2-nikhil.nd@ti.com>
Hi Nikhil,
Thank you for the patch.
On Thu, Nov 19, 2020 at 09:31:29PM +0530, Nikhil Devshatwar wrote:
> bus_flags can be specified by a bridge in the timings.
> If the bridge provides it, Override the bus_flags when propagating
> from next bridge.
>
> Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
> Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
> ---
>
> Notes:
> changes from v2:
> * update comment
> changes from v1:
> * Check for timings
> * Prioritize timings flags over next bridge's flags
>
> drivers/gpu/drm/drm_bridge.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_bridge.c b/drivers/gpu/drm/drm_bridge.c
> index 64f0effb52ac..13b67fc0dad3 100644
> --- a/drivers/gpu/drm/drm_bridge.c
> +++ b/drivers/gpu/drm/drm_bridge.c
> @@ -975,6 +975,14 @@ drm_atomic_bridge_propagate_bus_flags(struct drm_bridge *bridge,
> * duplicate the "dummy propagation" logic.
> */
> bridge_state->input_bus_cfg.flags = output_flags;
> +
> + /*
> + * If legacy bus flags are provided in bridge->timings, use those as
> + * input flags instead of propagating the output flags.
> + */
> + if (bridge->timings && bridge->timings->input_bus_flags)
> + bridge_state->input_bus_cfg.flags =
> + bridge->timings->input_bus_flags;
Hasn't Boris commented in his review of v1 that bus flags should be set
in atomic_check, even when they're static ? We're moving towards
removing timings->input_bus_flags, so this patch goes in the wrong
direction :-S
> }
>
> /**
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-11-30 9:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 16:01 [PATCH v3 0/6] drm/tidss: Use new connector model for tidss Nikhil Devshatwar
2020-11-19 16:01 ` [PATCH v3 1/6] drm: bridge: Propagate the bus flags from bridge->timings Nikhil Devshatwar
2020-11-30 9:36 ` Laurent Pinchart [this message]
2020-11-30 9:46 ` Tomi Valkeinen
2020-11-30 9:47 ` Laurent Pinchart
2020-11-30 10:02 ` Tomi Valkeinen
2020-11-30 10:04 ` Tomi Valkeinen
2020-11-30 18:59 ` Laurent Pinchart
2020-12-01 10:52 ` Nikhil Devshatwar
2020-11-19 16:01 ` [PATCH v3 2/6] drm/bridge: tfp410: Support format negotiation hooks Nikhil Devshatwar
2020-11-30 9:40 ` Laurent Pinchart
2020-11-19 16:01 ` [PATCH v3 3/6] drm/bridge: mhdp8546: Add minimal format negotiation Nikhil Devshatwar
2020-11-19 16:01 ` [PATCH v3 4/6] drm/tidss: Set bus_format correctly from bridge/connector Nikhil Devshatwar
2020-11-25 12:51 ` Tomi Valkeinen
2020-11-30 6:35 ` Nikhil Devshatwar
2020-11-30 9:46 ` Laurent Pinchart
2020-12-01 10:57 ` Nikhil Devshatwar
2020-12-01 15:53 ` Tomi Valkeinen
2020-11-30 9:45 ` Laurent Pinchart
2020-12-01 10:52 ` Nikhil Devshatwar
2020-11-19 16:01 ` [PATCH v3 5/6] drm/tidss: Move to newer connector model Nikhil Devshatwar
2020-11-19 16:01 ` [PATCH v3 6/6] drm/bridge: cdns-mhdp8546: Fix the interrupt enable/disable Nikhil Devshatwar
2020-11-23 14:54 ` 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=20201130093600.GB4141@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=nikhil.nd@ti.com \
--cc=nsekhar@ti.com \
--cc=sjakhade@cadence.com \
--cc=tomi.valkeinen@ti.com \
--cc=yamonkar@cadence.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).