[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87ecn7jin5.fsf@bootlin.com>
Date: Fri, 30 Jan 2026 15:10:38 +0100
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Junhao Xie <bigfoot@...xa.com>
Cc: Bjorn Andersson <andersson@...nel.org>, Konrad Dybcio
<konradybcio@...nel.org>, Richard Weinberger <richard@....at>, Vignesh
Raghavendra <vigneshr@...com>, linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mtd@...ts.infradead.org, Xilin Wu
<sophon@...xa.com>
Subject: Re: [PATCH v2 0/2] mtd: devices: Qualcomm SCM storage support
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
Powered by blists - more mailing lists