On Mon, May 11, 2020 at 10:38:04AM -0500, Rob Herring wrote: > On Fri, 8 May 2020 02:07:03 +0300, Serge Semin wrote: > > There is a single register provided by the SoC system controller, > > which can be used to tune the L2-cache RAM up. It only provides a way > > to change the L2-RAM access latencies. So aside from "be,bt1-l2-ctl" > > compatible string the device node can be optionally equipped with the > > properties of Tag/Data/WS latencies. > > > > Signed-off-by: Serge Semin <[email protected]> > > Cc: Alexey Malahov <[email protected]> > > Cc: Paul Burton <[email protected]> > > Cc: Ralf Baechle <[email protected]> > > Cc: Olof Johansson <[email protected]> > > Cc: Boris Brezillon <[email protected]> > > Cc: Paul Cercueil <[email protected]> > > Cc: Thomas Gleixner <[email protected]> > > Cc: Masahiro Yamada <[email protected]> > > Cc: [email protected] > > Cc: [email protected] > > > > --- > > > > Changelog v2: > > - Move driver to the memory subsystem. > > - Use dual GPL/BSD license. > > - Use single lined copyright header. > > - Move "allOf" restrictions to the root level of the properties. > > - Discard syscon compatible string and reg property. > > - The DT node is supposed to be a child of the Baikal-T1 system controller > > node. > > --- > > .../memory-controllers/baikal,bt1-l2-ctl.yaml | 59 +++++++++++++++++++ > > 1 file changed, 59 insertions(+) > > create mode 100644 > > Documentation/devicetree/bindings/memory-controllers/baikal,bt1-l2-ctl.yaml > > > > > My bot found errors running 'make dt_binding_check' on your patch: > > [nip] ... > > See https://patchwork.ozlabs.org/patch/1285665 > > If you already ran 'make dt_binding_check' and didn't see the above > error(s), then make sure dt-schema is up to date: > > pip3 install git+https://github.com/devicetree-org/dt-schema.git@master > --upgrade > > Please check and re-submit. >
The problem is due to an absent vendor prefix in the test kernel source tree environment. As I said in the cover-letter the new vendor prefix will be added in the framework of the next patchset: https://lkml.org/lkml/2020/5/6/1047 Rob, please review that patchset first, merge in the corresponding patch from there and test this binding out then. -Sergey
