From: Bingbu Cao <bingbu.cao@linux.intel.com>
To: Dan Scally <dan.scally@ideasonboard.com>,
bingbu.cao@intel.com, linux-media@vger.kernel.org,
sakari.ailus@linux.intel.com, andriy.shevchenko@linux.intel.com,
djrscally@gmail.com
Subject: Re: [PATCH v2] media: ipu3-cio2: support more camera sensors in cio2-bridge
Date: Fri, 31 Mar 2023 21:00:09 +0800 [thread overview]
Message-ID: <06f27826-356d-2ed1-2b28-2de59cfae14b@linux.intel.com> (raw)
In-Reply-To: <f5ce2815-a875-25a4-269d-69b30ce534b7@ideasonboard.com>
On 3/6/23 5:34 PM, Dan Scally wrote:
> Good morning Bingbu
>
> On 03/03/2023 18:15, bingbu.cao@intel.com wrote:
>> From: Bingbu Cao <bingbu.cao@intel.com>
>>
>> Add more camera sensors into the supported camera sensors list
>> to make cio2-bridge to support more camera sensors.
>>
>> Signed-off-by: Bingbu Cao <bingbu.cao@intel.com>
>
> Thanks; this looks ok to me now:
>
>
> Reviewed-by: Daniel Scally <dan.scally@ideasonboard.com>
>
Sakari,
Will you pick this change?
>> ---
>> Changes from v1:
>> - remove some sensors without available drivers
>> - add .link_frequencies for each sensor
>>
>> ---
>> drivers/media/pci/intel/ipu3/cio2-bridge.c | 8 ++++++++
>> 1 file changed, 8 insertions(+)
>>
>> diff --git a/drivers/media/pci/intel/ipu3/cio2-bridge.c b/drivers/media/pci/intel/ipu3/cio2-bridge.c
>> index dfefe0d8aa95..d59bec8a94e2 100644
>> --- a/drivers/media/pci/intel/ipu3/cio2-bridge.c
>> +++ b/drivers/media/pci/intel/ipu3/cio2-bridge.c
>> @@ -29,6 +29,14 @@ static const struct cio2_sensor_config cio2_supported_sensors[] = {
>> CIO2_SENSOR_CONFIG("INT347E", 1, 319200000),
>> /* Omnivision OV2680 */
>> CIO2_SENSOR_CONFIG("OVTI2680", 0),
>> + /* Omnivision ov8856 */
>> + CIO2_SENSOR_CONFIG("OVTI8856", 3, 180000000, 360000000, 720000000),
>> + /* Omnivision ov2740 */
>> + CIO2_SENSOR_CONFIG("INT3474", 1, 360000000),
>> + /* Hynix hi556 */
>> + CIO2_SENSOR_CONFIG("INT3537", 1, 437000000),
>> + /* Omnivision ov13b10 */
>> + CIO2_SENSOR_CONFIG("OVTIDB10", 1, 560000000),
>> };
>> static const struct cio2_property_names prop_names = {
--
Best regards,
Bingbu Cao
next prev parent reply other threads:[~2023-03-31 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 18:15 [PATCH v2] media: ipu3-cio2: support more camera sensors in cio2-bridge bingbu.cao
2023-03-06 9:34 ` Dan Scally
2023-03-31 13:00 ` Bingbu Cao [this message]
2023-03-31 13:03 ` 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=06f27826-356d-2ed1-2b28-2de59cfae14b@linux.intel.com \
--to=bingbu.cao@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=dan.scally@ideasonboard.com \
--cc=djrscally@gmail.com \
--cc=linux-media@vger.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