patches.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
	patches@lists.linux.dev, Alex Elder <elder@linaro.org>,
	Georgi Djakov <djakov@kernel.org>
Subject: Re: [PATCH 5.15 0/2] Fix suspend on qcom sc7180 SoCs
Date: Tue, 7 Jun 2022 11:56:25 +0200	[thread overview]
Message-ID: <Yp8gycx3v2S6drG4@kroah.com> (raw)
In-Reply-To: <20220606235155.2437168-1-swboyd@chromium.org>

On Mon, Jun 06, 2022 at 04:51:53PM -0700, Stephen Boyd wrote:
> These two patches fix suspend on sc7180 boards, i.e. Trogdor, on 5.15
> stable kernels. Without these two patches the IP0 interconnect is kept
> on forever, and suspend fails because XO shutdown can't be achieved.
> 
> Mike Tipton (1):
>   interconnect: qcom: icc-rpmh: Add BCMs to commit list in pre_aggregate
> 
> Stephen Boyd (1):
>   interconnect: qcom: sc7180: Drop IP0 interconnects
> 
>  drivers/interconnect/qcom/icc-rpmh.c | 10 +++++-----
>  drivers/interconnect/qcom/sc7180.c   | 21 ---------------------
>  drivers/interconnect/qcom/sm8150.c   |  1 -
>  drivers/interconnect/qcom/sm8250.c   |  1 -
>  drivers/interconnect/qcom/sm8350.c   |  1 -
>  5 files changed, 5 insertions(+), 29 deletions(-)
> 
> -- 
> https://chromeos.dev
>

Both now queued up, thanks.

greg k-h

      parent reply	other threads:[~2022-06-07  9:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 23:51 [PATCH 5.15 0/2] Fix suspend on qcom sc7180 SoCs Stephen Boyd
2022-06-06 23:51 ` [PATCH 5.15 1/2] interconnect: qcom: sc7180: Drop IP0 interconnects Stephen Boyd
2022-06-06 23:51 ` [PATCH 5.15 2/2] interconnect: qcom: icc-rpmh: Add BCMs to commit list in pre_aggregate Stephen Boyd
2022-06-07  9:56 ` Greg KH [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=Yp8gycx3v2S6drG4@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=djakov@kernel.org \
    --cc=elder@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=swboyd@chromium.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;
as well as URLs for NNTP newsgroup(s).