From: Christoph Hellwig <hch@infradead.org>
To: Nitin Rawat <quic_nitirawa@quicinc.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, linux-pci@vger.kernel.org,
Shaik Sajida Bhanu <quic_c_sbhanu@quicinc.com>
Subject: Re: [PATCH v3] nvme/pci: Add quick suspend quirk for Sc7280 Platform
Date: Wed, 20 Apr 2022 00:46:31 -0700 [thread overview]
Message-ID: <Yl+6V3pWuyRYuVV8@infradead.org> (raw)
In-Reply-To: <8b2735c1-4207-dc1b-45bc-33a4138b57cc@quicinc.com>
On Fri, Apr 15, 2022 at 02:29:27PM +0530, Nitin Rawat wrote:
> 1. Adding a flag notifying nvme driver about the d3 support or not - Adding
> flag to PCI bus will make it applicable to all the child devices of the
> RC/bridge and that would cause problem as this behaviour is only applicable
> for nvme device for now. Any suggestion
>
> to avoid this?
This seems like the only actual sensible option. Why would you want
to avoid it?
prev parent reply other threads:[~2022-04-20 7:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 20:53 [PATCH v3] nvme/pci: Add quick suspend quirk for Sc7280 Platform Nitin Rawat
2022-02-10 20:57 ` Keith Busch
2022-02-10 20:58 ` Nitin Rawat (QUIC)
2022-02-11 6:22 ` Christoph Hellwig
2022-02-16 16:07 ` Nitin Rawat (QUIC)
2022-02-16 16:09 ` Nitin Rawat (QUIC)
2022-02-17 2:42 ` Vidya Sagar
2022-02-16 17:12 ` Christoph Hellwig
[not found] ` <8b2735c1-4207-dc1b-45bc-33a4138b57cc@quicinc.com>
2022-04-20 7:46 ` Christoph Hellwig [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=Yl+6V3pWuyRYuVV8@infradead.org \
--to=hch@infradead.org \
--cc=axboe@fb.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=quic_c_sbhanu@quicinc.com \
--cc=quic_nitirawa@quicinc.com \
--cc=rjw@rjwysocki.net \
--cc=sagi@grimberg.me \
/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;
as well as URLs for NNTP newsgroup(s).