[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c7d8b05a-f5cb-49aa-95c0-48754fab1b7f@samsung.com>
Date: Wed, 11 Oct 2023 11:57:00 +0200
From: Marek Szyprowski <m.szyprowski@...sung.com>
To: Florian Fainelli <florian.fainelli@...adcom.com>,
linux-i2c@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Cc: Kamal Dasu <kamal.dasu@...adcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@...adcom.com>,
Andi Shyti <andi.shyti@...nel.org>,
Wolfram Sang <wsa@...nel.org>
Subject: Re: [PATCH] i2c: brcmstb: Add support for atomic transfers
On 09.10.2023 22:41, Florian Fainelli wrote:
> On 10/6/23 07:41, Marek Szyprowski wrote:
>> Add support for atomic transfers using polling mode with interrupts
>> intentionally disabled to get rid of the warning introduced by commit
>> 63b96983a5dd ("i2c: core: introduce callbacks for atomic transfers")
>> during system reboot and power-off.
>
> Is there an existing system that you have access to which needs atomic
> transfer support, or is this a forward looking change?
Frankly speaking I've observed the mentioned warning during system
reboot on RaspberryPi4 with linux-next kernel compiled from
multi_v7_defconfig. It looks that this driver is used by VC4 DRM for
DDC. This issue doesn't look critical, but the fix seems to be trivial,
thus my patch.
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
Powered by blists - more mailing lists