From: "Arnd Bergmann" <arnd@arndb.de>
To: "Beleswar Padhi" <b-padhi@ti.com>,
"Russell King" <linux@armlinux.org.uk>
Cc: "Krzysztof Kozlowski" <krzk@kernel.org>,
"Andrew Davis" <afd@ti.com>, "Udit Kumar" <u-kumar1@ti.com>,
"Praneeth Bajjuri" <praneeth@ti.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm: multi_v7_defconfig: Enable more OMAP related configs
Date: Wed, 06 Aug 2025 17:41:33 +0200 [thread overview]
Message-ID: <133a5da2-d161-411c-9cc9-0bad46ab981d@app.fastmail.com> (raw)
In-Reply-To: <20250806141808.4013462-1-b-padhi@ti.com>
On Wed, Aug 6, 2025, at 16:18, Beleswar Padhi wrote:
> From: Sinthu Raja <sinthu.raja@ti.com>
>
> This allows us to enable various peripherals in the TI OMAP family
> platforms like AM571X-IDK, AM572X-IDK, AM574X-IDK, AM57XX-BEAGLE-X15,
> AM57XX-EVM using the multi_v7_defconfig, instead of only with the
> OMAP specific defconfigs.
Hi Beleswar,
It's fine to enable drivers that are only used on a specific
platform, but those should generally be loadable modules, not
built-in.
For the generic (platform-independent) options, I would
suggest splitting them out into a separate patch, so you
can describe better what the purpose is, since this is
clearly not just for OMAP.
> IKCONFIG*:
> Allows reading the current kernel configuration through /proc/config.gz
This one seems particularly unnecessary in a "defconfig" build
since the configuration is already known based on the version.
> THERMAL_EMULATION:
> Adds emul_temp sysfs node under thermal zones to allow emulating
> temperature changes.
The documentation for this option suggests that we probably
don't want it enabled.
> FANOTIFY:
> Allows sending open file descriptors to userspace listeners along with
> file access events.
>
> USER_NS:
> NAMESPACES:
> Enable user NS to provide user info of different users for different
> process.
>
> POSIX_MQUEUE:
> Supports POSIX message queues for priority-based IPC.
>
> BSD_PROCESS_ACCT:
> Enables BSD process accounting to allow user space program to write
> process accounting information to a file.
I assume these are all in order to run a particular userspace
distro?
Arnd
next prev parent reply other threads:[~2025-08-06 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 14:18 Beleswar Padhi
2025-08-06 14:47 ` Andrew Davis
2025-08-06 15:05 ` Krzysztof Kozlowski
2025-08-06 15:41 ` Arnd Bergmann [this message]
2025-08-19 10:15 ` Beleswar Prasad Padhi
-- strict thread matches above, loose matches on Subject: below --
2025-06-11 7:49 Beleswar Padhi
2025-06-11 10:22 ` Krzysztof Kozlowski
2025-06-16 8:27 ` Beleswar Prasad Padhi
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=133a5da2-d161-411c-9cc9-0bad46ab981d@app.fastmail.com \
--to=arnd@arndb.de \
--cc=afd@ti.com \
--cc=b-padhi@ti.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=praneeth@ti.com \
--cc=u-kumar1@ti.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
all inboxes | Powered by JetHome®