From: Stanimir Varbanov <svarbanov@suse.de>
To: Jon Hunter <jonathanh@nvidia.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>
Cc: devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
Prathamesh Shete <pshete@nvidia.com>,
Shardar Mohammed <smohammed@nvidia.com>
Subject: Re: [PATCH V2 2/2] soc/tegra: pmc: don't fail if "aotag" is not present
Date: Thu, 20 Nov 2025 12:32:23 +0200 [thread overview]
Message-ID: <ee9809e3-58e5-4a40-8c77-a8115f11c1d1@suse.de> (raw)
In-Reply-To: <20251119093729.441654-2-jonathanh@nvidia.com>
Hi Jon,
On 11/19/25 11:37 AM, Jon Hunter wrote:
> From: Prathamesh Shete <pshete@nvidia.com>
>
> The "aotog" is an optional aperture, so if that aperture is not defined
> for a given device, then initialise the 'aotag' pointer to NULL instead
> of returning an error. Note that the PMC driver will not use 'aotag'
> pointer if initialised to NULL.
>
> Co-developed-by: Shardar Mohammed <smohammed@nvidia.com>
> Signed-off-by: Shardar Mohammed <smohammed@nvidia.com>
> Signed-off-by: Prathamesh Shete <pshete@nvidia.com>
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> ---
> Changes since V2:
> - None
>
> drivers/soc/tegra/pmc.c | 13 ++++++++++---
> 1 file changed, 10 insertions(+), 3 deletions(-)
Reviewed-by: Stanimir Varbanov <svarbanov@suse.de>
Tested-by: Stanimir Varbanov <svarbanov@suse.de>
~Stan
next prev parent reply other threads:[~2025-11-20 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 9:37 [PATCH V2 1/2] dt-bindings: tegra: pmc: Update aotag as an optional aperture Jon Hunter
2025-11-19 9:37 ` [PATCH V2 2/2] soc/tegra: pmc: don't fail if "aotag" is not present Jon Hunter
2025-11-20 10:32 ` Stanimir Varbanov [this message]
2025-11-19 10:04 ` [PATCH V2 1/2] dt-bindings: tegra: pmc: Update aotag as an optional aperture Krzysztof Kozlowski
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=ee9809e3-58e5-4a40-8c77-a8115f11c1d1@suse.de \
--to=svarbanov@suse.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pshete@nvidia.com \
--cc=robh@kernel.org \
--cc=smohammed@nvidia.com \
--cc=thierry.reding@gmail.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).