mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nipun Gupta <nipun.gupta@amd.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: maz@kernel.org, tglx@linutronix.de, jgg@ziepe.ca,
	linux-kernel@vger.kernel.org, git@amd.com,
	harpreet.anand@amd.com, pieter.jansen-van-vuuren@amd.com,
	nikhil.agarwal@amd.com, michal.simek@amd.com,
	abhijit.gangurde@amd.com
Subject: Re: [PATCH v2] cdx: add MSI support for CDX bus
Date: Mon, 26 Jun 2023 14:07:25 +0530	[thread overview]
Message-ID: <b2126d18-c9d9-0e93-952f-fbedd478b587@amd.com> (raw)
In-Reply-To: <2023062612-navigate-hyphen-6fc7@gregkh>



On 6/26/2023 1:30 PM, Greg KH wrote:
> On Mon, Jun 26, 2023 at 01:23:27PM +0530, Nipun Gupta wrote:
>>
>>
>> On 6/6/2023 4:32 PM, Nipun Gupta wrote:
>>>
>>>
>>> On 5/18/2023 5:14 PM, Nipun Gupta wrote:
>>>> Add CDX-MSI domain per CDX controller with gic-its domain as
>>>> a parent, to support MSI for CDX devices. CDX devices allocate
>>>> MSIs from the CDX domain. Also, introduce APIs to alloc and free
>>>> IRQs for CDX domain.
>>>>
>>>> In CDX subsystem firmware is a controller for all devices and
>>>> their configuration. CDX bus controller sends all the write_msi_msg
>>>> commands to firmware running on RPU and the firmware interfaces with
>>>> actual devices to pass this information to devices
>>>>
>>>> Since, CDX controller is the only way to communicate with the Firmware
>>>> for MSI write info, CDX domain per controller required in contrast to
>>>> having a CDX domain per device.
>>>>
>>>> Co-developed-by: Nikhil Agarwal <nikhil.agarwal@amd.com>
>>>> Signed-off-by: Nikhil Agarwal <nikhil.agarwal@amd.com>
>>>> Co-developed-by: Abhijit Gangurde <abhijit.gangurde@amd.com>
>>>> Signed-off-by: Abhijit Gangurde <abhijit.gangurde@amd.com>
>>>> Signed-off-by: Nipun Gupta <nipun.gupta@amd.com>
>>>> Reviewed-by: Pieter Jansen van Vuuren <pieter.jansen-van-vuuren@amd.com>
>>>> Tested-by: Nikhil Agarwal <nikhil.agarwal@amd.com>
>>>> ---
>>>>
>>>> Changes v1->v2:
>>>> - fixed scenario where msi write was called asyncronously in
>>>>     an atomic context, by using irq_chip_(un)lock, and using sync
>>>>     MCDI API for write MSI message.
>>>> - fixed broken Signed-off-by chain.
>>>
>>> Hi Thomas,
>>>
>>> Did you had a chance to look at patch v2. Please let me know in case
>>> anything else is required to be updated.
>>
>> Hi Thomas,
>>
>> A gentle reminder, could you please have a look into this updated version of
>> the patch?
> 
> It's the middle of the merge window, nothing we can do now with new
> stuff.  Perhaps resend it after 6.5-rc1 is out and you have rebased it
> against that release?

Sure, will rebase and resend after 6.5-rc1 is out.

Thanks,
Nipun

> 
> thanks,
> 
> greg k-h

      reply	other threads:[~2023-06-26  8:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18 11:44 Nipun Gupta
2023-06-06 11:02 ` Nipun Gupta
2023-06-26  7:53   ` Nipun Gupta
2023-06-26  8:00     ` Greg KH
2023-06-26  8:37       ` Nipun Gupta [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=b2126d18-c9d9-0e93-952f-fbedd478b587@amd.com \
    --to=nipun.gupta@amd.com \
    --cc=abhijit.gangurde@amd.com \
    --cc=git@amd.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=harpreet.anand@amd.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=michal.simek@amd.com \
    --cc=nikhil.agarwal@amd.com \
    --cc=pieter.jansen-van-vuuren@amd.com \
    --cc=tglx@linutronix.de \
    /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®