From: Heiko Stuebner <heiko@sntech.de>
To: vkoul@kernel.org, kishon@kernel.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
quentin.schulz@cherry.de, sebastian.reichel@collabora.com,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
dse@thaumatec.com
Subject: Re: [PATCH v5 0/2] MIPI DSI phy for rk3588
Date: Fri, 31 Jan 2025 19:25:28 +0100 [thread overview]
Message-ID: <2498993.ElGaqSPkdT@phil> (raw)
In-Reply-To: <20241203164934.1500616-1-heiko@sntech.de>
Hi phy-maintainers,
Am Dienstag, 3. Dezember 2024, 17:49:30 MEZ schrieb Heiko Stuebner:
> This adds the phy driver need for DSI output on rk3588.
>
> The phy itself is used for both DSI output and CSI input, though the
> CSI part for the whole chain needs a lot more work, so is left out for
> now and only the DSI part implemented.
>
> This allows the rk3588 with its current VOP support to drive a DSI display
> using the DSI2 controller driver I'll submit in a next step.
>
> Only generic phy interfaces are used, so the DSI part is pretty straight
> forward.
a tiny little ping :-)
Is this still in a queue, or did it fall through the cracks during xmas?
Thanks a lot
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: vkoul@kernel.org, kishon@kernel.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
quentin.schulz@cherry.de, sebastian.reichel@collabora.com,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
dse@thaumatec.com
Subject: Re: [PATCH v5 0/2] MIPI DSI phy for rk3588
Date: Fri, 31 Jan 2025 19:25:28 +0100 [thread overview]
Message-ID: <2498993.ElGaqSPkdT@phil> (raw)
In-Reply-To: <20241203164934.1500616-1-heiko@sntech.de>
Hi phy-maintainers,
Am Dienstag, 3. Dezember 2024, 17:49:30 MEZ schrieb Heiko Stuebner:
> This adds the phy driver need for DSI output on rk3588.
>
> The phy itself is used for both DSI output and CSI input, though the
> CSI part for the whole chain needs a lot more work, so is left out for
> now and only the DSI part implemented.
>
> This allows the rk3588 with its current VOP support to drive a DSI display
> using the DSI2 controller driver I'll submit in a next step.
>
> Only generic phy interfaces are used, so the DSI part is pretty straight
> forward.
a tiny little ping :-)
Is this still in a queue, or did it fall through the cracks during xmas?
Thanks a lot
Heiko
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: vkoul@kernel.org, kishon@kernel.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
quentin.schulz@cherry.de, sebastian.reichel@collabora.com,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
dse@thaumatec.com
Subject: Re: [PATCH v5 0/2] MIPI DSI phy for rk3588
Date: Fri, 31 Jan 2025 19:25:28 +0100 [thread overview]
Message-ID: <2498993.ElGaqSPkdT@phil> (raw)
In-Reply-To: <20241203164934.1500616-1-heiko@sntech.de>
Hi phy-maintainers,
Am Dienstag, 3. Dezember 2024, 17:49:30 MEZ schrieb Heiko Stuebner:
> This adds the phy driver need for DSI output on rk3588.
>
> The phy itself is used for both DSI output and CSI input, though the
> CSI part for the whole chain needs a lot more work, so is left out for
> now and only the DSI part implemented.
>
> This allows the rk3588 with its current VOP support to drive a DSI display
> using the DSI2 controller driver I'll submit in a next step.
>
> Only generic phy interfaces are used, so the DSI part is pretty straight
> forward.
a tiny little ping :-)
Is this still in a queue, or did it fall through the cracks during xmas?
Thanks a lot
Heiko
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-01-31 18:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 16:49 [PATCH v5 0/2] MIPI DSI phy for rk3588 Heiko Stuebner
2024-12-03 16:49 ` Heiko Stuebner
2024-12-03 16:49 ` Heiko Stuebner
2024-12-03 16:49 ` [PATCH v5 1/2] dt-bindings: phy: Add Rockchip MIPI C-/D-PHY schema Heiko Stuebner
2024-12-03 16:49 ` Heiko Stuebner
2024-12-03 16:49 ` Heiko Stuebner
2024-12-04 7:39 ` Krzysztof Kozlowski
2024-12-04 7:39 ` Krzysztof Kozlowski
2024-12-04 7:39 ` Krzysztof Kozlowski
2024-12-03 16:49 ` [PATCH v5 2/2] phy: rockchip: Add Samsung MIPI D-/C-PHY driver Heiko Stuebner
2024-12-03 16:49 ` Heiko Stuebner
2024-12-03 16:49 ` Heiko Stuebner
2025-01-31 16:02 ` [PATCH v5 0/2] MIPI DSI phy for rk3588 Quentin Schulz
2025-01-31 16:02 ` Quentin Schulz
2025-01-31 16:02 ` Quentin Schulz
2025-01-31 18:25 ` Heiko Stuebner [this message]
2025-01-31 18:25 ` Heiko Stuebner
2025-01-31 18:25 ` Heiko Stuebner
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=2498993.ElGaqSPkdT@phil \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dse@thaumatec.com \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=quentin.schulz@cherry.de \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=vkoul@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 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.