From: "Nirujogi, Pratap" <pnirujog@amd.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
alok.a.tiwari@oracle.com, hdegoede@redhat.com, W_Armin@gmx.de,
mario.limonciello@amd.com,
"Pratap Nirujogi" <pratap.nirujogi@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 v15] platform/x86: Add AMD ISP platform config for OV05C10
Date: Thu, 15 May 2025 10:23:02 -0400 [thread overview]
Message-ID: <6b20fa34-fd57-4862-835e-2c7e874d125a@amd.com> (raw)
In-Reply-To: <174730984157.2231.15808775923608626252.b4-ty@linux.intel.com>
Hi Ilpo,
Thanks for all your support and guidance, and happy to see the patch is
accepted.
Thanks,
Pratap
On 5/15/2025 7:50 AM, Ilpo Järvinen wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
> On Wed, 14 May 2025 17:54:59 -0400, Pratap Nirujogi wrote:
>
>> ISP device specific configuration is not available in ACPI. Add
>> swnode graph to configure the missing device properties for the
>> OV05C10 camera device supported on amdisp platform.
>>
>> Add support to create i2c-client dynamically when amdisp i2c
>> adapter is available.
>>
>> [...]
>
>
> Thank you for your contribution, it has been applied to my local
> review-ilpo-next branch. Note it will show up in the public
> platform-drivers-x86/review-ilpo-next branch only once I've pushed my
> local branch there, which might take a while.
>
> The list of commits applied:
> [1/1] platform/x86: Add AMD ISP platform config for OV05C10
> commit: 90b85567e45736b662d034be536a76ba0f4c7ca8
>
> --
> i.
>
prev parent reply other threads:[~2025-05-15 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 21:54 Pratap Nirujogi
2025-05-15 11:50 ` Ilpo Järvinen
2025-05-15 14:23 ` 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=6b20fa34-fd57-4862-835e-2c7e874d125a@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®