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>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, soc@kernel.org,
"Ulf Hansson" <ulf.hansson@linaro.org>
Cc: "Jianmin Lv" <lvjianmin@loongson.cn>,
wanghongliang@loongson.cn, "Liu Peibao" <liupeibao@loongson.cn>,
loongson-kernel@lists.loongnix.cn, loongarch@lists.linux.dev,
"Liu Yun" <liuyun@loongson.cn>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v6 1/2] soc: dt-bindings: add loongson-2 pm
Date: Thu, 03 Aug 2023 09:44:52 +0200 [thread overview]
Message-ID: <193f9138-57e0-4d4b-8225-54d38be9bfbc@app.fastmail.com> (raw)
In-Reply-To: <20230803063703.5659-2-zhuyinbo@loongson.cn>
On Thu, Aug 3, 2023, at 08:37, Yinbo Zhu wrote:
> + loongson,suspend-address:
> + $ref: /schemas/types.yaml#/definitions/uint64
> + description:
> + The "loongson,suspend-address" is a deep sleep state (Suspend To
> + RAM) firmware entry address which was jumped from kernel and it's
> + value was dependent on specific platform firmware code. In
> + addition, the PM need according to it to indicate that current
> + SoC whether support Suspend To RAM.
> +
I just commented on this in the driver patch, assuming this
was an MMIO address, but I'm even more confused now, since
we try hard to not rely on being able to just interface with
firmware like this.
If this is executable code, where does this actually reside?
Is this some SRAM that needs to execute the suspend logic
in order to shut down memory and cache controllers? Or is
this a runtime firmware interface similar to how UEFI handles
its runtime services to keep the implementation out of
the kernel?
Does the code work with both traditional suspend-to-ram and
modern suspend-to-idle logic?
Arnd
next prev parent reply other threads:[~2023-08-03 7:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 6:37 [PATCH v6 0/2] soc: loongson2_pm: add power management support Yinbo Zhu
2023-08-03 6:37 ` [PATCH v6 1/2] soc: dt-bindings: add loongson-2 pm Yinbo Zhu
2023-08-03 7:44 ` Arnd Bergmann [this message]
2023-08-04 2:54 ` Yinbo Zhu
2023-08-12 12:25 ` Arnd Bergmann
2023-08-14 7:57 ` Yinbo Zhu
2023-08-14 8:19 ` Arnd Bergmann
2023-08-14 11:57 ` Yinbo Zhu
2023-08-14 13:41 ` Arnd Bergmann
2023-08-15 4:08 ` Yinbo Zhu
2023-08-03 6:37 ` [PATCH v6 2/2] soc: loongson2_pm: add power management support Yinbo Zhu
2023-08-03 7:02 ` Arnd Bergmann
2023-08-08 14:42 ` Ulf Hansson
2023-08-08 14:55 ` Arnd Bergmann
2023-08-22 1:03 ` [PATCH v6 0/2] " Arnd Bergmann
2023-08-22 2:31 ` patchwork-bot+linux-soc
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=193f9138-57e0-4d4b-8225-54d38be9bfbc@app.fastmail.com \
--to=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=liupeibao@loongson.cn \
--cc=liuyun@loongson.cn \
--cc=loongarch@lists.linux.dev \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=lvjianmin@loongson.cn \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=wanghongliang@loongson.cn \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.