From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Umang Jain <umang.jain@ideasonboard.com>,
linux-media@vger.kernel.org, stable@vger.kernel.org,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Tommaso Merciai <tomm.merciai@gmail.com>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH v2 2/2] media: imx335: Fix reset-gpio handling
Date: Tue, 30 Jul 2024 10:42:01 +0200 [thread overview]
Message-ID: <729280cd-557f-43ba-b1a6-8d319977ca82@kernel.org> (raw)
In-Reply-To: <ZqijVf68ZQuFGKhU@kekkonen.localdomain>
On 30/07/2024 10:24, Sakari Ailus wrote:
> Hi Krzysztof,
>
> On Mon, Jul 29, 2024 at 04:09:39PM +0200, Krzysztof Kozlowski wrote:
>> On 29/07/2024 13:04, Umang Jain wrote:
>>> Rectify the logical value of reset-gpio so that it is set to
>>> 0 (disabled) during power-on and to 1 (enabled) during power-off.
>>>
>>> Meanwhile at it, set the reset-gpio to GPIO_OUT_HIGH at initialization
>>> time to make sure it starts off in reset.
>>>
>>> Fixes: 45d19b5fb9ae ("media: i2c: Add imx335 camera sensor driver")
>>> Signed-off-by: Umang Jain <umang.jain@ideasonboard.com>
>>> ---
>>> drivers/media/i2c/imx335.c | 8 ++++----
>>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>>
>>
>> This will break all the users, so no. At least not without mentioning
>> ABI break and some sort of investigating how customers or users are
>> affected.
>
> I know the original authors aren't using the driver anymore and it took
> quite a bit of time until others started to contribute to it so I suspect
> the driver hasn't been in use for that long. There are no instances of the
> device in the in-kernel DTS either.
>
> Any DTS author should have also noticed the issue but of course there's a
> risk someone could have just changed the polarity and not bothered to chech
> what it was supposed to be.
>
> I agree the commit message should be more vocal about the effects on
> existing DTS.
I can imagine that all users (out of tree, in this case) inverted
polarity in DTS based on what's implemented. You could go with some
trivial hack, like I did for one of codecs - see 738455858a2d ("ASoC:
codecs: wsa881x: Use proper shutdown GPIO polarity"), but I remember
Mark Brown rejected similar commit for newer drivers.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-07-30 8:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 11:04 [PATCH v2 0/2] media: imx335: Fix reset-gpio handling Umang Jain
2024-07-29 11:04 ` [PATCH v2 1/2] dt-bindings: imx335: Mention reset-gpio polarity Umang Jain
2024-07-29 11:10 ` Laurent Pinchart
2024-07-29 12:06 ` Umang Jain
2024-07-29 14:27 ` Laurent Pinchart
2024-07-29 13:14 ` kernel test robot
2024-07-29 14:08 ` Krzysztof Kozlowski
2024-07-29 14:20 ` Laurent Pinchart
2024-07-29 11:04 ` [PATCH v2 2/2] media: imx335: Fix reset-gpio handling Umang Jain
2024-07-29 11:13 ` Laurent Pinchart
2024-07-30 8:17 ` Sakari Ailus
2024-07-29 14:09 ` Krzysztof Kozlowski
2024-07-30 8:24 ` Sakari Ailus
2024-07-30 8:42 ` Krzysztof Kozlowski [this message]
2024-07-30 9:10 ` Laurent Pinchart
2024-07-31 5:41 ` Umang Jain
2024-07-31 9:02 ` Kieran Bingham
2024-07-31 9:06 ` Krzysztof Kozlowski
2024-07-31 9:39 ` Laurent Pinchart
2024-08-01 16:09 ` Sakari Ailus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=729280cd-557f-43ba-b1a6-8d319977ca82@kernel.org \
--to=krzk@kernel.org \
--cc=jacopo.mondi@ideasonboard.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=tomm.merciai@gmail.com \
--cc=umang.jain@ideasonboard.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox