All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: bhelgaas@google.com, koba.ko@canonical.com,
	Russell Currey <ruscur@russell.cc>,
	Oliver O'Halloran <oohall@gmail.com>,
	linuxppc-dev@lists.ozlabs.org, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] PCI/DPC: Disable DPC service when link is in L2/L3 ready, L2 and L3 state
Date: Thu, 27 Jan 2022 08:31:20 +0200	[thread overview]
Message-ID: <YfI8OGuAWKtPsv+J@lahna> (raw)
In-Reply-To: <20220127025418.1989642-2-kai.heng.feng@canonical.com>

On Thu, Jan 27, 2022 at 10:54:18AM +0800, Kai-Heng Feng wrote:
> Since TLP and DLLP transmission is disabled for a Link in L2/L3 Ready,
> L2 and L3 (i.e. device in D3hot and D3cold), and DPC depends on AER, so
> also disable DPC here.
> 
> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>

Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>

WARNING: multiple messages have this Message-ID (diff)
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	koba.ko@canonical.com, Oliver O'Halloran <oohall@gmail.com>,
	bhelgaas@google.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 2/2] PCI/DPC: Disable DPC service when link is in L2/L3 ready, L2 and L3 state
Date: Thu, 27 Jan 2022 08:31:20 +0200	[thread overview]
Message-ID: <YfI8OGuAWKtPsv+J@lahna> (raw)
In-Reply-To: <20220127025418.1989642-2-kai.heng.feng@canonical.com>

On Thu, Jan 27, 2022 at 10:54:18AM +0800, Kai-Heng Feng wrote:
> Since TLP and DLLP transmission is disabled for a Link in L2/L3 Ready,
> L2 and L3 (i.e. device in D3hot and D3cold), and DPC depends on AER, so
> also disable DPC here.
> 
> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>

Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>

  reply	other threads:[~2022-01-27  6:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27  2:54 [PATCH v2 1/2] PCI/AER: Disable AER service when link is in L2/L3 ready, L2 and L3 state Kai-Heng Feng
2022-01-27  2:54 ` Kai-Heng Feng
2022-01-27  2:54 ` [PATCH v2 2/2] PCI/DPC: Disable DPC " Kai-Heng Feng
2022-01-27  2:54   ` Kai-Heng Feng
2022-01-27  6:31   ` Mika Westerberg [this message]
2022-01-27  6:31     ` Mika Westerberg
2022-03-19 20:40   ` Sathyanarayanan Kuppuswamy
2022-03-19 20:40     ` Sathyanarayanan Kuppuswamy
2022-01-27  6:30 ` [PATCH v2 1/2] PCI/AER: Disable AER " Mika Westerberg
2022-01-27  6:30   ` Mika Westerberg
2022-01-27  7:01 ` Lu Baolu
2022-01-27  7:01   ` Lu Baolu
2022-01-27 11:14   ` Kai-Heng Feng
2022-01-27 11:14     ` Kai-Heng Feng
2022-01-28  2:53     ` Lu Baolu
2022-01-28  2:53       ` Lu Baolu
2022-01-28  3:29       ` Kai-Heng Feng
2022-01-28  3:29         ` Kai-Heng Feng
2022-03-19 20:38 ` Sathyanarayanan Kuppuswamy
2022-03-19 20:38   ` Sathyanarayanan Kuppuswamy
2022-03-21  2:38   ` Kai-Heng Feng
2022-03-21  2:38     ` Kai-Heng Feng
2022-03-21  3:52     ` Sathyanarayanan Kuppuswamy
2022-03-21  3:52       ` Sathyanarayanan Kuppuswamy

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=YfI8OGuAWKtPsv+J@lahna \
    --to=mika.westerberg@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=koba.ko@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=oohall@gmail.com \
    --cc=ruscur@russell.cc \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.