From: Brad Griffis <bgriffis@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>, Ivy Huang <yijuh@nvidia.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
Sumit Gupta <sumitg@nvidia.com>
Subject: Re: [PATCH 2/2] arm64: tegra: disable Tegra234 sce-fabric node
Date: Fri, 13 Dec 2024 16:39:30 -0800 [thread overview]
Message-ID: <6a3037a1-d047-434c-a927-d21629743bf4@nvidia.com> (raw)
In-Reply-To: <l23rd5dt2it4tvh26225a5ortsl7wwhwl64tyncn33mpamdkxa@5mo7hiasunki>
On 12/13/24 02:28, Thierry Reding wrote:
> Hm... so what's the purpose of having this here if we can't use it? Are
> there cases where we might want to access this? For example, could some
> firmware *not* firewall this in some use-case, and would we want to use
> this for error reporting in such cases?
Given that this has changed once, it has hard to say definitively
whether it might ever change again. I think keeping it around in a
disabled state is reasonable.
I also find it typical that most things in the soc.dtsi are disabled by
default such that they are enabled as needed by upper layers.
prev parent reply other threads:[~2024-12-14 0:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 0:03 [PATCH 0/2] Tegra234 fabric fixes Ivy Huang
2024-12-13 0:03 ` [PATCH 1/2] arm64: tegra: fix typo in Tegra234 dce-fabric compatible Ivy Huang
2024-12-13 2:32 ` Brad Griffis
2024-12-13 9:44 ` Jon Hunter
2024-12-13 10:22 ` Thierry Reding
2024-12-13 11:11 ` Krzysztof Kozlowski
2024-12-13 11:10 ` Krzysztof Kozlowski
2024-12-18 2:08 ` Brad Griffis
2024-12-13 0:03 ` [PATCH 2/2] arm64: tegra: disable Tegra234 sce-fabric node Ivy Huang
2024-12-13 2:32 ` Brad Griffis
2024-12-13 9:45 ` Jon Hunter
2024-12-13 10:28 ` Thierry Reding
2024-12-14 0:39 ` Brad Griffis [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=6a3037a1-d047-434c-a927-d21629743bf4@nvidia.com \
--to=bgriffis@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sumitg@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=yijuh@nvidia.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