From: maxime.ripard@bootlin.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: dts: sunxi: Add sid for a83t
Date: Thu, 19 Apr 2018 15:38:33 +0200 [thread overview]
Message-ID: <20180419133833.etuuxm3eygp3wfye@flea> (raw)
In-Reply-To: <CACNAnaEyKztSt_SO25e+VcmyN=fdGTVbpooWSu891ueY6xvh-g@mail.gmail.com>
On Wed, Apr 18, 2018 at 09:05:19AM -0500, Kyle Evans wrote:
> On Tue, Jan 9, 2018 at 7:34 AM, Maxime Ripard
> <maxime.ripard@free-electrons.com> wrote:
> > On Mon, Jan 08, 2018 at 09:30:57AM -0600, Kyle Evans wrote:
> >> On Thu, Jan 4, 2018 at 8:01 AM, Maxime Ripard
> >> <maxime.ripard@free-electrons.com> wrote:
> >> > On Fri, Dec 22, 2017 at 06:11:52PM +0800, Chen-Yu Tsai wrote:
> >> >> On Fri, Dec 22, 2017 at 6:07 PM, Emmanuel Vadot <manu@bidouilliste.com> wrote:
> >> >> > On Fri, 22 Dec 2017 09:35:08 +0100
> >> >> > Maxime Ripard <maxime.ripard@free-electrons.com> wrote:
> >> >> >
> >> >> >> On Thu, Dec 21, 2017 at 07:09:03PM +0100, Emmanuel Vadot wrote:
> >> >> >> >
> >> >> >> > Hi Maxime,
> >> >> >> >
> >> >> >> > On Thu, 21 Dec 2017 16:26:30 +0100
> >> >> >> > Maxime Ripard <maxime.ripard@free-electrons.com> wrote:
> >> >> >> >
> >> >> >> > > Hi,
> >> >> >> > >
> >> >> >> > > On Thu, Dec 21, 2017 at 09:19:24AM -0600, Kyle Evans wrote:
> >> >> >> > > > On Thu, Dec 21, 2017 at 8:55 AM, Maxime Ripard
> >> >> >> > > > <maxime.ripard@free-electrons.com> wrote:
> >> >> >> > > > > 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 have a patch that I think should make it work fine on Linux [1], but
> >> >> >> > > > I'm afraid I have little to no capability to test it myself and so I
> >> >> >> > > > did not add it as well.
> >> >> >> > > >
> >> >> >> > > > I do know that the rootkey is offset 0x200 into the given space [2],
> >> >> >> > > > as is the case with the H3, and that the readout quirk is not needed.
> >> >> >> > > > I wasn't 100% sure that the a83t has 2Kbit worth of efuse space as the
> >> >> >> > > > H3, but I do know that thermal data can be found at 0x34 and 0x38 in
> >> >> >> > > > this space.
> >> >> >> > >
> >> >> >> > > Then maybe we should leave it aside until someone takes some time on
> >> >> >> > > the A83t.
> >> >> >> >
> >> >> >> > Take some time on the Linux driver and do not apply this patch for
> >> >> >> > now you mean ?
> >> >> >>
> >> >> >> Yep.
> >> >> >>
> >> >> >> Maxime
> >> >> >
> >> >> > Since linux doesn't have the compatible in it's driver what would
> >> >> > be the harm to add the node in the DTS ? If a quirks is needed because
> >> >> > some region is weird this would go in the driver right ? I don't see a
> >> >> > technical problem for adding this node right now.
> >> >> > If Kyle confirm the lenght of the region and that no quirk is needed
> >> >> > will it be enough ?
> >> >>
> >> >> I guess I wasn't very clear. I'm OK with the patch going in. The device
> >> >> node currently says nothing about how much efuse space there is. The
> >> >> memory region covers that and the control section, and the size matches
> >> >> what the memory map says.
> >> >>
> >> >> The size and offset of the efuse space would be dealt with in the driver.
> >> >
> >> > Let's merge it then.
> >> >
> >> > Acked-by: Maxime Ripard <maxime.ripard@free-electrons.com>
> >>
> >> What does the timeline for these things normally look like? I'm new to
> >> these parts. =)
> >
> > We're one week away from the merge window, so it's a bit late for it
> > to be merged in 4.16, but it'll be in 4.17.
> It's been two months and this still hasn't quite landed in
> sunxi/for-next. =( May I ask the status on this?
It seems to have fallen through the cracks, sorry :/
Can you resend it based on 4.17?
Thanks!
Maxime
--
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180419/b1663c4f/attachment-0001.sig>
prev parent reply other threads:[~2018-04-19 13:38 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
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 [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=20180419133833.etuuxm3eygp3wfye@flea \
--to=maxime.ripard@bootlin.com \
--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