Messages in this thread | | | Date | Wed, 18 May 2022 10:55:51 -0500 | From | Rob Herring <> | Subject | Re: Re: [RFC v3 1/5] dt-bindings: phy: rockchip: add PCIe v3 phy |
| |
On Mon, May 16, 2022 at 09:21:31PM +0200, Frank Wunderlich wrote: > Am 16. Mai 2022 19:35:37 MESZ schrieb Rob Herring <robh@kernel.org>: > >On Sun, May 15, 2022 at 01:49:47PM +0200, Frank Wunderlich wrote: > >> Hi > >> > >> > Gesendet: Sonntag, 15. Mai 2022 um 01:14 Uhr > >> > Von: "Rob Herring" <robh@kernel.org> > >> > >> > On Sat, 14 May 2022 13:59:42 +0200, Frank Wunderlich wrote: > > >Documentation/devicetree/bindings/phy/rockchip,pcie3-phy.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: > >> > > >/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/phy/rockchip,pcie3-phy.yaml: > >properties:clock-names: 'oneOf' conditional failed, one must be fixed: > >> > [{'const': 'refclk_m'}, {'const': 'refclk_n'}, {'const': 'pclk'}] > >is too long > >> > [{'const': 'refclk_m'}, {'const': 'refclk_n'}, {'const': 'pclk'}] > >is too short > >> > False schema does not allow 3 > >> > 1 was expected > >> > 3 is greater than the maximum of 2 > >> > hint: "minItems" is only needed if less than the "items" list > >length > >> > from schema $id: http://devicetree.org/meta-schemas/items.yaml# > >> > > >/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/phy/rockchip,pcie3-phy.yaml: > >ignoring, error in schema: properties: clock-names > >> > > >Documentation/devicetree/bindings/phy/rockchip,pcie3-phy.example.dtb:0:0: > >/example-0/phy@fe8c0000: failed to match any schema with compatible: > >['rockchip,rk3568-pcie3-phy'] > >> > >> seems this is fixed when i remove the "minItems: 3" from clock names > >> (which is already fixed length because of the list). > > > >Yes. > > > >> needed to change type of lane-map to this: > >> > >> $ref: /schemas/types.yaml#/definitions/uint8-array > > > >Why? That's not a standard property though, so needs a 'rockchip' > >prefix. Though maybe a common property would be appropriate here. > > Originally it was a bool property named "rockchip,bifurcation" and we > changed it (after comments) to be a more generic property "lane-map" > that can be re-used on other vendors/controllers/phys.
Fair enough. The type needs to be defined in a common binding though. phy/phy-provider.yaml in dtschema probably.
We already have clock-lanes and data-lanes for other serdes interfaces. Maybe data-lanes works here?
> Driver reads as u8 array and range is small enough for u8 even if > used for larger controllers (e.g. PCIe x16).
Not arguing that it shouldn't be, just confused how the type was related to warnings.
> > >> then it looks clean for it.... > >> > >> -m causes many errors unrelated to this schema-file even if i pass > >> > >DT_SCHEMA_FILES=Documentation/devicetree/bindings/phy/rockchip,pcie3-phy.yaml > > > >The fix is fixing the remaining 40 or so '-m' errors. > > So now clean for you(r bot), too? Did only get a bunch of other unrelated messages.
No, the bot does a baseline build and extracts the diff in warnings. Still too many warnings popping up frequently... :(
Rob
| |