mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* Re: [PATCH v3 1/2] dt-bindings: clock: mediatek: Remove compatible for MT8188 VPPSYS
       [not found] ` <20231117053934.10571-2-yu-chang.lee@mediatek.com>
@ 2023-11-19 13:13   ` Conor Dooley
  2023-11-19 13:25     ` Conor Dooley
  0 siblings, 1 reply; 2+ messages in thread
From: Conor Dooley @ 2023-11-19 13:13 UTC (permalink / raw)
  To: yu-chang.lee
  Cc: Rob Herring, Krzysztof Kozlowski, Conor Dooley,
	Michael Turquette, Stephen Boyd, Matthias Brugger,
	AngeloGioacchino Del Regno, Garmin Chang, devicetree,
	linux-kernel, linux-clk, linux-arm-kernel, linux-mediatek,
	Project_Global_Chrome_Upstream_Group

[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]

On Fri, Nov 17, 2023 at 01:39:33PM +0800, yu-chang.lee wrote:
> MT8188 VPPSYS 0/1 should be probed from mtk-mmsys driver to
> populate device by platform_device_register_data then start
> its own clock driver.

How does one operating system's driver probing model render these
compatibles invalid?

Cheers,
Conor.

> 
> Signed-off-by: yu-chang.lee <yu-chang.lee@mediatek.com>
> ---
>  .../devicetree/bindings/clock/mediatek,mt8188-clock.yaml        | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/clock/mediatek,mt8188-clock.yaml b/Documentation/devicetree/bindings/clock/mediatek,mt8188-clock.yaml
> index d7214d97b2ba..860570320545 100644
> --- a/Documentation/devicetree/bindings/clock/mediatek,mt8188-clock.yaml
> +++ b/Documentation/devicetree/bindings/clock/mediatek,mt8188-clock.yaml
> @@ -43,8 +43,6 @@ properties:
>        - mediatek,mt8188-vdecsys
>        - mediatek,mt8188-vdecsys-soc
>        - mediatek,mt8188-vencsys
> -      - mediatek,mt8188-vppsys0
> -      - mediatek,mt8188-vppsys1
>        - mediatek,mt8188-wpesys
>        - mediatek,mt8188-wpesys-vpp0
>  
> -- 
> 2.18.0
> 
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [PATCH v3 1/2] dt-bindings: clock: mediatek: Remove compatible for MT8188 VPPSYS
  2023-11-19 13:13   ` [PATCH v3 1/2] dt-bindings: clock: mediatek: Remove compatible for MT8188 VPPSYS Conor Dooley
@ 2023-11-19 13:25     ` Conor Dooley
  0 siblings, 0 replies; 2+ messages in thread
From: Conor Dooley @ 2023-11-19 13:25 UTC (permalink / raw)
  To: yu-chang.lee
  Cc: Rob Herring, Krzysztof Kozlowski, Conor Dooley,
	Michael Turquette, Stephen Boyd, Matthias Brugger,
	AngeloGioacchino Del Regno, Garmin Chang, devicetree,
	linux-kernel, linux-clk, linux-arm-kernel, linux-mediatek,
	Project_Global_Chrome_Upstream_Group

[-- Attachment #1: Type: text/plain, Size: 534 bytes --]

On Sun, Nov 19, 2023 at 01:13:47PM +0000, Conor Dooley wrote:
> On Fri, Nov 17, 2023 at 01:39:33PM +0800, yu-chang.lee wrote:
> > MT8188 VPPSYS 0/1 should be probed from mtk-mmsys driver to
> > populate device by platform_device_register_data then start
> > its own clock driver.
> 
> How does one operating system's driver probing model render these
> compatibles invalid?

I see there are 2 patches in the series. Merging them into one would
likely make it easier to explain the hardware-related reason for this
change.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2023-11-19 13:26 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20231117053934.10571-1-yu-chang.lee@mediatek.com>
     [not found] ` <20231117053934.10571-2-yu-chang.lee@mediatek.com>
2023-11-19 13:13   ` [PATCH v3 1/2] dt-bindings: clock: mediatek: Remove compatible for MT8188 VPPSYS Conor Dooley
2023-11-19 13:25     ` Conor Dooley

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®