mbox series

[0/2] can: flexcan: fix regression from v4.16-rc1

Message ID 20180425145040.22031-1-u.kleine-koenig@pengutronix.de
Headers show
Series can: flexcan: fix regression from v4.16-rc1 | expand

Message

Uwe Kleine-König April 25, 2018, 2:50 p.m. UTC
Hello,

when porting the kernel from a i.MX25 based machine to 4.17-rc1 (but
still using the old dtb) can failed to probe. After some research we
noticed that a commit that was merged in the v4.16 merge window
introduced a change that broke using an older device tree.

This series first commit fixes the issue.
The second patch introduces a fallback compatible which matches the
usual dt-style on i.MX. (Before v4.16-rc1 there was a wrong fallback
compatible that was removed.)

Best regards
Uwe

Uwe Kleine-König (2):
  can: flexcan: fix endianess detection
  arm: dts: imx[35]*: declare flexcan devices to be compatible to
    imx25's flexcan

 arch/arm/boot/dts/imx35.dtsi |  4 ++--
 arch/arm/boot/dts/imx53.dtsi |  4 ++--
 drivers/net/can/flexcan.c    | 26 ++++++++++++++------------
 3 files changed, 18 insertions(+), 16 deletions(-)

Comments

Marc Kleine-Budde April 25, 2018, 3:07 p.m. UTC | #1
On 04/25/2018 04:50 PM, Uwe Kleine-König wrote:
> Hello,
> 
> when porting the kernel from a i.MX25 based machine to 4.17-rc1 (but
> still using the old dtb) can failed to probe. After some research we
> noticed that a commit that was merged in the v4.16 merge window
> introduced a change that broke using an older device tree.
> 
> This series first commit fixes the issue.
> The second patch introduces a fallback compatible which matches the
> usual dt-style on i.MX. (Before v4.16-rc1 there was a wrong fallback
> compatible that was removed.)

Applied both to linux-can + added stable on Cc.

Marc