From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Junhao Xie <bigfoot@radxa.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mtd@lists.infradead.org, Xilin Wu <sophon@radxa.com>
Subject: Re: [PATCH v2 0/2] mtd: devices: Qualcomm SCM storage support
Date: Fri, 30 Jan 2026 15:10:38 +0100 [thread overview]
Message-ID: <87ecn7jin5.fsf@bootlin.com> (raw)
In-Reply-To: <86F97239DB3D962C+98826904-6649-4c19-815d-73003c046c14@radxa.com> (Junhao Xie's message of "Fri, 30 Jan 2026 21:39:48 +0800")
Hi,
>> I don't believe you answered my question regarding how to access this
>> interface from the kernel. On many of these devices we can find the MAC
>> addresses of the system in the "DPP" partition. Do you have any ideas
>> about how we could access this from within the kernel?
>>
>> Regards,
>> Bjorn
>
> I agree with your point. I will add a module param in v3 for default
> read-only mode. e.g.: /sys/module/qcom_scm_storage/parameters/allow_write
>
> For something like the "DPP" partition, I think it's better to access it
> from userspace than from kernel.
If it's a MAC address that you are accessing, direct userspace does not
sound like a good fit. If I may, NVMEM cells are there exactly for this
purpose: identifying the content of a subpart of a storage device in a
storage agnostic way. The NVMEM cells are made available to in-kernel
drivers (ie. network devices have all the infrastructure to get the MAC
address from there) and their content is also exposed to userspace
through sysfs now.
Thanks,
Miquèl
next prev parent reply other threads:[~2026-01-30 14:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 11:44 [PATCH v2 0/2] mtd: devices: Qualcomm SCM storage support Junhao Xie
2026-01-26 11:44 ` [PATCH v2 1/2] firmware: qcom: scm: Add SCM storage interface support Junhao Xie
2026-01-28 13:39 ` Konrad Dybcio
2026-01-30 10:58 ` Junhao Xie
2026-01-26 11:44 ` [PATCH v2 2/2] mtd: devices: Add Qualcomm SCM storage driver Junhao Xie
2026-01-29 19:01 ` Miquel Raynal
2026-01-28 13:26 ` [PATCH v2 0/2] mtd: devices: Qualcomm SCM storage support Konrad Dybcio
2026-01-28 14:13 ` Miquel Raynal
2026-01-28 20:31 ` Bjorn Andersson
2026-01-29 18:38 ` Miquel Raynal
2026-01-29 13:05 ` Junhao Xie
2026-01-28 20:42 ` Bjorn Andersson
2026-01-30 13:39 ` Junhao Xie
2026-01-30 14:10 ` Miquel Raynal [this message]
2026-01-30 16:45 ` Junhao Xie
2026-02-03 14:20 ` Miquel Raynal
2026-03-13 10:16 ` Val Packett
2026-01-28 21:43 ` Trilok Soni
2026-01-29 12:47 ` Junhao Xie
2026-01-29 14:17 ` Konrad Dybcio
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=87ecn7jin5.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=andersson@kernel.org \
--cc=bigfoot@radxa.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=sophon@radxa.com \
--cc=vigneshr@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