From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: W_Armin@gmx.de, mario.limonciello@amd.com,
Hans de Goede <hansg@kernel.org>,
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,
Dominic.Antony@amd.com, Phil.Jawich@amd.com
Subject: Re: [PATCH] platform/x86: Update swnode graph for amd isp4
Date: Mon, 30 Jun 2025 12:19:44 +0300 [thread overview]
Message-ID: <175127518473.2486.7831984908188662697.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20250618202958.3934822-1-pratap.nirujogi@amd.com>
On Wed, 18 Jun 2025 16:29:48 -0400, Pratap Nirujogi wrote:
> Existing swnode graph format is specific to sensor device
> and is causing conflicts when accessing standard property
> variables outside the sensor driver.
>
> To address this issue, enhanced swnode graph format with
> dedicated nodes for i2c and isp devices, with sensor node
> added as child to i2c node. This approach allows to have
> standard property variables (ex: 'clock-frequency') with
> values applicable for each of the devices (sensor, i2c and
> isp).
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo-fixes branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-fixes branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/1] platform/x86: Update swnode graph for amd isp4
commit: e1af6f0146d64fc4fb142504ba128a97cd171558
--
i.
next prev parent reply other threads:[~2025-06-30 9:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 20:29 Pratap Nirujogi
2025-06-20 3:06 ` Mario Limonciello
2025-06-20 18:33 ` Nirujogi, Pratap
2025-06-30 9:19 ` Ilpo Järvinen [this message]
2025-06-30 15:34 ` 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=175127518473.2486.7831984908188662697.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=Dominic.Antony@amd.com \
--cc=Phil.Jawich@amd.com \
--cc=W_Armin@gmx.de \
--cc=benjamin.chan@amd.com \
--cc=bin.du@amd.com \
--cc=gjorgji.rosikopulos@amd.com \
--cc=hansg@kernel.org \
--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®