From: Marco Felsch <m.felsch@pengutronix.de>
To: Adam Ford <aford173@gmail.com>
Cc: Dave Stevenson <dave.stevenson@raspberrypi.com>,
Neil Armstrong <narmstrong@baylibre.com>,
David Airlie <airlied@linux.ie>,
dri-devel <dri-devel@lists.freedesktop.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Marek Vasut <marex@denx.de>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Jagan Teki <jagan@amarulasolutions.com>,
robert.chiras@nxp.com, laurentiu.palcu@nxp.com,
NXP Linux Team <linux-imx@nxp.com>,
Jonas Karlman <jonas@kwiboo.se>,
Sascha Hauer <s.hauer@pengutronix.de>,
arm-soc <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Robert Foss <robert.foss@linaro.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>
Subject: Re: imx8mm lcdif->dsi->adv7535 no video, no errors
Date: Thu, 4 Aug 2022 11:57:15 +0200 [thread overview]
Message-ID: <20220804095715.d3ay7yvn2adxdo4x@pengutronix.de> (raw)
In-Reply-To: <CAHCN7x+HSPJpYYDgV_F91ZsPHW9Uwze8KRAqWE-XAyp5yzB9Hw@mail.gmail.com>
On 22-08-03, Adam Ford wrote:
> On Wed, Aug 3, 2022 at 7:17 AM Dave Stevenson
...
> > Not meaning to butt in, but I have datasheets for ADV7533 and 7535
> > from previously looking at these chips.
>
> Thanks for the feedback.
>
> > Mine fairly plainly states:
> > "The DSI receiver input supports DSI video mode operation only, and
> > specifically, only supports nonburst mode with sync pulses".
> > Non-burst mode meaning that the DSI pixel rate MUST be the same as the
> > HDMI pixel rate.
>
> Mine also states the DSI source needs to provide correct video timing
> with start and stop sync packets.
>
> If I remember correctly, it seemed like Marek V wanted the hard coded
> samsung,burst-clock-frequency to go away so the clock frequency could
> be set dynamically.
As previously said, this is something on our TODO list too :) but needs
a bit more infrastructure work.
> I have attempted to do some of this work based on what I am seeing in
> the NXP kernel, and I get get my monitor to sync at some resolutions,
> but the screen is usually all green or all blue, so it's not really a
> success. The clock part appears to be good enough to make the monitor
> see some sort of signal, so I am going to investigate the calculation
> of the rest of the video timings to see if I can fix the color issue.
Please don't pay to much attention to the NXP kernel. No one have a glue
where those porches came from. If I specify the burst-clock-freq. to
445.5 and set the lane number to 4 and hack in the porches values from
NXP, than I get a 720P output too. But this isn't the way to go instead
we should calc the porches settings and the burst-clock-frequency
dynamiclly to provide more than just a few resolutions. But for that we
need a clear understanding of how the ADV is working.
I will prepare a repo to day and will send you a link with the hack
patches in it, so you can test it :)
Regards,
Marco
next prev parent reply other threads:[~2022-08-04 9:57 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 15:15 imx8mm lcdif->dsi->adv7535 no video, no errors Adam Ford
2022-08-01 6:19 ` Marco Felsch
2022-08-01 10:54 ` Adam Ford
2022-08-01 12:15 ` Adam Ford
2022-08-01 19:33 ` Fabio Estevam
2022-08-01 20:07 ` Adam Ford
2022-08-01 22:57 ` Adam Ford
2022-08-01 22:55 ` Marco Felsch
2022-08-01 23:11 ` Fabio Estevam
2022-08-02 1:39 ` Adam Ford
2022-08-02 1:53 ` Fabio Estevam
2022-08-02 2:29 ` Adam Ford
2022-08-02 8:08 ` Marco Felsch
2022-08-02 12:13 ` Adam Ford
2022-08-02 13:51 ` Adam Ford
2022-08-03 2:14 ` Adam Ford
2022-08-03 6:20 ` Marco Felsch
2022-08-03 11:02 ` Adam Ford
2022-08-03 12:17 ` Dave Stevenson
2022-08-03 12:31 ` Adam Ford
2022-08-03 13:41 ` Dave Stevenson
2022-08-04 10:27 ` Marco Felsch
2022-08-04 12:03 ` Dave Stevenson
2022-08-04 13:16 ` Marco Felsch
2022-08-04 9:57 ` Marco Felsch [this message]
2022-08-04 9:38 ` Marco Felsch
2022-08-04 11:31 ` Dave Stevenson
2022-08-04 12:51 ` Marco Felsch
2022-08-04 13:12 ` Adam Ford
2022-08-04 13:23 ` Marco Felsch
2022-08-04 14:43 ` Biju Das
2022-08-04 14:51 ` Dave Stevenson
2022-08-05 0:05 ` Adam Ford
2022-08-05 8:44 ` Biju Das
2022-08-05 10:55 ` Adam Ford
2022-08-05 12:56 ` Adam Ford
2022-08-05 21:05 ` Adam Ford
2022-08-08 2:49 ` Adam Ford
2022-08-08 8:54 ` Marco Felsch
2022-08-08 10:13 ` Adam Ford
2022-08-09 3:45 ` Adam Ford
2022-08-04 8:41 ` Marco Felsch
2022-08-03 5:56 ` Marco Felsch
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=20220804095715.d3ay7yvn2adxdo4x@pengutronix.de \
--to=m.felsch@pengutronix.de \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=aford173@gmail.com \
--cc=airlied@linux.ie \
--cc=andrzej.hajda@intel.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jagan@amarulasolutions.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kernel@pengutronix.de \
--cc=laurentiu.palcu@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=marex@denx.de \
--cc=narmstrong@baylibre.com \
--cc=robert.chiras@nxp.com \
--cc=robert.foss@linaro.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).