From: Jan-Michael Brummer <jan.brummer@tabos.org>
To: linux-media@vger.kernel.org
Cc: sakari.ailus@linux.intel.com, mchehab@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
tian.shu.qiu@intel.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jan-Michael Brummer <jan.brummer@tabos.org>
Subject: [PATCH 0/3] media: ak7375: Add AK7377 support
Date: Sat, 29 Aug 2026 07:25:11 +0200 [thread overview]
Message-ID: <20260829052514.18178-1-jan.brummer@tabos.org> (raw)
The AK7377 drives the focus actuator of the main camera on the Fairphone
5, and is register compatible with the AK7375 already supported by this
driver: a 12 bit position in registers 0x00/0x01 shifted left by four,
and standby control in 0x02. Patches 1 and 2 add the binding and the
compatible.
Patch 3 is a fix that is independent of the above and applies to every
user of this driver. probe() calls pm_runtime_set_active() while the
regulators are still off, so the first runtime transition is a suspend
against an unpowered chip; it fails its I2C writes and then disables
regulators that were never enabled. On the Fairphone 5 that showed up
as an -ENXIO from the first resume, after which focus control stayed
dead for the whole session even though the actuator answered fine on the
bus, and as a WARN from regulator_bulk_free() on unbind.
I can send patch 3 on its own if that is easier to route - it does not
depend on the other two.
Testing: the AK7377 on a Fairphone 5, driving the lens across its range
and checking that the image comes into focus, with an out-of-tree IMX800
sensor driver. I have no AK7345 or AK7375 hardware, so patch 3 is
untested on those; the change moves the first runtime resume from probe
to the first focus request, and confirmation that this does not regress
them would be welcome.
Jan-Michael Brummer (3):
media: dt-bindings: ak7375: Add AK7377
media: i2c: ak7375: Add support for the AK7377
media: i2c: ak7375: Do not mark the VCM active before powering it
.../bindings/media/i2c/asahi-kasei,ak7375.yaml | 1 +
drivers/media/i2c/ak7375.c | 45 ++++++++++++++++---
2 files changed, 41 insertions(+), 5 deletions(-)
--
2.51.0
next reply other threads:[~2026-08-29 5:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 5:25 Jan-Michael Brummer [this message]
2026-08-29 5:25 ` [PATCH] media: dt-bindings: ak7375: Add AK7377 Jan-Michael Brummer
2026-08-29 5:25 ` [PATCH 1/2] media: i2c: ak7375: Add support for the AK7377 Jan-Michael Brummer
2026-08-29 5:25 ` [PATCH 2/2] media: i2c: ak7375: Do not mark the VCM active before powering it Jan-Michael Brummer
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=20260829052514.18178-1-jan.brummer@tabos.org \
--to=jan.brummer@tabos.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tian.shu.qiu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®