From: Xi Ruoyao <xry111@xry111.site>
To: Huacai Chen <chenhuacai@kernel.org>, Yinbo Zhu <zhuyinbo@loongson.cn>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Arnd Bergmann <arnd@arndb.de>, Hector Martin <marcan@marcan.st>,
Lubomir Rintel <lkundrak@v3.sk>,
Conor Dooley <conor.dooley@microchip.com>,
Linus Walleij <linus.walleij@linaro.org>,
Hitomi Hasegawa <hasegawa-hitomi@fujitsu.com>,
Heiko Stuebner <heiko@sntech.de>,
Brian Norris <briannorris@chromium.org>,
Sven Peter <sven@svenpeter.dev>,
loongarch@lists.linux.dev, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, soc@kernel.org
Subject: Re: [PATCH v6 1/2] soc: loongson: add GUTS driver for loongson-2 platforms
Date: Wed, 09 Nov 2022 22:00:26 +0800 [thread overview]
Message-ID: <80accd6a82d35902c08acbafcd10426b81d15bec.camel@xry111.site> (raw)
In-Reply-To: <CAAhV-H4mpNp6wEGY0xOJgf5Kjm1EKXBUZdSKoGeacN5_CVuxtA@mail.gmail.com>
On Wed, 2022-11-09 at 21:57 +0800, Huacai Chen wrote:
> Hi, Yinbo,
>
> On Fri, Nov 4, 2022 at 10:48 AM Yinbo Zhu <zhuyinbo@loongson.cn>
> wrote:
> >
> > The global utilities block controls PCIE device enabling, alternate
> > function selection for multiplexed signals, consistency of HDA, USB
> > and PCIE, configuration of memory controller, rtc controller, lio
> > controller, and clock control.
> >
> > This patch adds a driver to manage and access global utilities block
> > for loongarch architecture Loongson-2 SoCs. Initially only reading
> > SVR
> Replace loongarch with LoongArch.
>
> > and registering soc device are supported. Other guts accesses, such
> > as reading PMON configuration by default, should eventually be added
> > into this driver as well.
> Replace PMON with BIOS is better.
Or just "firmware"? I remember Xuerui (or another guy?) has said
"nobody should use the term BIOS for non-x86 platforms in 2022".
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
prev parent reply other threads:[~2022-11-09 14:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 2:48 [PATCH v6 1/2] soc: loongson: add GUTS driver for loongson-2 platforms Yinbo Zhu
2022-11-04 2:48 ` [PATCH v6 2/2] dt-bindings: soc: add loongson-2 chipid Yinbo Zhu
2022-11-09 10:04 ` Yinbo Zhu
2022-11-09 10:03 ` [PATCH v6 1/2] soc: loongson: add GUTS driver for loongson-2 platforms Yinbo Zhu
2022-11-09 10:15 ` Linus Walleij
2022-11-09 11:05 ` Krzysztof Kozlowski
2022-11-09 11:05 ` Arnd Bergmann
[not found] ` <CAAhV-H64s-2gNMd0-F21kUzieh5G-MbBnA0k6J8EP2_7SpevaA@mail.gmail.com>
2022-11-09 15:08 ` Arnd Bergmann
2022-11-11 6:08 ` Yinbo Zhu
[not found] ` <CAAhV-H4mpNp6wEGY0xOJgf5Kjm1EKXBUZdSKoGeacN5_CVuxtA@mail.gmail.com>
2022-11-09 14:00 ` Xi Ruoyao [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=80accd6a82d35902c08acbafcd10426b81d15bec.camel@xry111.site \
--to=xry111@xry111.site \
--cc=arnd@arndb.de \
--cc=briannorris@chromium.org \
--cc=chenhuacai@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=hasegawa-hitomi@fujitsu.com \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=loongarch@lists.linux.dev \
--cc=marcan@marcan.st \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.org \
--cc=sven@svenpeter.dev \
--cc=zhuyinbo@loongson.cn \
/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).