From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Icenowy Zheng <icenowy@aosc.xyz>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com
Subject: Re: [PATCH v3 1/3] nvmem: sunxi-sid: read NVMEM size from device compatible
Date: Mon, 6 Feb 2017 09:48:28 +0100 [thread overview]
Message-ID: <20170206084828.s33k4fg6n7mcivb2@lukather> (raw)
In-Reply-To: <20170202131338.20234-1-icenowy@aosc.xyz>
[-- Attachment #1: Type: text/plain, Size: 610 bytes --]
On Thu, Feb 02, 2017 at 09:13:36PM +0800, Icenowy Zheng wrote:
> Sometimes the SID device have more memory address space than the real
> NVMEM size (for the registers used to read/write the SID).
>
> Fetch the NVMEM size from device compatible, rather than the memory
> address space's length, in order to prepare for adding some
> registers-based read support.
>
> Signed-off-by: Icenowy Zheng <icenowy@aosc.xyz>
Acked-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Thanks,
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next parent reply other threads:[~2017-02-06 8:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170202131338.20234-1-icenowy@aosc.xyz>
2017-02-06 8:48 ` Maxime Ripard [this message]
[not found] ` <20170202131338.20234-2-icenowy@aosc.xyz>
2017-02-06 8:54 ` [PATCH v3 2/3] nvmem: sunxi-sid: add support for H3's SID controller Maxime Ripard
[not found] ` <5119511486371415@web15m.yandex.ru>
2017-02-07 9:25 ` Maxime Ripard
[not found] ` <4664661486474595@web28j.yandex.ru>
2017-02-10 8:05 ` Maxime Ripard
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=20170206084828.s33k4fg6n7mcivb2@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=icenowy@aosc.xyz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=wens@csie.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
all inboxes | Powered by JetHome®