From: Greg KH <greg@kroah.com>
To: Stephen Boyd <swboyd@chromium.org>
Cc: stable@vger.kernel.org, Sibi Sankar <sibis@codeaurora.org>,
linux-kernel@vger.kernel.org, patches@lists.linux.dev,
Evan Green <evgreen@chromium.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Alex Elder <elder@linaro.org>
Subject: Re: [PATCH] arm64: dts: qcom: sc7180-trogdor: Fixup modem memory region
Date: Thu, 27 Oct 2022 12:14:50 +0200 [thread overview]
Message-ID: <Y1paGsh1o1Y3gAR4@kroah.com> (raw)
In-Reply-To: <20221017182241.1086545-1-swboyd@chromium.org>
On Mon, Oct 17, 2022 at 11:22:41AM -0700, Stephen Boyd wrote:
> From: Sibi Sankar <sibis@codeaurora.org>
>
> commit ef9a5d188d663753e73a3c8e8910ceab8e9305c4 upstream.
>
> The modem firmware memory requirements vary between 32M/140M on
> no-lte/lte skus respectively, so fixup the modem memory region
> to reflect the requirements.
>
> Reviewed-by: Evan Green <evgreen@chromium.org>
> Signed-off-by: Sibi Sankar <sibis@codeaurora.org>
> Link: https://lore.kernel.org/r/1602786476-27833-1-git-send-email-sibis@codeaurora.org
> Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> Acked-by: Alex Elder <elder@linaro.org>
> Signed-off-by: Stephen Boyd <swboyd@chromium.org>
> ---
>
> This fixes boot of the modem on trogdor boards with the DTS from 5.10.y
> stable tree. Without this patch I run into memory assignment errors and
> then the modem fails to boot.
Now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2022-10-27 10:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 18:22 [PATCH] arm64: dts: qcom: sc7180-trogdor: Fixup modem memory region Stephen Boyd
2022-10-27 10:14 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-15 18:27 Sibi Sankar
2020-10-20 18:37 ` Evan Green
2020-11-09 19:18 ` Evan Green
2020-11-11 4:39 ` Bjorn Andersson
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=Y1paGsh1o1Y3gAR4@kroah.com \
--to=greg@kroah.com \
--cc=bjorn.andersson@linaro.org \
--cc=elder@linaro.org \
--cc=evgreen@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=sibis@codeaurora.org \
--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).