mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Yinbo Zhu" <zhuyinbo@loongson.cn>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"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 Stübner" <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
Subject: Re: [PATCH v5 1/2] soc: loongson: add GUTS driver for loongson-2 platforms
Date: Thu, 03 Nov 2022 09:53:17 +0100	[thread overview]
Message-ID: <b82c5b2c-d8a3-4b6f-9aad-0a63d2f45f08@app.fastmail.com> (raw)
In-Reply-To: <20221103081942.3529-1-zhuyinbo@loongson.cn>

On Thu, Nov 3, 2022, at 09:19, Yinbo Zhu 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
> 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.
>
> Signed-off-by: Yinbo Zhu <zhuyinbo@loongson.cn>

Looks ok to me. I can take the new driver through the SoC tree,
so please send it to soc@kernel.org once there are no more
remaining review comments that need to be addressed.

One last thing from my side, with that addressed, please add my

Reviewed-by: Arnd Bergmann <arnd@arndb.de>

> +config LOONGSON2_GUTS
> +	tristate "Loongson-2 GUTS"
> +	depends on LOONGARCH || COMPILE_TEST
> +	select SOC_BUS

In the one-line description, please spell out GUTS, since this
is not a generic term but apparently is something that is only
used on Loongarch and Layerscape.

Just for clarification: is this derived from the same IP block
that NXP are using, or is this just coincidentally named
similarly?

      Arnd

  parent reply	other threads:[~2022-11-03  8:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03  8:19 Yinbo Zhu
2022-11-03  8:19 ` [PATCH v5 2/2] dt-bindings: soc: add loongson-2 chipid Yinbo Zhu
2022-11-03  8:53 ` Arnd Bergmann [this message]
2022-11-04  2:56   ` [PATCH v5 1/2] soc: loongson: add GUTS driver for loongson-2 platforms Yinbo Zhu

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=b82c5b2c-d8a3-4b6f-9aad-0a63d2f45f08@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=briannorris@chromium.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=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

all inboxes | Powered by JetHome®