From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: [PATCH v1 1/1] media: ov7251: Remap "reset" to "enable" for OV7251
Date: Fri, 8 Nov 2024 18:28:05 +0200 [thread overview]
Message-ID: <Zy48Fc_nUceCs3PK@smile.fi.intel.com> (raw)
In-Reply-To: <Zy43D7wAZLrBDtiX@kekkonen.localdomain>
On Fri, Nov 08, 2024 at 04:06:39PM +0000, Sakari Ailus wrote:
> On Fri, Nov 08, 2024 at 04:50:24PM +0200, Andy Shevchenko wrote:
> > The driver of OmniVision OV7251 expects "enable" pin instead of "reset".
> > Remap "reset" to "enable" and update polarity.
> >
> > In particular, the Linux kernel can't load the camera sensor
> > driver on Microsoft Surface Book without this change:
> >
> > ov7251 i2c-INT347E:00: supply vdddo not found, using dummy regulator
> > ov7251 i2c-INT347E:00: supply vddd not found, using dummy regulator
> > ov7251 i2c-INT347E:00: supply vdda not found, using dummy regulator
> > ov7251 i2c-INT347E:00: cannot get enable gpio
> > ov7251 i2c-INT347E:00: probe with driver ov7251 failed with error -2
...
> Should this be cc'd to stable? I guess it's not exactly a fix in the driver
> but a BIOS bug, but it can be worked around in the driver. :-)
It's everything, but a BIOS bug, it's DT bug and whoever first introduced that
GPIO in the driver. Even in the DT present in kernel the pin was referred as
CAM_RST_N, which is exactly how this patch names it.
OTOH it's a fix to the driver that never worked for ACPI case, so there never
was a regression to fix.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-11-08 16:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 14:50 [PATCH v1 1/1] media: ov7251: Remap "reset" to "enable" for OV7251 Andy Shevchenko
2024-11-08 14:57 ` Hans de Goede
2024-11-08 16:06 ` Sakari Ailus
2024-11-08 16:28 ` Andy Shevchenko [this message]
2024-11-08 16:42 ` Sakari Ailus
2024-11-08 18:19 ` Hans de Goede
2024-11-11 7:55 ` Sakari Ailus
2024-11-11 9:46 ` Hans de Goede
2025-01-16 14:48 ` Andy Shevchenko
2025-01-20 9:39 ` Sakari Ailus
2025-01-20 13:30 ` Hans de Goede
2025-01-20 16:05 ` Laurent Pinchart
2025-01-20 16:37 ` Hans de Goede
2025-01-20 17:03 ` Andy Shevchenko
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=Zy48Fc_nUceCs3PK@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.