[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YsPhH1sXiT/+unbj@matsya>
Date: Tue, 5 Jul 2022 12:28:39 +0530
From: Vinod Koul <vkoul@...nel.org>
To: Bo-Chen Chen <rex-bc.chen@...iatek.com>
Cc: chunkuang.hu@...nel.org, p.zabel@...gutronix.de,
chunfeng.yun@...iatek.com, kishon@...com, matthias.bgg@...il.com,
airlied@...ux.ie, msp@...libre.com, granquet@...libre.com,
jitao.shi@...iatek.com, wenst@...omium.org,
angelogioacchino.delregno@...labora.com, ck.hu@...iatek.com,
dri-devel@...ts.freedesktop.org,
linux-mediatek@...ts.infradead.org, linux-phy@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Project_Global_Chrome_Upstream_Group@...iatek.com
Subject: Re: [PATCH v12 1/1] phy: phy-mtk-dp: Add driver for DP phy
On 24-06-22, 14:27, Bo-Chen Chen wrote:
> From: Markus Schneider-Pargmann <msp@...libre.com>
>
> This is a new driver that supports the integrated DisplayPort phy for
> mediatek SoCs, especially the mt8195. The phy is integrated into the
> DisplayPort controller and will be created by the mtk-dp driver. This
> driver expects a struct regmap to be able to work on the same registers
> as the DisplayPort controller. It sets the device data to be the struct
> phy so that the DisplayPort controller can easily work with it.
>
> The driver does not have any devicetree bindings because the datasheet
> does not list the controller and the phy as distinct units.
>
> The interaction with the controller can be covered by the configure
> callback of the phy framework and its displayport parameters.
>
> Signed-off-by: Markus Schneider-Pargmann <msp@...libre.com>
> Signed-off-by: Guillaume Ranquet <granquet@...libre.com>
> [Bo-Chen: Modify reviewers' comments.]
> Signed-off-by: Bo-Chen Chen <rex-bc.chen@...iatek.com>
> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
Applied, thanks
--
~Vinod
Powered by blists - more mailing lists