From: wens@csie.org (Chen-Yu Tsai)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/5] ARM: dts: sun8i: Add SID node
Date: Tue, 24 Nov 2015 14:42:26 +0800 [thread overview]
Message-ID: <CAGb2v67aS+2vM8CLB=4ynFOvb14t+kiWjJvAa60U2nq22S8ZEw@mail.gmail.com> (raw)
In-Reply-To: <20151124063808.GB32142@lukather>
On Tue, Nov 24, 2015 at 2:38 PM, Maxime Ripard
<maxime.ripard@free-electrons.com> wrote:
> On Tue, Nov 24, 2015 at 11:13:13AM +0800, Chen-Yu Tsai wrote:
>> Hi,
>>
>> On Mon, Nov 23, 2015 at 8:43 PM, Maxime Ripard
>> <maxime.ripard@free-electrons.com> wrote:
>> > Hi,
>> >
>> > On Mon, Nov 23, 2015 at 09:02:48AM +0100, Josef Gajdusek wrote:
>> >> Add a node describing the Security ID memory to the
>> >> Allwinner H3 .dtsi file.
>> >>
>> >> Signed-off-by: Josef Gajdusek <atx@atx.name>
>> >> ---
>> >> arch/arm/boot/dts/sun8i-h3.dtsi | 7 +++++++
>> >> 1 file changed, 7 insertions(+)
>> >>
>> >> diff --git a/arch/arm/boot/dts/sun8i-h3.dtsi b/arch/arm/boot/dts/sun8i-h3.dtsi
>> >> index 0faa38a..58de718 100644
>> >> --- a/arch/arm/boot/dts/sun8i-h3.dtsi
>> >> +++ b/arch/arm/boot/dts/sun8i-h3.dtsi
>> >> @@ -359,6 +359,13 @@
>> >> #size-cells = <0>;
>> >> };
>> >>
>> >> + sid: eeprom at 01c14000 {
>> >> + compatible = "allwinner,sun4i-a10-sid";
>> >> + reg = <0x01c14000 0x400>;
>> >
>> > The datasheet says it's 256 bytes wide, while the size here is of 1kB,
>> > is it intentional?
>>
>> My H3 datasheet (v1.1) says its 1 kB wide.
>
> Is it? in the Security ID section, it is said to be 2kb == 256B wide.
Right. I was looking at the memory map. Maybe it's sparsely mapped?
I guess we'll know soon.
ChenYu
>> It'd be nice if Allwinner actually listed the "usable" E-fuse
>> offsets and widths, instead of having us dig through the SDK code.
>
> Yep.
>
> Thanks!
> Maxime
>
> --
> Maxime Ripard, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
next prev parent reply other threads:[~2015-11-24 6:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 8:02 [PATCH v2 0/5] sunxi: THS support Josef Gajdusek
2015-11-23 8:02 ` [PATCH v2 1/5] ARM: dts: sun8i: Add SID node Josef Gajdusek
2015-11-23 12:43 ` Maxime Ripard
2015-11-24 3:13 ` Chen-Yu Tsai
2015-11-24 6:38 ` Maxime Ripard
2015-11-24 6:42 ` Chen-Yu Tsai [this message]
2015-11-24 7:26 ` Maxime Ripard
[not found] ` <077cd975-1f91-40fe-ab05-2381e4fb6448@googlegroups.com>
2015-11-24 6:38 ` Maxime Ripard
[not found] ` <a7d4e538-db64-476d-b5de-5222419229a2@googlegroups.com>
2015-11-24 9:32 ` [linux-sunxi] " Maxime Ripard
2015-11-25 1:22 ` Shuge
2015-12-01 8:41 ` Maxime Ripard
2015-11-23 8:02 ` [PATCH v2 2/5] clk: sunxi: Add driver for the H3 THS clock Josef Gajdusek
2015-11-23 10:28 ` [linux-sunxi] " Priit Laes
2015-11-23 21:37 ` Rob Herring
2015-11-23 8:02 ` [PATCH v2 3/5] thermal: Add a driver for the Allwinner THS sensor Josef Gajdusek
2015-11-24 8:43 ` Maxime Ripard
2015-11-25 11:02 ` [linux-sunxi] " Josef Gajdusek
2015-11-30 19:58 ` Maxime Ripard
2015-11-23 8:02 ` [PATCH v2 4/5] dt-bindings: document sun8i_ths Josef Gajdusek
2015-11-23 9:47 ` Chen-Yu Tsai
2015-11-23 12:38 ` Maxime Ripard
2015-11-23 8:02 ` [PATCH v2 5/5] ARM: dts: sun8i: Add THS node to the H3 .dtsi Josef Gajdusek
2015-11-24 8:45 ` 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='CAGb2v67aS+2vM8CLB=4ynFOvb14t+kiWjJvAa60U2nq22S8ZEw@mail.gmail.com' \
--to=wens@csie.org \
--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).