netdev - Re: [PATCH V2 8/8] can: flexcan: add CAN wakeup function for i.MX8QM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2bf3da55-5d25-a5b5-f265-40bdc1cd0cad@pengutronix.de>
Date:   Mon, 19 Oct 2020 11:05:12 +0200
From:   Marc Kleine-Budde <mkl@...gutronix.de>
To:     Joakim Zhang <qiangqing.zhang@....com>,
        "robh+dt@...nel.org" <robh+dt@...nel.org>,
        "shawnguo@...nel.org" <shawnguo@...nel.org>,
        "s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
        Aisheng Dong <aisheng.dong@....com>
Cc:     "kernel@...gutronix.de" <kernel@...gutronix.de>,
        dl-linux-imx <linux-imx@....com>, Ying Liu <victor.liu@....com>,
        "linux-can@...r.kernel.org" <linux-can@...r.kernel.org>,
        Pankaj Bansal <pankaj.bansal@....com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V2 8/8] can: flexcan: add CAN wakeup function for i.MX8QM

On 10/19/20 11:03 AM, Joakim Zhang wrote:
>>> include/dt-bindings/firmware/imx/rsrc.h:111:#define IMX_SC_R_CAN_0
>> 105
> 
> As I can see in rsrc.h file, it just list each resource sequentially, and there is a note in the comments:

> "Note items from list should never be changed or removed (only added to at
> the end of the list)."

So don't do it! Do not remove the CAN_0...2 :) Only add IMX_SC_R_CAN(x)

> So the driver author doesn't want any scu users to
> change these resource macro. If we only do below change for CAN, but keep
> other devices unchanged, It would be very strange. And I think this code
> change could not be accepted. There may be another consideration, now we only
> has 3 CAN instances, how can we handle if later SoCs have more CAN instances,
> and they still want to reuse this header file. This is also reason I prefer
> to use these defined macros directly in flexcan driver.
> 
> --- a/include/dt-bindings/firmware/imx/rsrc.h
> +++ b/include/dt-bindings/firmware/imx/rsrc.h
> @@ -108,9 +108,7 @@
>  #define IMX_SC_R_ADC_1                 102
>  #define IMX_SC_R_FTM_0                 103
>  #define IMX_SC_R_FTM_1                 104
> -#define IMX_SC_R_CAN_0                 105
> -#define IMX_SC_R_CAN_1                 106
> -#define IMX_SC_R_CAN_2                 107
> +#define IMX_SC_R_CAN(x)                 (105 + (x))
>  #define IMX_SC_R_DMA_1_CH0             108
>  #define IMX_SC_R_DMA_1_CH1             109
>  #define IMX_SC_R_DMA_1_CH2             110
>  
> Add @Aisheng Dong, could above code changes can be accepted by you?

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 |



Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)