From: Sam Ravnborg <sam@ravnborg.org>
To: Marek Vasut <marex@denx.de>
Cc: dri-devel@lists.freedesktop.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v5 2/2] drm/bridge: lvds-codec: Add support for pixel data sampling edge select
Date: Sun, 17 Oct 2021 19:40:57 +0200 [thread overview]
Message-ID: <YWxgKWXBpT6PyQO8@ravnborg.org> (raw)
In-Reply-To: <075913ae-e5a0-3a9e-c928-55cae99ab0e5@denx.de>
Hi Marek,
On Sun, Oct 17, 2021 at 07:29:51PM +0200, Marek Vasut wrote:
> On 10/17/21 6:49 PM, Sam Ravnborg wrote:
>
> [...]
>
> > > + /*
> > > + * Encoder might sample data on different clock edge than the display,
> > > + * for example OnSemi FIN3385 has a dedicated strapping pin to select
> > > + * the sampling edge.
> > > + */
> > > + if (lvds_codec->connector_type == DRM_MODE_CONNECTOR_LVDS &&
> > > + !of_property_read_u32(dev->of_node, "pclk-sample", &val)) {
> > > + lvds_codec->timings.input_bus_flags = val ?
> > > + DRM_BUS_FLAG_PIXDATA_SAMPLE_POSEDGE :
> > > + DRM_BUS_FLAG_PIXDATA_SAMPLE_NEGEDGE;
> > > + }
> > > +
> > > /*
> > > * The panel_bridge bridge is attached to the panel's of_node,
> > > * but we need a bridge attached to our of_node for our user
> > > * to look up.
> > > */
> > > lvds_codec->bridge.of_node = dev->of_node;
> > > + lvds_codec->bridge.timings = &lvds_codec->timings;
> > I do not understand how this will work. The only field that is set is timings.input_bus_flags
> > but any user will see bridge.timings is set and will think this is all
> > timing info.
> >
> > Maybe I just misses something obvious?
>
> Is there anything else in those timings that should be set ? See
> include/drm/drm_bridge.h around line 640
>
> setup_time_ps/hold_time_ps/dual_link isn't supported by this driver, so it
> is 0 or false anyway, i.e. no change.
Just me being confused with display_timings. Patch looks good.
Reviewed-by: Sam Ravnborg <sam@ravnborg.org>
Ping me in a few days to apply it if there is no more feedback.
Sam
next prev parent reply other threads:[~2021-10-17 17:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 0:12 [PATCH v5 1/2] dt-bindings: display: bridge: lvds-codec: Document pixel data sampling edge select Marek Vasut
2021-10-17 0:12 ` [PATCH v5 2/2] drm/bridge: lvds-codec: Add support for " Marek Vasut
2021-10-17 16:49 ` Sam Ravnborg
2021-10-17 17:29 ` Marek Vasut
2021-10-17 17:40 ` Sam Ravnborg [this message]
2021-10-17 20:05 ` Marek Vasut
2021-10-23 23:04 ` Marek Vasut
2021-11-24 3:02 ` Marek Vasut
2021-12-07 17:30 ` Marek Vasut
2021-10-18 17:54 ` [PATCH v5 1/2] dt-bindings: display: bridge: lvds-codec: Document " Rob Herring
2021-10-18 18:08 ` Laurent Pinchart
2021-10-18 19:47 ` Marek Vasut
2021-10-18 19:57 ` Laurent Pinchart
2021-10-18 22:18 ` Marek Vasut
2021-10-19 6:49 ` Laurent Pinchart
2021-10-19 14:39 ` Marek Vasut
2021-10-26 23:43 ` Laurent Pinchart
2021-10-27 12:29 ` Marek Vasut
-- strict thread matches above, loose matches on Subject: below --
2021-06-02 20:36 [PATCH V5 " Marek Vasut
2021-06-02 20:36 ` [PATCH V5 2/2] drm/bridge: lvds-codec: Add support for " 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=YWxgKWXBpT6PyQO8@ravnborg.org \
--to=sam@ravnborg.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=marex@denx.de \
--cc=robh+dt@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox