linux-kernel - RE: [PATCH v1 6/6] i2c: npcm: Support NPCM845

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] [thread-next>] [day] [month] [year] [list]
Message-ID: <SI2PR03MB6167FAAD0820B0A8F1305A7C902D9@SI2PR03MB6167.apcprd03.prod.outlook.com>
Date:   Tue, 8 Feb 2022 07:11:25 +0000
From:   "tali.perry@...oton.com" <tali.perry@...oton.com>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>,
        Jonathan Neuschäfer <j.neuschaefer@....net>,
        Tyrone Ting <warp5tw@...il.com>
CC:     "avifishman70@...il.com" <avifishman70@...il.com>,
        "tmaimon77@...il.com" <tmaimon77@...il.com>,
        "tali.perry1@...il.com" <tali.perry1@...il.com>,
        "venture@...gle.com" <venture@...gle.com>,
        "yuenn@...gle.com" <yuenn@...gle.com>,
        "benjaminfair@...gle.com" <benjaminfair@...gle.com>,
        "robh+dt@...nel.org" <robh+dt@...nel.org>,
        "semen.protsenko@...aro.org" <semen.protsenko@...aro.org>,
        "yangyicong@...ilicon.com" <yangyicong@...ilicon.com>,
        "wsa@...nel.org" <wsa@...nel.org>,
        "jie.deng@...el.com" <jie.deng@...el.com>,
        "sven@...npeter.dev" <sven@...npeter.dev>,
        "bence98@....bme.hu" <bence98@....bme.hu>,
        "lukas.bulwahn@...il.com" <lukas.bulwahn@...il.com>,
        "arnd@...db.de" <arnd@...db.de>, "olof@...om.net" <olof@...om.net>,
        "andriy.shevchenko@...ux.intel.com" 
        <andriy.shevchenko@...ux.intel.com>,
        "Avi.Fishman@...oton.com" <Avi.Fishman@...oton.com>,
        "tomer.maimon@...oton.com" <tomer.maimon@...oton.com>,
        "KWLIU@...oton.com" <KWLIU@...oton.com>,
        "JJLIU0@...oton.com" <JJLIU0@...oton.com>,
        "KFTING@...oton.com" <KFTING@...oton.com>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "openbmc@...ts.ozlabs.org" <openbmc@...ts.ozlabs.org>,
        "linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v1 6/6] i2c: npcm: Support NPCM845



>-----Original Message-----
>From: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
>Sent: Monday, February 7, 2022 5:27 PM
>To: Jonathan Neuschäfer <j.neuschaefer@....net>; Tyrone Ting <warp5tw@...il.com>
>Cc: avifishman70@...il.com; tmaimon77@...il.com; tali.perry1@...il.com; venture@...gle.com; yuenn@...gle.com; benjaminfair@...gle.com; robh+dt@...nel.org; semen.protsenko@...aro.org; yangyicong@...ilicon.com; wsa@...nel.org; jie.deng@...el.com; sven@...npeter.dev; bence98@....bme.hu; lukas.bulwahn@...il.com; arnd@...db.de; olof@...om.net; andriy.shevchenko@...ux.intel.com; IS20 Tali Perry <tali.perry@...oton.com>; IS20 Avi Fishman <Avi.Fishman@...oton.com>; IS20 Tomer Maimon <tomer.maimon@...oton.com>; CS20 KWLiu <KWLIU@...oton.com>; CS20 JJLiu0 <JJLIU0@...oton.com>; CS20 KFTing <KFTING@...oton.com>; devicetree@...r.kernel.org; openbmc@...ts.ozlabs.org; linux-i2c@...r.kernel.org; linux-kernel@...r.kernel.org
>Subject: Re: [PATCH v1 6/6] i2c: npcm: Support NPCM845
>
>On 07/02/2022 13:00, Jonathan Neuschäfer wrote:
>> Hello,
>>
>> On Mon, Feb 07, 2022 at 02:33:38PM +0800, Tyrone Ting wrote:
>>> From: Tyrone Ting <kfting@...oton.com>
>>>
>>> NPCM8XX uses a similar i2c module as NPCM7XX.
>>> The only difference is that the internal HW FIFO is larger.
>>>
>>> Related Makefile and Kconfig files are modified to support as well.
>>>
>>> Fixes: 56a1485b102e ("i2c: npcm7xx: Add Nuvoton NPCM I2C controller
>>> driver")
>>
>> It's not really a bug fix, but rather an additional feature.
>> Therefore, I suggest removing the Fixes tag from this patch.
>>
>>> Signed-off-by: Tyrone Ting <kfting@...oton.com>
>>> Signed-off-by: Tali Perry <tali.perry1@...il.com>
>>> ---
>> [...]
>>>  /* init register and default value required to enable module */
>>>  #define NPCM_I2CSEGCTL                     0xE4
>>> +#ifdef CONFIG_ARCH_NPCM7XX
>>>  #define NPCM_I2CSEGCTL_INIT_VAL            0x0333F000
>>> +#else
>>> +#define NPCM_I2CSEGCTL_INIT_VAL            0x9333F000
>>> +#endif
>>
>> This is going to cause problems when someone tries to compile a kernel
>> that runs on both NPCM7xx and NPCM8xx (because the driver will then
>> only work on NPCM7xx).
>
>Yes, good catch.
>
>The NPCM7XX is multiplatform, I guess NPCM8xx will be as well, so this looks like an invalid code. How such code is supposed to work on multiplatform kernel?
>


NPCM7xx and NPCM8xx are very different devices.
They share same driver sources for some of the modules but it's not ABI.
Users cannot compile a single kernel with two separate DTS.
In case of the i2c controller, the npcm7xx has a 16 byte HW FIFO,
and the NPCM8xx has 32 bytes HW FIFO.
This also means that registers fields are slightly different.
For init data we can move it to the DTS, but register field sizes
can't be handled with this approach.



>>
>> And every time another platform is added, this approach will make the
>> code less readable.
>>
>> A more future-proof approach is probably to have a struct with chip-
>> specific data (such as the I2CSECCTL initialization value), which is
>> then selected via the .data field in of_device_id.
>
>
>Best regards,
>Krzysztof

Thanks for the review!
Tali Perry, Nuvoton.
________________________________
________________________________
 The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Nuvoton is strictly prohibited; and any information in this email irrelevant to the official business of Nuvoton shall be deemed as neither given nor endorsed by Nuvoton.