public inbox for linux-i3c@lists.infradead.org
 help / color / mirror / Atom feed
From: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Sanket.Goswami@amd.com, linux-i3c@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/5] i3c: dw: Add support for AMDI0015 ACPI ID
Date: Tue, 12 Nov 2024 18:37:59 +0530	[thread overview]
Message-ID: <6b3ec964-a756-4d4e-b629-aecaa12a4044@amd.com> (raw)
In-Reply-To: <eaca7890-af22-4913-9758-53846ad1ec79@linux.intel.com>



On 11/12/2024 15:18, Jarkko Nikula wrote:
> Hi
> 
> On 11/12/24 10:48 AM, Shyam Sundar S K wrote:
>>> Am I right this and patch 5/5 can be independent from rest of the
>>> series?
>>
>> Right. 1/5 and 5/5 can be grouped. But rest of the other patches are
>> equally important because they drive the usecase.
>>
>>>
>>> To me it looks these two patches enable bus communication and thus be
>>> useful without rest of the series while latter need more discussion
>>> (I'll have some notes coming) and Cc'ing linux-acpi.
>>
>> I have Cc'ed linux-acpi in this revision. Do you have any feedback for
>> patches 2-4 ?
>>
> Yes, I'm reviewing them and only the patch 2/5 was Cc'ed to linux-acpi.
> 
> Patchset split would serve better in my opinion enabling basic
> communication and have an other set concentrating more complex
> scenario we were try to get input from ACPI folks.

Ok. I can copy the linux-apci for patches from 2-4 after your feedback
on the current series.

Can atleast patches 1/5 and 5/5 be independently applied for -next so
they we don't miss out this cycle?

Thanks,
Shyam

-- 
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c

  reply	other threads:[~2024-11-12 13:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08  7:33 [PATCH v3 0/5] Introduce initial support for the AMD I3C (non-HCI) to DW driver Shyam Sundar S K
2024-11-08  7:33 ` [PATCH v3 1/5] i3c: dw: Add support for AMDI0015 ACPI ID Shyam Sundar S K
2024-11-12  8:16   ` Jarkko Nikula
2024-11-12  8:48     ` Shyam Sundar S K
2024-11-12  9:48       ` Jarkko Nikula
2024-11-12 13:07         ` Shyam Sundar S K [this message]
2024-11-14  8:00   ` Jarkko Nikula
2024-11-08  7:33 ` [PATCH v3 2/5] i3c: master: Add ACPI support to i3c subsystem Shyam Sundar S K
2024-11-12 15:17   ` Jarkko Nikula
2024-11-13  9:42   ` Jarkko Nikula
2024-11-13 14:21   ` Heikki Krogerus
2024-11-14  4:33     ` Shyam Sundar S K
2024-11-14  7:56       ` Alexandre Belloni
2024-11-14 11:04         ` Shyam Sundar S K
2024-11-14  8:00       ` Jarkko Nikula
2024-11-08  7:33 ` [PATCH v3 3/5] i3c: master: Add a routine to include the I3C SPD device Shyam Sundar S K
2024-11-08  7:33 ` [PATCH v3 4/5] i3c: master: Add support for SETAASA CCC Shyam Sundar S K
2024-11-13 10:00   ` Jarkko Nikula
2024-11-08  7:33 ` [PATCH v3 5/5] i3c: dw: Add quirk to address OD/PP timing issue on AMD platform Shyam Sundar S K
2024-11-14  8:01   ` Jarkko Nikula

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=6b3ec964-a756-4d4e-b629-aecaa12a4044@amd.com \
    --to=shyam-sundar.s-k@amd.com \
    --cc=Sanket.Goswami@amd.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=linux-i3c@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /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