mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nirujogi, Pratap" <pnirujog@amd.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
	Armin Wolf <W_Armin@gmx.de>,
	Pratap Nirujogi <pratap.nirujogi@amd.com>,
	hdegoede@redhat.com, ilpo.jarvinen@linux.intel.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 v7] platform/x86: Add AMD ISP platform config for OV05C10
Date: Tue, 29 Apr 2025 15:58:59 -0400	[thread overview]
Message-ID: <9bb289c9-6aef-4900-bd94-c4ae6b246641@amd.com> (raw)
In-Reply-To: <911a1642-2cd9-4619-b409-6df8aae82ca9@amd.com>



On 4/29/2025 3:30 PM, Mario Limonciello wrote:
>>> Hi,
>>>
>>> just a question: when will the CONFIG_AMD_ISP4 symbol be introduced?
>>>
>> CONFIG_AMD_ISP4 will be introduced in the V4L2 ISP driver patches. We 
>> are working on isp driver patches and planning to submit once the 
>> review for x86/platform and sensor driver patches completes.
>>
> 
> I had a side bar conversation with Pratap on this and that dependency 
> isn't needed right now as no symbols are used from it.
> 
> The drivers are coming in different subsystems and can be enabled 
> independently.  That dependency can be dropped for the next version.

Thanks Mario. Yes, this driver has no strict dependency on ISP driver. I 
will drop this dependency in V8.


  reply	other threads:[~2025-04-29 19:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17 18:28 Pratap Nirujogi
2025-04-22 15:37 ` Mario Limonciello
2025-04-27  0:25 ` Armin Wolf
2025-04-29 18:33   ` Nirujogi, Pratap
2025-04-29 19:30     ` Mario Limonciello
2025-04-29 19:58       ` Nirujogi, Pratap [this message]
2025-04-29 20:52     ` Armin Wolf
2025-04-29 21:25       ` Nirujogi, Pratap

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=9bb289c9-6aef-4900-bd94-c4ae6b246641@amd.com \
    --to=pnirujog@amd.com \
    --cc=W_Armin@gmx.de \
    --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®