From: "Krzysztof Hałasa" <khalasa@piap.pl>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Jacopo Mondi <jacopo@jmondi.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Matteo Lisi <matteo.lisi@engicam.com>
Subject: Re: [PATCH v5] Driver for ON Semi AR0521 camera sensor
Date: Fri, 22 Oct 2021 08:42:16 +0200 [thread overview]
Message-ID: <m3bl3hd0hj.fsf@t19.piap.pl> (raw)
In-Reply-To: <YXBjX2vUwrKVOd78@valkosipuli.retiisi.eu> (Sakari Ailus's message of "Wed, 20 Oct 2021 21:43:43 +0300")
Hi Sakari,
> The drivers you're looking at are based on register lists so they usually
> support just a single frequency. The sensors are not limited to this
> frequency however, which is why you see the frequency in DT bindings, too.
Does that mean that drivers supporting a frequency range (rather than a
single frequency) don't need the range (nor single frequency) in DT?
While it's true that the AR0521 driver can (and has to) work with
different frequencies (on different systems), I think I can specify
a single frequency per system. But - should I really do that?
--
Krzysztof "Chris" Hałasa
Sieć Badawcza Łukasiewicz
Przemysłowy Instytut Automatyki i Pomiarów PIAP
Al. Jerozolimskie 202, 02-486 Warszawa
next prev parent reply other threads:[~2021-10-22 6:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 12:05 [PATCH v5] Driver for ON Semi AR0521 camera sensor Krzysztof Hałasa
2021-10-06 17:10 ` Sakari Ailus
2021-10-07 9:11 ` Krzysztof Hałasa
2021-10-09 9:07 ` Jacopo Mondi
2021-10-09 20:18 ` Randy Dunlap
2021-10-09 20:34 ` Sakari Ailus
2021-10-11 6:24 ` Krzysztof Hałasa
2021-10-11 6:20 ` Krzysztof Hałasa
2021-10-11 6:31 ` Laurent Pinchart
2021-10-12 7:52 ` Krzysztof Hałasa
2021-10-09 10:24 ` Jacopo Mondi
2021-10-11 12:19 ` Krzysztof Hałasa
2021-10-11 14:34 ` Jacopo Mondi
2021-10-11 22:22 ` Daniel Scally
2021-10-12 7:16 ` Jacopo Mondi
2021-10-12 12:24 ` Krzysztof Hałasa
2021-10-12 20:30 ` Sakari Ailus
2021-10-13 5:39 ` Krzysztof Hałasa
2021-10-20 18:43 ` Sakari Ailus
2021-10-22 6:42 ` Krzysztof Hałasa [this message]
2021-10-13 8:26 ` Jacopo Mondi
2021-10-13 12:55 ` Krzysztof Hałasa
2021-10-13 15:14 ` Jacopo Mondi
2021-10-14 5:43 ` Krzysztof Hałasa
2021-10-14 7:59 ` Jacopo Mondi
2021-10-14 10:43 ` Krzysztof Hałasa
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=m3bl3hd0hj.fsf@t19.piap.pl \
--to=khalasa@piap.pl \
--cc=jacopo@jmondi.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=matteo.lisi@engicam.com \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@iki.fi \
/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