From: Sam Edwards <cfsworks@gmail.com>
To: "Florian Fainelli" <florian.fainelli@broadcom.com>,
"Rafał Miłecki" <rafal@milecki.pl>,
"William Zhang" <william.zhang@broadcom.com>,
"Anand Gore" <anand.gore@broadcom.com>,
"Kursad Oney" <kursad.oney@broadcom.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Sam Edwards <CFSworks@gmail.com>
Subject: [PATCH v2 0/2] bcm4908: Fix secondary CPU initialization
Date: Fri, 4 Oct 2024 22:01:53 -0700 [thread overview]
Message-ID: <20241005050155.61103-1-CFSworks@gmail.com> (raw)
Hello list,
This is v2 of my previous patch [1] for resolving a problem preventing
secondary CPU(s) from coming up on bcm4908. After some discussion, I decided to
try dropping the reserved memory region from 64K to only 4K. Looks like it
works!
Changes v1->v2:
- Reduce 64K reserved region to 4K
- Style change to the `reg` property to use hex instead of decimal
- Slight rephrasing to the commit message
- Add a new patch that also moves the `cpu-release-addr` into this reserved
memory region
Cheers,
Sam
[1]: https://lore.kernel.org/lkml/20241003213007.1339811-1-CFSworks@gmail.com/T/
Sam Edwards (2):
arm64: dts: broadcom: bcmbca: bcm4908: Reserve CFE stub area
arm64: dts: broadcom: bcmbca: bcm4908: Protect cpu-release-addr
.../boot/dts/broadcom/bcmbca/bcm4908.dtsi | 18 ++++++++++++++----
1 file changed, 14 insertions(+), 4 deletions(-)
--
2.44.2
next reply other threads:[~2024-10-05 5:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-05 5:01 Sam Edwards [this message]
2024-10-05 5:01 ` [PATCH v2 1/2] arm64: dts: broadcom: bcmbca: bcm4908: Reserve CFE stub area Sam Edwards
2024-10-10 22:57 ` Florian Fainelli
2024-10-11 0:05 ` Sam Edwards
2024-11-24 17:56 ` Florian Fainelli
2024-10-05 5:01 ` [PATCH v2 2/2] arm64: dts: broadcom: bcmbca: bcm4908: Protect cpu-release-addr Sam Edwards
2024-11-24 17:56 ` Florian Fainelli
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=20241005050155.61103-1-CFSworks@gmail.com \
--to=cfsworks@gmail.com \
--cc=anand.gore@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=krzk+dt@kernel.org \
--cc=kursad.oney@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=robh@kernel.org \
--cc=william.zhang@broadcom.com \
/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).