mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: "Róbert Božik" <robertbozik@gmail.com>
Cc: linux-media@vger.kernel.org,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: media: i2c: Add OmniVision OV32C4
Date: Wed, 26 Aug 2026 23:47:24 +0100	[thread overview]
Message-ID: <20260826-prowling-jimmy-61f30fb50d03@spud> (raw)
In-Reply-To: <CALSBEvTvrhniBrM29Y7sery15W-onz7t_8ZQhg1TW8nBDgYKxg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]

On Wed, Aug 26, 2026 at 08:34:01PM +0200, Róbert Božik wrote:
> Hi Conor,
> 
> > Where do this name and frequency come from? pin name I presume for the
> > former? Is 19.2 MHz a mandatory frequency?

Please do normal inline replies, instead of this which removes some
context.

> The name is the sensor's input clock pin (XVCLK), as in the other
> OmniVision bindings. 19.2 MHz is not a requirement of the sensor but of
> the driver: it comes from the platform (the ACPI SSDB of the laptop this
> was developed on provides 19.2 MHz) and the register tables in the
> driver are computed for it (the internal 96 MHz clock the timing
> registers count in is 5 x 19.2 MHz). The driver refuses other rates
> because I have no verified PLL settings for them. I'll drop the
> frequency from the description and keep it only in the example and in
> the driver. I've also dropped the sentence about what the driver
> supports from the description, that doesn't describe the hardware.

Great, sounds good to me. Thanks.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2026-08-26 22:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26  7:19 [PATCH 0/3] media: Add OmniVision OV32C4 sensor driver Robert Bozik
2026-08-26  7:20 ` [PATCH 1/3] dt-bindings: media: i2c: Add OmniVision OV32C4 Robert Bozik
2026-08-26 16:13   ` Conor Dooley
     [not found]     ` <CALSBEvTvrhniBrM29Y7sery15W-onz7t_8ZQhg1TW8nBDgYKxg@mail.gmail.com>
2026-08-26 22:47       ` Conor Dooley [this message]
2026-08-28 10:18   ` Krzysztof Kozlowski
2026-08-26  7:20 ` [PATCH 2/3] media: i2c: Add driver for " Robert Bozik
2026-08-28 14:30   ` Sakari Ailus
2026-08-28 15:34     ` Robert Bozik
2026-08-26  7:20 ` [PATCH 3/3] media: ipu-bridge: Add " Robert Bozik
2026-10-05 10:50   ` 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=20260826-prowling-jimmy-61f30fb50d03@spud \
    --to=conor@kernel.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=robertbozik@gmail.com \
    --cc=robh@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 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®