All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Cc: Fabio Estevam <festevam@gmail.com>,
	dri-devel@lists.freedesktop.org, Marek Vasut <marex@denx.de>,
	linux-samsung-soc@vger.kernel.org, matteo.lisi@engicam.com,
	aford173@gmail.com, dri-devel@lists.freedesktop.org,
	sw0312.kim@samsung.com, linux-imx@nxp.com,
	Frieder Schrempf <frieder.schrempf@kontron.de>,
	kyungmin.park@samsung.com,
	Jagan Teki <jagan@amarulasolutions.com>,
	andrzej.hajda@intel.com, m.szyprowski@samsung.com,
	linux-amarula@amarulasolutions.com,
	linux-arm-kernel@lists.infradead.org,
	Laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH v12 00/18] drm: Add Samsung MIPI DSIM bridge
Date: Fri, 17 Feb 2023 11:05:15 +0100	[thread overview]
Message-ID: <9068722.CDJkKcVGEf@steina-w> (raw)
In-Reply-To: <25ae1824-4f00-4337-4512-0d8190981fb6@prevas.dk>

Am Freitag, 17. Februar 2023, 09:55:22 CET schrieb Rasmus Villemoes:
> On 14/02/2023 12.09, Fabio Estevam wrote:
> > Hi Rasmus,
> > 
> > On Tue, Feb 14, 2023 at 7:55 AM Rasmus Villemoes
> > 
> > <rasmus.villemoes@prevas.dk> wrote:
> >> 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?
> > 
> > I don't have access to an imx8mp-evk, but I tested the ADV7535 MIPI to
> > HDMI daughter card on an imx8mm-evk.
> > 
> > Some extra ADV7535 patches were needed. Please check patches 0020-0023
> > and see if they help.
> 
> Thanks, but they don't seem to make a difference.
> 
> I've started trying to simply compare registers between the NXP 5.15
> kernel and the imx8mm-dsi-v12 branch with Marek's patch on top. Already
> in MEDIA_BLK_CTRL, 0x32ec0000, there's something interesting:
> 
>  ## Media Mix Clock Enable Register
> -CLK_EN                 0004    0080e133
> +CLK_EN                 0004    00800133
>  ## MIPI PHY Control Register
> -MIPI_RESET_DIV         0008    40030000
> +MIPI_RESET_DIV         0008    00020000
> 
> So with the NXP kernel, there are three bits set in CLK_EN which are not
> set with the "mainline", but those bits are marked reserved in the RM,
> so I have no idea if they are just some RO bits that get set due to some
> other munging. Then there's the MIPI_RESET_DIV register where bits 16
> and 30 do not get set. Of course, there are lots of other differences,
> but perhaps this gives somebody an idea.

Looking at drivers/soc/imx/imx8m-blk-ctrl.c the bits for MIPI_RESET_DIV are
16: MIPI_CSI1
17: MIPI_DSI
30: MIPI_CSI2
So i think that's okay here.

Best regards,
Alexander
-- 
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/



WARNING: multiple messages have this Message-ID (diff)
From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Cc: Fabio Estevam <festevam@gmail.com>,
	dri-devel@lists.freedesktop.org, Marek Vasut <marex@denx.de>,
	linux-samsung-soc@vger.kernel.org, matteo.lisi@engicam.com,
	aford173@gmail.com, dri-devel@lists.freedesktop.org,
	sw0312.kim@samsung.com, linux-imx@nxp.com,
	Frieder Schrempf <frieder.schrempf@kontron.de>,
	kyungmin.park@samsung.com,
	Jagan Teki <jagan@amarulasolutions.com>,
	andrzej.hajda@intel.com, m.szyprowski@samsung.com,
	linux-amarula@amarulasolutions.com,
	linux-arm-kernel@lists.infradead.org,
	Laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH v12 00/18] drm: Add Samsung MIPI DSIM bridge
Date: Fri, 17 Feb 2023 11:05:15 +0100	[thread overview]
Message-ID: <9068722.CDJkKcVGEf@steina-w> (raw)
In-Reply-To: <25ae1824-4f00-4337-4512-0d8190981fb6@prevas.dk>

