From: Krzysztof Kozlowski <krzk@kernel.org>
To: Laurentiu Mihalcea <laurentiumihalcea111@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] arm64: defconfig: enable i.MX AIPSTZ driver
Date: Sun, 24 Aug 2025 13:27:48 +0200 [thread overview]
Message-ID: <255d3a30-9e44-41d8-8b38-ced6c245d025@kernel.org> (raw)
In-Reply-To: <20250821105634.1893-2-laurentiumihalcea111@gmail.com>
On 21/08/2025 12:56, Laurentiu Mihalcea wrote:
> From: Laurentiu Mihalcea <laurentiu.mihalcea@nxp.com>
>
> Enable the config (CONFIG_IMX_AIPSTZ) for the i.MX AIPSTZ driver, which
> is required for platforms using the AIPSTZ bridge (e.g. i.MX8MP).
Qualcomm i.MX8MP? You are changing wide defconfig.
Which boards use it?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-24 11:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 10:56 [PATCH 0/4] Switch to using AIPSTZ5 on i.MX8MP Laurentiu Mihalcea
2025-08-21 10:56 ` [PATCH 1/4] arm64: defconfig: enable i.MX AIPSTZ driver Laurentiu Mihalcea
2025-08-24 11:27 ` Krzysztof Kozlowski [this message]
2025-08-21 10:56 ` [PATCH 2/4] arm64: dts: imx8mp: convert 'aips5' to 'aipstz5' Laurentiu Mihalcea
2025-08-24 11:29 ` Krzysztof Kozlowski
2025-08-21 10:56 ` [PATCH 3/4] arm64: dts: imx8mp: add aipstz-related definitions Laurentiu Mihalcea
2025-08-24 11:29 ` Krzysztof Kozlowski
2025-08-21 10:56 ` [PATCH 4/4] arm64: dts: imx8mp: make 'dsp' node depend on 'aips5' Laurentiu Mihalcea
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=255d3a30-9e44-41d8-8b38-ced6c245d025@kernel.org \
--to=krzk@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=laurentiumihalcea111@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=will@kernel.org \
/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).