On 03/04/2023 16:40, Julien Stephan wrote: > Hi Krzysztof, > > Le lun. 3 avr. 2023 à 11:49, Krzysztof Kozlowski < > krzysztof.kozlowski@xxxxxxxxxx> a écrit : > >> On 03/04/2023 09:19, Julien Stephan wrote: >>> From: Florian Sylvestre <fsylvestre@xxxxxxxxxxxx> >>> >> >> There is no commit msg. >> >>> Signed-off-by: Florian Sylvestre <fsylvestre@xxxxxxxxxxxx> >>> Signed-off-by: Julien Stephan <jstephan@xxxxxxxxxxxx> >>> --- >>> .../bindings/phy/mediatek,csi-phy.yaml | 41 +++++++++++++++++++ >>> MAINTAINERS | 6 +++ >>> 2 files changed, 47 insertions(+) >>> create mode 100644 >> Documentation/devicetree/bindings/phy/mediatek,csi-phy.yaml >>> >>> diff --git a/Documentation/devicetree/bindings/phy/mediatek,csi-phy.yaml >> b/Documentation/devicetree/bindings/phy/mediatek,csi-phy.yaml >>> new file mode 100644 >>> index 000000000000..c026e43f35fd >>> --- /dev/null >>> +++ b/Documentation/devicetree/bindings/phy/mediatek,csi-phy.yaml >> >> Filename like compatible. >> > Should I rename the binding file > Documentation/devicetree/bindings/phy/mediatek,mt8365-mipi-csi.yaml or This. > should I rename the compatible string mediatek,csi-phy? > The csi PHY module is a module of the mt8365 soc and can possibly be used > on other mediatek soc. I think this binding is generic enough to have a > generic name, what do you think? You did not allow adding new variants, as you made it const, not enum. If there are other devices with this phy, they could be even added now. Bindings should be rather complete. Best regards, Krzysztof
