All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Rob Herring <robh+dt@kernel.org>
Cc: netdev <netdev@vger.kernel.org>,
	David Miller <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	linux-can@vger.kernel.org, Sascha Hauer <kernel@pengutronix.de>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Shawn Guo <shawnguo@kernel.org>
Subject: Re: pull-request: can 2020-11-11
Date: Wed, 11 Nov 2020 22:39:11 +0100	[thread overview]
Message-ID: <e138af95-b924-9d93-1f31-49628179d25b@pengutronix.de> (raw)
In-Reply-To: <CAL_JsqLCRA4ee5OYzz2FNz+WTRiCa6YEGXDoXB29PC3D9uH6EQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2138 bytes --]

On 11/11/20 8:05 PM, Rob Herring wrote:
>> after v5.10-rc1 the flexcan bindings were converted to yaml. This causes
>> several unneeded regressions on i.MX53 based boards and/or SoC specifying the
>> fsl,stop-mode property in their flexcan node.
>>
>> This series fixes these problems by first updating the affected i.MX SoC dtsi
>> files and then fixing the flexcan yaml binding.
>>
>> After I got the OK from the DT and fsl people, the plan is to upstream this via
>> net/master. If this is not an option, I'll send individual patches.
> 
> There's no need for dts changes to go into 5.10. dtbs_check is nowhere
> near warning free yet. They should go via the soc tree. The schema
> fixes do need to go in and I can take them. However, all the issues
> still aren't fixed:

Right, this shows up with the dt_binding_check...

> Documentation/devicetree/bindings/clock/imx5-clock.example.dt.yaml:
> can@53fc8000: compatible: 'oneOf' conditional failed, one must be
> fixed:
>         ['fsl,imx53-flexcan', 'fsl,p1010-flexcan'] is too long
>         Additional items are not allowed ('fsl,p1010-flexcan' was unexpected)
>         'fsl,imx53-flexcan' is not one of ['fsl,imx7d-flexcan',
> 'fsl,imx6ul-flexcan', 'fsl,imx6sx-flexcan']
>         'fsl,imx53-flexcan' is not one of ['fsl,ls1028ar1-flexcan']
>         'fsl,imx25-flexcan' was expected
>         'fsl,imx6q-flexcan' was expected
>         'fsl,lx2160ar1-flexcan' was expected
>         From schema:
> /home/rob/proj/git/linux-dt/Documentation/devicetree/bindings/net/can/fsl,flexcan.yaml
> 
> Either the imx5-clock.yaml example needs changing or the schema does.
> I'm guessing it's the former. 

Ack. I've created a patch to fix this:

http://lore.kernel.org/r/20201111213548.1621094-1-mkl@pengutronix.de

> I've applied the 2 schema patches here.

Thanks

Marc

-- 
Pengutronix e.K.                 | Marc Kleine-Budde           |
Embedded Linux                   | https://www.pengutronix.de  |
Vertretung West/Dortmund         | Phone: +49-231-2826-924     |
Amtsgericht Hildesheim, HRA 2686 | Fax:   +49-5121-206917-5555 |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Rob Herring <robh+dt@kernel.org>
Cc: netdev <netdev@vger.kernel.org>,
	linux-can@vger.kernel.org, Sascha Hauer <kernel@pengutronix.de>,
	Jakub Kicinski <kuba@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
	David Miller <davem@davemloft.net>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: pull-request: can 2020-11-11
Date: Wed, 11 Nov 2020 22:39:11 +0100	[thread overview]
Message-ID: <e138af95-b924-9d93-1f31-49628179d25b@pengutronix.de> (raw)
In-Reply-To: <CAL_JsqLCRA4ee5OYzz2FNz+WTRiCa6YEGXDoXB29PC3D9uH6EQ@mail.gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 2138 bytes --]

