From: "André Apitzsch via B4 Relay" <devnull+git.apitzsch.eu@kernel.org>
To: Ricardo Ribalda <ribalda@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, "André Apitzsch" <git@apitzsch.eu>,
"Ricardo Ribalda" <ribalda@chromium.org>
Subject: [PATCH v2 0/4] media: i2c: imx214: Add support for more clock frequencies
Date: Mon, 05 May 2025 23:05:52 +0200 [thread overview]
Message-ID: <20250505-imx214_ccs_pll-v2-0-f50452061ff1@apitzsch.eu> (raw)
The imx214 driver currently supports only a 24 MHz external clock. But
there are devices, like Qualcomm-MSM8916-based phones, which cannot
provide this frequency. To make the sensor usable by those devices, add
support for additional clock frequencies.
This series supersedes
https://lore.kernel.org/linux-media/20250308-imx214_clk_freq-v1-0-467a4c083c35@apitzsch.eu/
Signed-off-by: André Apitzsch <git@apitzsch.eu>
---
Changes in v2:
- Add A-b tags
- Switch to v4l2_ctrl_s_ctrl_int64() to acquire the control handler mutex
- Add error handling for v4l2_ctrl_s_ctrl_int64() and
imx214_pll_update()
- Replace "read clock frequency from dt" patch by "remove hard-coded
external clock frequency" patch
- Link to v1:
https://lore.kernel.org/r/20250415-imx214_ccs_pll-v1-0-d3d7748e5fbd@apitzsch.eu
---
André Apitzsch (4):
media: i2c: imx214: Reorder imx214_parse_fwnode call
media: i2c: imx214: Prepare for variable clock frequency
media: i2c: imx214: Make use of CCS PLL calculator
media: i2c: imx214: Remove hard-coded external clock frequency
drivers/media/i2c/Kconfig | 1 +
drivers/media/i2c/imx214.c | 266 ++++++++++++++++++++++++++++++++++-----------
2 files changed, 204 insertions(+), 63 deletions(-)
---
base-commit: 4d4cc73d2632e07451c98c77fdb04aead3f78b00
change-id: 20250406-imx214_ccs_pll-e4aed0e9e532
Best regards,
--
André Apitzsch <git@apitzsch.eu>
next reply other threads:[~2025-05-05 21:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 21:05 André Apitzsch via B4 Relay [this message]
2025-05-05 21:05 ` [PATCH v2 1/4] media: i2c: imx214: Reorder imx214_parse_fwnode call André Apitzsch via B4 Relay
2025-05-05 21:05 ` [PATCH v2 2/4] media: i2c: imx214: Prepare for variable clock frequency André Apitzsch via B4 Relay
2025-05-05 21:05 ` [PATCH v2 3/4] media: i2c: imx214: Make use of CCS PLL calculator André Apitzsch via B4 Relay
2025-05-06 8:05 ` Sakari Ailus
2025-05-06 20:16 ` André Apitzsch
2025-05-06 20:53 ` Sakari Ailus
2025-05-05 21:05 ` [PATCH v2 4/4] media: i2c: imx214: Remove hard-coded external clock frequency André Apitzsch via B4 Relay
2025-05-06 8:24 ` Sakari Ailus
2025-05-14 6:46 ` André Apitzsch
2025-05-15 8:58 ` Laurent Pinchart
2025-05-15 11:54 ` Sakari Ailus
2025-05-15 13:03 ` Laurent Pinchart
2025-05-15 21:02 ` Sakari Ailus
2025-05-15 21:21 ` André Apitzsch
2025-05-21 16:50 ` Laurent Pinchart
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=20250505-imx214_ccs_pll-v2-0-f50452061ff1@apitzsch.eu \
--to=devnull+git.apitzsch.eu@kernel.org \
--cc=git@apitzsch.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=ribalda@chromium.org \
--cc=ribalda@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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;
as well as URLs for NNTP newsgroup(s).