[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<DB6PR07MB350922B1A1458EE3D7EB3F019D4E2@DB6PR07MB3509.eurprd07.prod.outlook.com>
Date: Thu, 24 Oct 2024 07:05:17 +0000
From: "Wojciech Siudy (Nokia)" <wojciech.siudy@...ia.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
CC: Rob Herring <robh@...nel.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "linux-i2c@...r.kernel.org"
<linux-i2c@...r.kernel.org>, "devicetree@...r.kernel.org"
<devicetree@...r.kernel.org>, "andi.shyti@...nel.org"
<andi.shyti@...nel.org>, "peda@...ntia.se" <peda@...ntia.se>
Subject: ODP: [PATCH v5 1/2] dt-bindings: i2c: pca954x: Add timeout reset
property
Hello,
> This is reset of the I2C devices (children), not the controller, right?
Right, the mux is child device.
> switch to reset controller framework
Please note that I left the function pca954x_reset_deassert() unchanged,
just moved it up and implemented two corresponding ones.
Do you mean that we should get rid of gpiod_set_value_cansleep(),
because the reset controller will handle it? I can agree but this is topic
for another submission since there we change when the reset is done,
not the way we achieve that.
Regards,
Wojciech
Powered by blists - more mailing lists