On 11/11/20 8:05 PM, Rob Herring wrote:
>> after v5.10-rc1 the flexcan bindings were converted to yaml. This causes
>> several unneeded regressions on i.MX53 based boards and/or SoC specifying the
>> fsl,stop-mode property in their flexcan node.
>>
>> This series fixes these problems by first updating the affected i.MX SoC dtsi
>> files and then fixing the flexcan yaml binding.
>>
>> After I got the OK from the DT and fsl people, the plan is to upstream this via
>> net/master. If this is not an option, I'll send individual patches.
> 
> There's no need for dts changes to go into 5.10. dtbs_check is nowhere
> near warning free yet. They should go via the soc tree. The schema
> fixes do need to go in and I can take them. However, all the issues
> still aren't fixed:

Right, this shows up with the dt_binding_check...

> Documentation/devicetree/bindings/clock/imx5-clock.example.dt.yaml:
> can@53fc8000: compatible: 'oneOf' conditional failed, one must be
> fixed:
>         ['fsl,imx53-flexcan', 'fsl,p1010-flexcan'] is too long
>         Additional items are not allowed ('fsl,p1010-flexcan' was unexpected)
>         'fsl,imx53-flexcan' is not one of ['fsl,imx7d-flexcan',
> 'fsl,imx6ul-flexcan', 'fsl,imx6sx-flexcan']
>         'fsl,imx53-flexcan' is not one of ['fsl,ls1028ar1-flexcan']
>         'fsl,imx25-flexcan' was expected
>         'fsl,imx6q-flexcan' was expected
>         'fsl,lx2160ar1-flexcan' was expected
>         From schema:
> /home/rob/proj/git/linux-dt/Documentation/devicetree/bindings/net/can/fsl,flexcan.yaml
> 
> Either the imx5-clock.yaml example needs changing or the schema does.
> I'm guessing it's the former. 

Ack. I've created a patch to fix this:

http://lore.kernel.org/r/20201111213548.1621094-1-mkl@pengutronix.de

> I've applied the 2 schema patches here.

Thanks

Marc

-- 
Pengutronix e.K.                 | Marc Kleine-Budde           |
Embedded Linux                   | https://www.pengutronix.de  |
Vertretung West/Dortmund         | Phone: +49-231-2826-924     |
Amtsgericht Hildesheim, HRA 2686 | Fax:   +49-5121-206917-5555 |


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-11-11 21:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <[net v2 0/4] arm: imx: flexcan: fix yaml bindings and DTs>
2020-11-11 13:05 ` pull-request: can 2020-11-11 Marc Kleine-Budde
2020-11-11 13:05   ` Marc Kleine-Budde
2020-11-11 13:05   ` [net v2 1/4] ARM: dts: imx: fix can fsl,stop-mode Marc Kleine-Budde
2020-11-11 13:05     ` Marc Kleine-Budde
2020-11-16  8:23     ` Shawn Guo
2020-11-16  8:23       ` Shawn Guo
2020-11-11 13:05   ` [net v2 2/4] ARM: dts: imx: Change flexcan node name to "can" Marc Kleine-Budde
2020-11-11 13:05     ` Marc Kleine-Budde
2020-11-16  8:24     ` Shawn Guo
2020-11-16  8:24       ` Shawn Guo
2020-11-11 13:05   ` [net v2 3/4] dt-bindings: can: fsl,flexcan.yaml: fix compatible for i.MX35 and i.MX53 Marc Kleine-Budde
2020-11-11 13:05     ` [net v2 3/4] dt-bindings: can: fsl, flexcan.yaml: " Marc Kleine-Budde
2020-11-11 13:05   ` [net v2 4/4] dt-bindings: can: fsl,flexcan.yaml: fix fsl,stop-mode Marc Kleine-Budde
2020-11-11 13:05     ` Marc Kleine-Budde
2020-11-11 19:05   ` pull-request: can 2020-11-11 Rob Herring
2020-11-11 19:05     ` Rob Herring
2020-11-11 21:39     ` Marc Kleine-Budde [this message]
2020-11-11 21:39       ` Marc Kleine-Budde

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e138af95-b924-9d93-1f31-49628179d25b@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=davem@davemloft.net \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-can@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.