public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: icenowy@aosc.io (Icenowy Zheng)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: dts: sunxi: Add sid for a83t
Date: Thu, 21 Dec 2017 23:07:14 +0800	[thread overview]
Message-ID: <23300841.b4klJayR8J@ice-x220i> (raw)
In-Reply-To: <20171221145512.llxvzkcrjpquhczi@flea.lan>

? 2017?12?21???? CST ??10:55:12?Maxime Ripard ???
> Hi Kyle,
> 
> On Tue, Dec 19, 2017 at 03:05:23PM -0600, kevans91 at ksu.edu wrote:
> > Allwinner a83t has a 1 KB sid block with efuse for security rootkey and
> > thermal calibration data, add node to describe it.
> > 
> > a83t-sid is not currently supported by nvmem/sunxi-sid, but it is
> > supported in an external driver for FreeBSD.
> > 
> > Signed-off-by: Kyle Evans <kevans91@ksu.edu>
> 
> The patch looks fine in itself, but we've had a number of issues with
> the register layout (and access patterns) in the past, so I'd rather
> have something that works in Linux too if possible.

I think for A83T it can just refer H3.

> 
> Maxime

  reply	other threads:[~2017-12-21 15:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 21:05 [PATCH v2] ARM: dts: sunxi: Add sid for a83t kevans91 at ksu.edu
2017-12-20 21:45 ` Rob Herring
2017-12-21 14:55 ` Maxime Ripard
2017-12-21 15:07   ` Icenowy Zheng [this message]
2017-12-21 15:19   ` Kyle Evans
2017-12-21 15:26     ` Maxime Ripard
2017-12-21 15:30       ` Kyle Evans
2017-12-21 18:09       ` Emmanuel Vadot
2017-12-22  8:35         ` Maxime Ripard
2017-12-22 10:07           ` Emmanuel Vadot
     [not found]             ` <CAGb2v64mf-ihyOs-WJZuVa4Yib3Szp90RZu_a1EeQ1LJXnoXEQ@mail.gmail.com>
2018-01-04 14:01               ` Maxime Ripard
2018-01-08 15:30                 ` Kyle Evans
2018-01-09 13:34                   ` Maxime Ripard
2018-01-09 13:55                     ` Kyle Evans
2018-04-18 14:05                     ` Kyle Evans
2018-04-19 13:38                       ` 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=23300841.b4klJayR8J@ice-x220i \
    --to=icenowy@aosc.io \
    --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