From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/3] nvmem: rockchip-efuse: support more rockchip SoCs
Date: Thu, 01 Sep 2016 22:43:32 +0200 [thread overview]
Message-ID: <3728837.exfccSJxkh@diego> (raw)
In-Reply-To: <f9c6e53e-ae5f-d67a-3464-e10a3dee808c@linaro.org>
Hi srini,
Am Donnerstag, 1. September 2016, 21:02:23 schrieb Srinivas Kandagatla:
> On 29/08/16 10:50, Finley Xiao wrote:
> > As the timing and organization of efuse may be different
> > between rockchip SoCs, so their read function may be different.
> > We add different device tree compatible string for rockchip SoCs
> > to match their own read function.
> >
> > V3->V4:
> > - 3/3 change the type of out_value into u32 and buf into u8, their values
> >
> > come from register, use u32 and u8 may be more readable.
> >
> > Finley Xiao (3):
> > nvmem: rockchip-efuse: update compatible strings for Rockchip efuse
> > ARM: dts: rockchip: update compatible strings for Rockchip efuse
> > nvmem: rockchip-efuse: add rk3399-efuse support
>
> I can take patch 1 and 3, but dts has to go via arm soc tree.
that is really fine, and also what I somehow expect :-) .
So once you picked these two (I guess after Doug's comments are fixed) I'll
pick up the dts patch.
Heiko
prev parent reply other threads:[~2016-09-01 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 9:50 [PATCH v4 0/3] nvmem: rockchip-efuse: support more rockchip SoCs Finley Xiao
2016-08-29 9:50 ` [PATCH v4 1/3] nvmem: rockchip-efuse: update compatible strings for Rockchip efuse Finley Xiao
2016-09-02 14:16 ` Rob Herring
2016-08-29 9:50 ` [PATCH v4 2/3] ARM: dts: rockchip: " Finley Xiao
2016-08-29 9:50 ` [PATCH v4 3/3] nvmem: rockchip-efuse: add rk3399-efuse support Finley Xiao
2016-09-01 17:58 ` Doug Anderson
2016-09-01 20:02 ` [PATCH v4 0/3] nvmem: rockchip-efuse: support more rockchip SoCs Srinivas Kandagatla
2016-09-01 20:43 ` Heiko Stübner [this message]
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=3728837.exfccSJxkh@diego \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).