From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
To: Marek Vasut <marex@denx.de>,
Frieder Schrempf <frieder.schrempf@kontron.de>,
Jagan Teki <jagan@amarulasolutions.com>
Cc: Laurent.pinchart@ideasonboard.com, aford173@gmail.com,
andrzej.hajda@intel.com, dri-devel@lists.freedesktop.org,
inki.dae@samsung.com, kyungmin.park@samsung.com,
linux-amarula@amarulasolutions.com,
linux-arm-kernel@lists.infradead.org, linux-imx@nxp.com,
linux-samsung-soc@vger.kernel.org, m.szyprowski@samsung.com,
matteo.lisi@engicam.com, sw0312.kim@samsung.com,
tharvey@gateworks.com
Subject: Re: [PATCH v12 00/18] drm: Add Samsung MIPI DSIM bridge
Date: Tue, 14 Feb 2023 11:55:02 +0100 [thread overview]
Message-ID: <6ceb6866-f8a5-072f-3d86-895024fcec79@prevas.dk> (raw)
In-Reply-To: <12d5568f-c12c-970d-0f78-17d6dc7c0c1d@denx.de>
On 07/02/2023 10.23, Marek Vasut wrote:
> On 2/7/23 10:09, Rasmus Villemoes wrote:
>
> [...]
>
>> Now hotplug-detect doesn't work with the current sn65dsi86 driver, but
>> that's a separate issue; when I boot with a monitor attached, its edid
>> is correctly read out. But I still don't get any output, and the monitor
>> says "no signal" - my naive attempt (which has worked fine in other
>> cases) was to just dd /dev/urandom to /dev/fb0, so I'm clearly missing
>> some important step.
>
> You could try and tweak the DSI mode flags in
> drivers/gpu/drm/bridge/ti-sn65dsi86.c to operate in DSI burst mode
> MIPI_DSI_MODE_VIDEO_BURST instead of MIPI_DSI_MODE_VIDEO . Then you
> could configure the DSIM PLL to 891 MHz , but you also have to make sure
> the DSI86 would expect the 891 MHz (please check the datasheet).
Well, the data sheet for the dsi86 says up to 750MHz DSI HS clock, and
if the value specified in samsung,burst-clock-frequency is twice the DSI
HS clk, I suppose I should be good up to 1.5GHz? I have tried many
different values, but I never seem to get anything through; I think I'm
missing some piece.
So now I've tried to use these patches on the imx8mp-evk with the
mipi->hdmi accessory from NXP, just to see if I can ever get any
graphics through the mipi interface. And there the story is the same:
the adv7535 bridge gets probed, and can read out the edid from the
monitor over hdmi. And while the mipi block and the bridge seem to
attach to each other, I still don't get any output.
Do any of you happen to have this working on the imx8mp-evk, and if so,
can you share the .dts updates you've done and how exactly you test the
graphics?
Thanks,
Rasmus
WARNING: multiple messages have this Message-ID (diff)
From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
To: Marek Vasut <marex@denx.de>,
Frieder Schrempf <frieder.schrempf@kontron.de>,
Jagan Teki <jagan@amarulasolutions.com>
Cc: linux-samsung-soc@vger.kernel.org, matteo.lisi@engicam.com,
linux-amarula@amarulasolutions.com, sw0312.kim@samsung.com,
dri-devel@lists.freedesktop.org, kyungmin.park@samsung.com,
Laurent.pinchart@ideasonboard.com, andrzej.hajda@intel.com,
m.szyprowski@samsung.com, aford173@gmail.com,
linux-arm-kernel@lists.infradead.org, linux-imx@nxp.com
Subject: Re: [PATCH v12 00/18] drm: Add Samsung MIPI DSIM bridge
Date: Tue, 14 Feb 2023 11:55:02 +0100 [thread overview]
Message-ID: <6ceb6866-f8a5-072f-3d86-895024fcec79@prevas.dk> (raw)
In-Reply-To: <12d5568f-c12c-970d-0f78-17d6dc7c0c1d@denx.de>
On 07/02/2023 10.23, Marek Vasut wrote:
> On 2/7/23 10:09, Rasmus Villemoes wrote:
>
> [...]
>
>> Now hotplug-detect doesn't work with the current sn65dsi86 driver, but
>> that's a separate issue; when I boot with a monitor attached, its edid
>> is correctly read out. But I still don't get any output, and the monitor
>> says "no signal" - my naive attempt (which has worked fine in other
>> cases) was to just dd /dev/urandom to /dev/fb0, so I'm clearly missing
>> some important step.
>
> You could try and tweak the DSI mode flags in
> drivers/gpu/drm/bridge/ti-sn65dsi86.c to operate in DSI burst mode
> MIPI_DSI_MODE_VIDEO_BURST instead of MIPI_DSI_MODE_VIDEO . Then you
> could configure the DSIM PLL to 891 MHz , but you also have to make sure
> the DSI86 would expect the 891 MHz (please check the datasheet).
Well, the data sheet for the dsi86 says up to 750MHz DSI HS clock, and
if the value specified in samsung,burst-clock-frequency is twice the DSI
HS clk, I suppose I should be good up to 1.5GHz? I have tried many
different values, but I never seem to get anything through; I think I'm
missing some piece.
So now I've tried to use these patches on the imx8mp-evk with the
mipi->hdmi accessory from NXP, just to see if I can ever get any
graphics through the mipi interface. And there the story is the same:
the adv7535 bridge gets probed, and can read out the edid from the
monitor over hdmi. And while the mipi block and the bridge seem to
attach to each other, I still don't get any output.
Do any of you happen to have this working on the imx8mp-evk, and if so,
can you share the .dts updates you've done and how exactly you test the
graphics?
Thanks,
Rasmus
WARNING: multiple messages have this Message-ID (diff)
From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
To: Marek Vasut <marex@denx.de>,
Frieder Schrempf <frieder.schrempf@kontron.de>,
Jagan Teki <jagan@amarulasolutions.com>
Cc: Laurent.pinchart@ideasonboard.com, aford173@gmail.com,
andrzej.hajda@intel.com, dri-devel@lists.freedesktop.org,
inki.dae@samsung.com, kyungmin.park@samsung.com,
linux-amarula@amarulasolutions.com,
linux-arm-kernel@lists.infradead.org, linux-imx@nxp.com,
linux-samsung-soc@vger.kernel.org, m.szyprowski@samsung.com,
matteo.lisi@engicam.com, sw0312.kim@samsung.com,
tharvey@gateworks.com
Subject: Re: [PATCH v12 00/18] drm: Add Samsung MIPI DSIM bridge
Date: Tue, 14 Feb 2023 11:55:02 +0100 [thread overview]
Message-ID: <6ceb6866-f8a5-072f-3d86-895024fcec79@prevas.dk> (raw)
In-Reply-To: <12d5568f-c12c-970d-0f78-17d6dc7c0c1d@denx.de>
On 07/02/2023 10.23, Marek Vasut wrote:
> On 2/7/23 10:09, Rasmus Villemoes wrote:
>
> [...]
>
>> Now hotplug-detect doesn't work with the current sn65dsi86 driver, but
>> that's a separate issue; when I boot with a monitor attached, its edid
>> is correctly read out. But I still don't get any output, and the monitor
>> says "no signal" - my naive attempt (which has worked fine in other
>> cases) was to just dd /dev/urandom to /dev/fb0, so I'm clearly missing
>> some important step.
>
> You could try and tweak the DSI mode flags in
> drivers/gpu/drm/bridge/ti-sn65dsi86.c to operate in DSI burst mode
> MIPI_DSI_MODE_VIDEO_BURST instead of MIPI_DSI_MODE_VIDEO . Then you
> could configure the DSIM PLL to 891 MHz , but you also have to make sure
> the DSI86 would expect the 891 MHz (please check the datasheet).
Well, the data sheet for the dsi86 says up to 750MHz DSI HS clock, and
if the value specified in samsung,burst-clock-frequency is twice the DSI
HS clk, I suppose I should be good up to 1.5GHz? I have tried many
different values, but I never seem to get anything through; I think I'm
missing some piece.
So now I've tried to use these patches on the imx8mp-evk with the
mipi->hdmi accessory from NXP, just to see if I can ever get any
graphics through the mipi interface. And there the story is the same:
the adv7535 bridge gets probed, and can read out the edid from the
monitor over hdmi. And while the mipi block and the bridge seem to
attach to each other, I still don't get any output.
Do any of you happen to have this working on the imx8mp-evk, and if so,
can you share the .dts updates you've done and how exactly you test the
graphics?
Thanks,
Rasmus
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-02-14 10:55 UTC|newest]
Thread overview: 133+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 14:44 [PATCH v12 00/18] drm: Add Samsung MIPI DSIM bridge Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` [PATCH v12 01/18] drm: of: Lookup if child node has DSI panel or bridge Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` [PATCH v12 02/18] drm: bridge: panel: Add devm_drm_of_dsi_get_bridge helper Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:47 ` Maxime Ripard
2023-01-26 14:47 ` Maxime Ripard
2023-01-26 14:47 ` Maxime Ripard
2023-01-26 14:58 ` Jagan Teki
2023-01-26 14:58 ` Jagan Teki
2023-01-26 14:58 ` Jagan Teki
2023-01-26 14:44 ` [PATCH v12 03/18] drm: exynos: dsi: Drop explicit call to bridge detach Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` [PATCH v12 04/18] drm: exynos: dsi: Switch to devm_drm_of_dsi_get_bridge Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` [PATCH v12 05/18] drm: exynos: dsi: Mark PHY as optional Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` [PATCH v12 06/18] drm: exynos: dsi: Add platform PLL_P (PMS_P) offset Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` [PATCH v12 07/18] drm: exynos: dsi: Introduce hw_type platform data Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` [PATCH v12 08/18] drm: exynos: dsi: Handle proper host initialization Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` [PATCH v12 09/18] drm: exynos: dsi: Add atomic check Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` [PATCH v12 10/18] drm: exynos: dsi: Add input_bus_flags Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` [PATCH v12 11/18] drm: exynos: dsi: Add atomic_get_input_bus_fmts Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 15:29 ` Marek Vasut
2023-01-26 15:29 ` Marek Vasut
2023-01-26 15:29 ` Marek Vasut
2023-01-26 14:44 ` [PATCH v12 12/18] drm: exynos: dsi: Consolidate component and bridge Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` [PATCH v12 13/18] drm: exynos: dsi: Add host helper for te_irq_handler Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` [PATCH v12 14/18] drm: bridge: Generalize Exynos-DSI driver into a Samsung DSIM bridge Jagan Teki
2023-01-26 14:44 ` [PATCH v12 15/18] dt-bindings: display: exynos: dsim: Add NXP i.MX8M Mini/Nano support Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` [PATCH v12 16/18] drm: bridge: samsung-dsim: Add " Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` [PATCH v12 17/18] dt-bindings: display: exynos: dsim: Add NXP i.MX8M Plus support Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` [PATCH v12 18/18] drm: bridge: samsung-dsim: Add " Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-26 14:44 ` Jagan Teki
2023-01-27 10:33 ` [PATCH v12 00/18] drm: Add Samsung MIPI DSIM bridge Rasmus Villemoes
2023-01-27 10:33 ` Rasmus Villemoes
2023-01-27 10:33 ` Rasmus Villemoes
2023-01-27 10:39 ` Jagan Teki
2023-01-27 10:39 ` Jagan Teki
2023-01-27 10:39 ` Jagan Teki
2023-01-27 10:56 ` Rasmus Villemoes
2023-01-27 10:56 ` Rasmus Villemoes
2023-01-27 10:56 ` Rasmus Villemoes
2023-01-27 11:04 ` Jagan Teki
2023-01-27 11:04 ` Jagan Teki
2023-01-27 11:04 ` Jagan Teki
2023-01-27 11:30 ` Marek Vasut
2023-01-27 11:30 ` Marek Vasut
2023-01-27 11:30 ` Marek Vasut
2023-01-30 12:45 ` Rasmus Villemoes
2023-01-30 12:45 ` Rasmus Villemoes
2023-01-30 12:45 ` Rasmus Villemoes
2023-01-31 7:27 ` Alexander Stein
2023-01-31 7:27 ` Alexander Stein
2023-01-31 7:27 ` Alexander Stein
2023-02-01 22:00 ` Marek Vasut
2023-02-01 22:00 ` Marek Vasut
2023-02-01 22:00 ` Marek Vasut
2023-02-03 12:29 ` Rasmus Villemoes
2023-02-03 12:29 ` Rasmus Villemoes
2023-02-03 12:29 ` Rasmus Villemoes
2023-02-06 8:11 ` Frieder Schrempf
2023-02-06 8:11 ` Frieder Schrempf
2023-02-06 8:11 ` Frieder Schrempf
2023-02-07 9:09 ` Rasmus Villemoes
2023-02-07 9:09 ` Rasmus Villemoes
2023-02-07 9:09 ` Rasmus Villemoes
2023-02-07 9:23 ` Marek Vasut
2023-02-07 9:23 ` Marek Vasut
2023-02-07 9:23 ` Marek Vasut
2023-02-14 10:55 ` Rasmus Villemoes [this message]
2023-02-14 10:55 ` Rasmus Villemoes
2023-02-14 10:55 ` Rasmus Villemoes
2023-02-14 11:08 ` Rasmus Villemoes
2023-02-14 11:08 ` Rasmus Villemoes
2023-02-14 11:08 ` Rasmus Villemoes
2023-02-14 11:09 ` Fabio Estevam
2023-02-14 11:09 ` Fabio Estevam
2023-02-14 11:09 ` Fabio Estevam
2023-02-14 11:11 ` Fabio Estevam
2023-02-14 11:11 ` Fabio Estevam
2023-02-14 11:11 ` Fabio Estevam
2023-02-17 8:55 ` Rasmus Villemoes
2023-02-17 8:55 ` Rasmus Villemoes
2023-02-17 8:55 ` Rasmus Villemoes
2023-02-17 10:05 ` Alexander Stein
2023-02-17 10:05 ` Alexander Stein
2023-02-17 10:05 ` Alexander Stein
2023-02-17 18:22 ` Rasmus Villemoes
2023-02-17 18:22 ` Rasmus Villemoes
2023-02-17 18:22 ` Rasmus Villemoes
2023-02-22 10:05 ` Frieder Schrempf
2023-02-22 10:05 ` Frieder Schrempf
2023-02-22 10:05 ` Frieder Schrempf
2023-02-24 14:08 ` Rasmus Villemoes
2023-02-24 14:08 ` Rasmus Villemoes
2023-02-24 14:08 ` Rasmus Villemoes
2023-02-24 15:00 ` Adam Ford
2023-02-24 15:00 ` Adam Ford
2023-02-24 15:00 ` Adam Ford
2023-02-01 8:37 ` Frieder Schrempf
2023-02-01 8:37 ` Frieder Schrempf
2023-02-01 8:37 ` Frieder Schrempf
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=6ceb6866-f8a5-072f-3d86-895024fcec79@prevas.dk \
--to=rasmus.villemoes@prevas.dk \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=aford173@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=frieder.schrempf@kontron.de \
--cc=inki.dae@samsung.com \
--cc=jagan@amarulasolutions.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=marex@denx.de \
--cc=matteo.lisi@engicam.com \
--cc=sw0312.kim@samsung.com \
--cc=tharvey@gateworks.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.