From: Laurentiu Mihalcea <laurentiumihalcea111@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Shawn Guo <shawnguo@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Alexander Stein <alexander.stein@ew.tq-group.com>,
Mark Brown <broonie@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH 2/2] arm64: defconfig: enable i.MX AIPSTZ driver
Date: Fri, 1 Aug 2025 15:18:01 +0300 [thread overview]
Message-ID: <c39de58f-7fd9-40e3-b48e-b26b9b3ec5ad@gmail.com> (raw)
In-Reply-To: <CAOMZO5DfuRKYHkC8e4mNzetY204UdPDBHzUVy4M9pyjKpx401w@mail.gmail.com>
On 7/8/2025 4:39 AM, Fabio Estevam wrote:
> On Mon, Jul 7, 2025 at 8:46 PM Laurentiu Mihalcea
> <laurentiumihalcea111@gmail.com> 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).
> Shouldn't this be enabled via a select in Kconfig instead?
would've been nice but I'm not sure we have an i.MX8MP SoC-specific config option for that?
or do you have anything particular in your mind?
next prev parent reply other threads:[~2025-08-01 12:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 23:46 [PATCH 0/2] bus: imx-aipstz: fix probe-related issues Laurentiu Mihalcea
2025-07-07 23:46 ` [PATCH 1/2] bus: imx-aipstz: allow creating pdevs for child buses Laurentiu Mihalcea
2025-07-08 5:42 ` Alexander Stein
2025-07-11 8:32 ` Shawn Guo
2025-07-07 23:46 ` [PATCH 2/2] arm64: defconfig: enable i.MX AIPSTZ driver Laurentiu Mihalcea
2025-07-08 1:39 ` Fabio Estevam
2025-08-01 12:18 ` Laurentiu Mihalcea [this message]
2025-07-08 5:42 ` Alexander Stein
2025-08-01 12:11 ` 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=c39de58f-7fd9-40e3-b48e-b26b9b3ec5ad@gmail.com \
--to=laurentiumihalcea111@gmail.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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).