public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: "André Apitzsch" <git@apitzsch.eu>
Cc: Ricardo Ribalda <ribalda@kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	~postmarketos/upstreaming@lists.sr.ht,
	phone-devel@vger.kernel.org, linux-media@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	devicetree@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	Ricardo Ribalda <ribalda@chromium.org>,
	Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH RESEND v4 0/5] media: i2c: imx214: Add support for more clock frequencies
Date: Mon, 23 Jun 2025 11:47:21 +0000	[thread overview]
Message-ID: <aFk-yTSOqzmEW1sz@kekkonen.localdomain> (raw)
In-Reply-To: <46a681a84a7493e2d0a6d3a4eedb6c86ccd9903f.camel@apitzsch.eu>

Hi André,

On Mon, Jun 23, 2025 at 01:34:03PM +0200, André Apitzsch wrote:
> Hi Sakari,
> 
> Am Montag, dem 23.06.2025 um 06:50 +0000 schrieb Sakari Ailus:
> > Hi André,
> > 
> > On Sat, Jun 21, 2025 at 11:37:24AM +0200, André Apitzsch via B4 Relay
> > wrote:
> > > 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/
> > 
> > Is there a difference in this set from the v4 you posted previously?
> 
> There is no difference to the v4 posted previously. This is a resend
> because there was no activity in the original v4.

It's not useful to resend patches, especially those that already have been
merged somewhere. Please ping people instead.

-- 
Regards,

Sakari Ailus

  reply	other threads:[~2025-06-23 11:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-21  9:37 [PATCH RESEND v4 0/5] media: i2c: imx214: Add support for more clock frequencies André Apitzsch via B4 Relay
2025-06-21  9:37 ` [PATCH RESEND v4 1/5] media: i2c: imx214: Reorder imx214_parse_fwnode call André Apitzsch via B4 Relay
2025-06-21  9:37 ` [PATCH RESEND v4 2/5] media: i2c: imx214: Prepare for variable clock frequency André Apitzsch via B4 Relay
2025-06-21  9:37 ` [PATCH RESEND v4 3/5] media: i2c: imx214: Make use of CCS PLL calculator André Apitzsch via B4 Relay
2025-06-21 18:17   ` Laurent Pinchart
2025-06-22 15:34     ` André Apitzsch
2025-06-22 17:13       ` Laurent Pinchart
2025-06-23  9:31         ` Ricardo Ribalda Delgado
2025-06-23 11:46           ` Laurent Pinchart
2025-06-23 13:55             ` Sakari Ailus
2025-06-21  9:37 ` [PATCH RESEND v4 4/5] media: dt-bindings: sony,imx214: Deprecate property clock-frequency André Apitzsch via B4 Relay
2025-06-21  9:37 ` [PATCH RESEND v4 5/5] media: i2c: imx214: Remove hard-coded external clock frequency André Apitzsch via B4 Relay
2025-06-23  6:50 ` [PATCH RESEND v4 0/5] media: i2c: imx214: Add support for more clock frequencies Sakari Ailus
2025-06-23 11:34   ` André Apitzsch
2025-06-23 11:47     ` Sakari Ailus [this message]
2025-06-23 17:35       ` André Apitzsch

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=aFk-yTSOqzmEW1sz@kekkonen.localdomain \
    --to=sakari.ailus@linux.intel.com \
    --cc=conor+dt@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=git@apitzsch.eu \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --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=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --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