Am Freitag, 17. Februar 2023, 09:55:22 CET schrieb Rasmus Villemoes:
> On 14/02/2023 12.09, Fabio Estevam wrote:
> > Hi Rasmus,
> > 
> > On Tue, Feb 14, 2023 at 7:55 AM Rasmus Villemoes
> > 
> > <rasmus.villemoes@prevas.dk> wrote:
> >> 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?
> > 
> > I don't have access to an imx8mp-evk, but I tested the ADV7535 MIPI to
> > HDMI daughter card on an imx8mm-evk.
> > 
> > Some extra ADV7535 patches were needed. Please check patches 0020-0023
> > and see if they help.
> 
> Thanks, but they don't seem to make a difference.
> 
> I've started trying to simply compare registers between the NXP 5.15
> kernel and the imx8mm-dsi-v12 branch with Marek's patch on top. Already
> in MEDIA_BLK_CTRL, 0x32ec0000, there's something interesting:
> 
>  ## Media Mix Clock Enable Register
> -CLK_EN                 0004    0080e133
> +CLK_EN                 0004    00800133
>  ## MIPI PHY Control Register
> -MIPI_RESET_DIV         0008    40030000
> +MIPI_RESET_DIV         0008    00020000
> 
> So with the NXP kernel, there are three bits set in CLK_EN which are not
> set with the "mainline", but those bits are marked reserved in the RM,
> so I have no idea if they are just some RO bits that get set due to some
> other munging. Then there's the MIPI_RESET_DIV register where bits 16
> and 30 do not get set. Of course, there are lots of other differences,
> but perhaps this gives somebody an idea.

Looking at drivers/soc/imx/imx8m-blk-ctrl.c the bits for MIPI_RESET_DIV are
16: MIPI_CSI1
17: MIPI_DSI
30: MIPI_CSI2
So i think that's okay here.

Best regards,
Alexander
-- 
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Cc: Marek Vasut <marex@denx.de>,
	linux-samsung-soc@vger.kernel.org,
	Laurent.pinchart@ideasonboard.com, matteo.lisi@engicam.com,
	sw0312.kim@samsung.com, dri-devel@lists.freedesktop.org,
	Frieder Schrempf <frieder.schrempf@kontron.de>,
	kyungmin.park@samsung.com, linux-imx@nxp.com,
	andrzej.hajda@intel.com, m.szyprowski@samsung.com,
	aford173@gmail.com, linux-amarula@amarulasolutions.com,
	linux-arm-kernel@lists.infradead.org,
	Jagan Teki <jagan@amarulasolutions.com>
Subject: Re: [PATCH v12 00/18] drm: Add Samsung MIPI DSIM bridge
Date: Fri, 17 Feb 2023 11:05:15 +0100	[thread overview]
Message-ID: <9068722.CDJkKcVGEf@steina-w> (raw)
In-Reply-To: <25ae1824-4f00-4337-4512-0d8190981fb6@prevas.dk>

Am Freitag, 17. Februar 2023, 09:55:22 CET schrieb Rasmus Villemoes:
> On 14/02/2023 12.09, Fabio Estevam wrote:
> > Hi Rasmus,
> > 
> > On Tue, Feb 14, 2023 at 7:55 AM Rasmus Villemoes
> > 
> > <rasmus.villemoes@prevas.dk> wrote:
> >> 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?
> > 
> > I don't have access to an imx8mp-evk, but I tested the ADV7535 MIPI to
> > HDMI daughter card on an imx8mm-evk.
> > 
> > Some extra ADV7535 patches were needed. Please check patches 0020-0023
> > and see if they help.
> 
> Thanks, but they don't seem to make a difference.
> 
> I've started trying to simply compare registers between the NXP 5.15
> kernel and the imx8mm-dsi-v12 branch with Marek's patch on top. Already
> in MEDIA_BLK_CTRL, 0x32ec0000, there's something interesting:
> 
>  ## Media Mix Clock Enable Register
> -CLK_EN                 0004    0080e133
> +CLK_EN                 0004    00800133
>  ## MIPI PHY Control Register
> -MIPI_RESET_DIV         0008    40030000
> +MIPI_RESET_DIV         0008    00020000
> 
> So with the NXP kernel, there are three bits set in CLK_EN which are not
> set with the "mainline", but those bits are marked reserved in the RM,
> so I have no idea if they are just some RO bits that get set due to some
> other munging. Then there's the MIPI_RESET_DIV register where bits 16
> and 30 do not get set. Of course, there are lots of other differences,
> but perhaps this gives somebody an idea.

Looking at drivers/soc/imx/imx8m-blk-ctrl.c the bits for MIPI_RESET_DIV are
16: MIPI_CSI1
17: MIPI_DSI
30: MIPI_CSI2
So i think that's okay here.

Best regards,
Alexander
-- 
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/



  reply	other threads:[~2023-02-17 10:05 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
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 [this message]
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=9068722.CDJkKcVGEf@steina-w \
    --to=alexander.stein@ew.tq-group.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=aford173@gmail.com \
    --cc=andrzej.hajda@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=festevam@gmail.com \
    --cc=frieder.schrempf@kontron.de \
    --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=rasmus.villemoes@prevas.dk \
    --cc=sw0312.kim@samsung.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.