From: Catalin Marinas <catalin.marinas@arm.com>
To: David Heidelberg via B4 Relay <devnull+david.ixit.cz@kernel.org>
Cc: "David Heidelberg" <david@ixit.cz>,
"Will Deacon" <will@kernel.org>,
"Casey Connolly" <casey.connolly@linaro.org>,
"Casey Connolly" <casey@connolly.tech>,
"Joel Selvaraj" <foss@joelselvaraj.com>,
"Alexander Martinz" <amartinz@shiftphones.com>,
"Dzmitry Sankouski" <dsankouski@gmail.com>,
"Pablo Correa Gómez" <ablocorrea@hotmail.com>,
"Guido Günther" <agx@sigxcpu.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org,
"Arnd Bergmann" <arnd@arndb.de>
Subject: Re: [PATCH QUESTION] arm64: configs: Add Snapdragon 845 config fragment
Date: Wed, 26 Nov 2025 18:10:55 +0000 [thread overview]
Message-ID: <aSdCryMAOb7Qk-qq@arm.com> (raw)
In-Reply-To: <20251126-sdm845-config-question-v1-1-ffa91ed53095@ixit.cz>
On Wed, Nov 26, 2025 at 05:19:20PM +0100, David Heidelberg via B4 Relay wrote:
> From: Casey Connolly <casey.connolly@linaro.org>
>
> This fragment provides reasonable default for the mobile devices
> based on Snapdragon 845 architecture. While default config could be
> used, the reality is it brings many issues to the development workflows,
> which are much harder to address than on generic boards or devices with
> available UART console.
>
> This config fragment produces the .config used by distributions.
> It is designed to be fairly minimal and specific to the
> supported SDM845 devices whilst offering all the features you would
> expect.
>
> It disables other arm64 architectures to speed up build times and
> decrease the size of the kernel image.
>
> To generate a .config use "make defconfig sdm845.config"
>
> [David]
> - Dropped distribution specific options.
> - Added entry into the MAINTAINERS file.
[...]
> MAINTAINERS | 5 +
> arch/arm64/configs/sdm845.config | 1048 ++++++++++++++++++++++++++++++++++++++
> 2 files changed, 1053 insertions(+)
I really don't think the kernel should carry configs other than the
generic ones used by developers. We had this on arm32 but mostly because
we didn't have a single kernel image for a long time (and when we got
it, it was mostly for v7 cores). I don't want to get back to hosting a
multitude of configs in mainline.
--
Catalin
next prev parent reply other threads:[~2025-11-26 18:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 16:19 [PATCH QUESTION] arm64: configs: Add Snapdragon 845 config fragment David Heidelberg via B4 Relay
2025-11-26 18:10 ` Catalin Marinas [this message]
2025-11-26 23:10 ` David Heidelberg
2025-11-26 19:03 ` Casey Connolly
2025-11-26 22:33 ` David Heidelberg
2025-11-27 19:52 ` Guido Günther
2025-12-03 21:35 ` Arnd Bergmann
2025-12-11 10:41 ` David Heidelberg
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=aSdCryMAOb7Qk-qq@arm.com \
--to=catalin.marinas@arm.com \
--cc=ablocorrea@hotmail.com \
--cc=agx@sigxcpu.org \
--cc=amartinz@shiftphones.com \
--cc=arnd@arndb.de \
--cc=casey.connolly@linaro.org \
--cc=casey@connolly.tech \
--cc=david@ixit.cz \
--cc=devnull+david.ixit.cz@kernel.org \
--cc=dsankouski@gmail.com \
--cc=foss@joelselvaraj.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.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).