From: "Nirujogi, Pratap" <pnirujog@amd.com>
To: ALOK TIWARI <alok.a.tiwari@oracle.com>,
Pratap Nirujogi <pratap.nirujogi@amd.com>,
ilpo.jarvinen@linux.intel.com, hdegoede@redhat.com,
W_Armin@gmx.de, mario.limonciello@amd.com
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, benjamin.chan@amd.com,
bin.du@amd.com, gjorgji.rosikopulos@amd.com, king.li@amd.com,
dantony@amd.com
Subject: Re: [PATCH v14] platform/x86: Add AMD ISP platform config for OV05C10
Date: Wed, 14 May 2025 13:19:44 -0400 [thread overview]
Message-ID: <80008a56-f410-4186-8bb6-7794aa066d0e@amd.com> (raw)
In-Reply-To: <aece6449-8acd-41ae-bed6-fe5cc7d64050@oracle.com>
Hi Alok,
On 5/14/2025 4:34 AM, ALOK TIWARI wrote:
> Caution: This message originated from an External Source. Use proper
> caution when opening attachments, clicking links, or responding.
>
>
>> +config AMD_ISP_PLATFORM
>> + tristate "AMD ISP4 platform driver"
>> + depends on I2C && X86_64 && ACPI
>> + help
>> + Platform driver for AMD platforms containing image signal
>> processor
>> + gen 4. Provides camera sensor module board information to allow
>> + sensor and V4L drivers to work properly.
>> +
>> + This driver can also be built as a module. If so, the module
>
> remove extra '' before If
>
sure, will remove the extra space.
> [clip]
>> +/*
>> + * Remote endpoint AMD ISP node definition. No properties defined for
>> + * remote endpoint node for OV05C10.
>> + */
>> +static const struct software_node remote_ep_isp_node = {
>> + .name = AMDISP_OV05C10_REMOTE_EP_NAME,
>> +};
>> +
>> +/*
>> + * Remote endpoint reference for isp node included in the
>> + * OV05C10 endpoint.
>> + */
>> +static const struct software_node_ref_args ov05c10_refs[] = {
>> + SOFTWARE_NODE_REFERENCE(&remote_ep_isp_node),
>> +};
>> +
>> +/* OV05C supports one single link frequency */
>> +static const u64 ov05c10_link_freqs[] = {
>> + 925 * HZ_PER_MHZ,
>> +};
>> +
>> +/* OV05C supports only 2-lane configuration */
>> +static const u32 ov05c10_data_lanes[] = {
>> + 1,
>> + 2,
>> +};
>
> OV05C -> OV05C10
>
ok, will fix it in next patch v15.
Thanks,
Pratap
>> +
>> +/* OV05C10 endpoint node properties table */
>> +static const struct property_entry ov05c10_endpoint_props[] = {
>> + PROPERTY_ENTRY_U32("bus-type", 4),
>> + PROPERTY_ENTRY_U32_ARRAY_LEN("data-lanes", ov05c10_data_lanes,
>> + ARRAY_SIZE(ov05c10_data_lanes)),
>> + PROPERTY_ENTRY_U64_ARRAY_LEN("link-frequencies",
>> ov05c10_link_freqs,
>> + ARRAY_SIZE(ov05c10_link_freqs)),
>> + PROPERTY_ENTRY_REF_ARRAY("remote-endpoint", ov05c10_refs),
>> + { }
>> +};
>> +
> [clip]
>
>
> Thanks,
> Alok
>
>
>
prev parent reply other threads:[~2025-05-14 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 21:36 Pratap Nirujogi
2025-05-14 8:34 ` ALOK TIWARI
2025-05-14 17:19 ` Nirujogi, Pratap [this message]
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=80008a56-f410-4186-8bb6-7794aa066d0e@amd.com \
--to=pnirujog@amd.com \
--cc=W_Armin@gmx.de \
--cc=alok.a.tiwari@oracle.com \
--cc=benjamin.chan@amd.com \
--cc=bin.du@amd.com \
--cc=dantony@amd.com \
--cc=gjorgji.rosikopulos@amd.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=king.li@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pratap.nirujogi@amd.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®