From: Jonathan Marek <hidden> Date: 2021-06-08 19:56:03
These got lost when going from .txt to .yaml bindings, add them back.
Signed-off-by: Jonathan Marek <redacted>
---
.../bindings/display/msm/dsi-phy-7nm.yaml | 66 +++++++++++++++++++
1 file changed, 66 insertions(+)
create mode 100644 Documentation/devicetree/bindings/display/msm/dsi-phy-7nm.yaml
From: Rob Herring <robh@kernel.org> Date: 2021-06-09 16:17:20
On Tue, 08 Jun 2021 15:53:27 -0400, Jonathan Marek wrote:
These got lost when going from .txt to .yaml bindings, add them back.
Signed-off-by: Jonathan Marek <redacted>
---
.../bindings/display/msm/dsi-phy-7nm.yaml | 66 +++++++++++++++++++
1 file changed, 66 insertions(+)
create mode 100644 Documentation/devicetree/bindings/display/msm/dsi-phy-7nm.yaml
My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
on your patch (DT_CHECKER_FLAGS is new in v5.13):
yamllint warnings/errors:
dtschema/dtc warnings/errors:
Unknown file referenced: [Errno 2] No such file or directory: '/usr/local/lib/python3.8/dist-packages/dtschema/schemas/display/msm/dsi-phy-common.yaml'
xargs: dt-doc-validate: exited with status 255; aborting
Error: Documentation/devicetree/bindings/display/msm/dsi-phy-7nm.example.dts:26.38-39 syntax error
FATAL ERROR: Unable to parse input tree
make[1]: *** [scripts/Makefile.lib:380: Documentation/devicetree/bindings/display/msm/dsi-phy-7nm.example.dt.yaml] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:1416: dt_binding_check] Error 2
\ndoc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/patch/1489620
This check can fail if there are any dependencies. The base for a patch
series is generally the most recent rc1.
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:
pip3 install dtschema --upgrade
Please check and re-submit.
From: Jonathan Marek <hidden> Date: 2021-06-08 19:56:50
Document a new phy-type property which will be used to determine whether
the phy should operate in D-PHY or C-PHY mode.
Signed-off-by: Jonathan Marek <redacted>
---
.../devicetree/bindings/display/msm/dsi-phy-7nm.yaml | 4 ++++
include/dt-bindings/phy/phy.h | 2 ++
2 files changed, 6 insertions(+)
@@ -34,6 +34,10 @@ properties:description:|Connected to VDD_A_DSI_PLL_0P9 pin (or VDDA_DSI{0,1}_PLL_0P9 for sm8150)+phy-type:+description:|+D-PHY (default) or C-PHY mode:PHY_TYPE_DSI_DPHY or PHY_TYPE_DSI_CPHY+required:-compatible-reg
Hi Jonathan,
Thank you for the patch.
On Tue, Jun 08, 2021 at 03:53:28PM -0400, Jonathan Marek wrote:
quoted hunk
Document a new phy-type property which will be used to determine whether
the phy should operate in D-PHY or C-PHY mode.
Signed-off-by: Jonathan Marek <redacted>
---
.../devicetree/bindings/display/msm/dsi-phy-7nm.yaml | 4 ++++
include/dt-bindings/phy/phy.h | 2 ++
2 files changed, 6 insertions(+)
@@ -34,6 +34,10 @@ properties:description:|Connected to VDD_A_DSI_PLL_0P9 pin (or VDDA_DSI{0,1}_PLL_0P9 for sm8150)+phy-type:+description:|+D-PHY (default) or C-PHY mode:PHY_TYPE_DSI_DPHY or PHY_TYPE_DSI_CPHY+required:-compatible-reg
The MIPI D-PHY and C-PHY apply to both DSI and CSI. I'd name this
PHY_TYPE_DPHY and PHY_TYPE_CPHY, or possibly, PHY_TYPE_MIPI_DPHY and
PHY_TYPE_MIPI_CPHY, without a DSI prefix. With this addressed and the DT
bindings updated accordingly,
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
(You may be asked to split this in two patches though, not sure)
From: Rob Herring <robh@kernel.org> Date: 2021-06-09 21:57:40
On Tue, Jun 08, 2021 at 03:53:28PM -0400, Jonathan Marek wrote:
quoted hunk
Document a new phy-type property which will be used to determine whether
the phy should operate in D-PHY or C-PHY mode.
Signed-off-by: Jonathan Marek <redacted>
---
.../devicetree/bindings/display/msm/dsi-phy-7nm.yaml | 4 ++++
include/dt-bindings/phy/phy.h | 2 ++
2 files changed, 6 insertions(+)
@@ -34,6 +34,10 @@ properties:description:|Connected to VDD_A_DSI_PLL_0P9 pin (or VDDA_DSI{0,1}_PLL_0P9 for sm8150)+phy-type:+description:|+D-PHY (default) or C-PHY mode:PHY_TYPE_DSI_DPHY or PHY_TYPE_DSI_CPHY
Don't write prose for what can be schema. Unfortunately, can't do
defines here, but you need:
enum: [ 10, 11 ]
default: 10