From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: "Mac Lu (盧孟德)" <mac.lu@mediatek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>
Cc: "Andrew-CT Chen (陳智迪)" <Andrew-CT.Chen@mediatek.com>
Subject: Re: NVMEM usage consult for device information
Date: Tue, 18 Feb 2020 09:29:39 +0000 [thread overview]
Message-ID: <6db967dc-7776-a10e-21cd-ba47ff6f02c3@linaro.org> (raw)
In-Reply-To: <57c79cb8f45449d3ba49609cdd4a0767@mtkmbs01n1.mediatek.inc>
On 18/02/2020 09:26, Mac Lu (盧孟德) wrote:
> Hi Srini:
>>Is this data stored in a non volatile memory on the SoC?
>>if yes, then we should have a proper nvmem provider driver.
>
> Yes. This data is stored in non volatile memory on the SoC.
It makes sense to have nvmem driver in that case. which can then be
used by Device Tree to retrieve the required configurations from NVMEM.
--srini
> It would be read at bootloader and delivered to kernel by DTB.
>
>
> Thanks
> Mac
>
> -----Original Message-----
> From: Srinivas Kandagatla [mailto:srinivas.kandagatla@linaro.org]
> Sent: Tuesday, February 18, 2020 5:19 PM
> To: Mac Lu (盧孟德) <mac.lu@mediatek.com>; linux-kernel@vger.kernel.org; linux-mediatek@lists.infradead.org
> Cc: Andrew-CT Chen (陳智迪) <Andrew-CT.Chen@mediatek.com>
> Subject: Re: NVMEM usage consult for device information
>
>
>
> On 18/02/2020 05:16, Mac Lu (盧孟德) wrote:
>> Hello,
>>
>> Mediatek chip have some SOC configurations and specific data which
>> would be delivered to kernel by DTB.
>>
> Is this data stored in a non volatile memory on the SoC?
> if yes, then we should have a proper nvmem provider driver.
>
> --srini
>
>> So we want to implement a new NVMEM driver to retrieve these data for
>> use by the NVMEM Framework.
>>
>> Do you agree with the usage for our application?
>>
>> Thanks
>>
>> Mac
>>
>> ************* MEDIATEK Confidentiality Notice ******************** The
>> information contained in this e-mail message (including any
>> attachments) may be confidential, proprietary, privileged, or
>> otherwise exempt from disclosure under applicable laws. It is intended
>> to be conveyed only to the designated recipient(s). Any use,
>> dissemination, distribution, printing, retaining or copying of this
>> e-mail (including its
>> attachments) by unintended recipient(s) is strictly prohibited and may
>> be unlawful. If you are not an intended recipient of this e-mail, or
>> believe that you have received this e-mail in error, please notify the
>> sender immediately (by replying to this e-mail), delete any and all
>> copies of this e-mail (including any attachments) from your system,
>> and do not disclose the content of this e-mail to any other person. Thank you!
>>
>
> ************* MEDIATEK Confidentiality Notice ********************
> The information contained in this e-mail message (including any
> attachments) may be confidential, proprietary, privileged, or otherwise
> exempt from disclosure under applicable laws. It is intended to be
> conveyed only to the designated recipient(s). Any use, dissemination,
> distribution, printing, retaining or copying of this e-mail (including its
> attachments) by unintended recipient(s) is strictly prohibited and may
> be unlawful. If you are not an intended recipient of this e-mail, or believe
> that you have received this e-mail in error, please notify the sender
> immediately (by replying to this e-mail), delete any and all copies of
> this e-mail (including any attachments) from your system, and do not
> disclose the content of this e-mail to any other person. Thank you!
>
next prev parent reply other threads:[~2020-02-18 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <06d083206a4f4f5981be9d2e628162f8@mtkmbs01n1.mediatek.inc>
2020-02-18 9:18 ` Srinivas Kandagatla
2020-02-18 9:26 ` Mac Lu (盧孟德)
2020-02-18 9:29 ` Srinivas Kandagatla [this message]
2020-02-18 9:38 ` Mac Lu (盧孟德)
2020-02-18 6:56 mac.lu
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=6db967dc-7776-a10e-21cd-ba47ff6f02c3@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=Andrew-CT.Chen@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mac.lu@mediatek.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®