Received: by 10.192.165.156 with SMTP id m28csp1282878imm; Wed, 18 Apr 2018 07:16:54 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+RGZ3OEy/X+epz9sSHnjUNY/Y8NeKje+QidKWB3ikyQA/XY9uMafyjboTqy4Eh9+xA08Au X-Received: by 10.99.167.6 with SMTP id d6mr1834963pgf.287.1524061013952; Wed, 18 Apr 2018 07:16:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524061013; cv=none; d=google.com; s=arc-20160816; b=KF6krcwO91GfUPD1sWLCtHTbpTjDG1Jyx27ot7aT1iJf1qMJgI6ouMJsFW79Tj0O5F rWl84yx+e7+JYPme4P0f195cK4jPTDsKnch/POUJdHRJZnOr7HCmWn9AH89+mOYBcYxF 6au9us/3pCOHcy9KamQb/6CbrVrVk0DKAaq+/xn6a3pUz+ArMiHrAc3MS3RBs7AIsnRA lMVc06ObT6zrAts+466JSSe3tiwcU1sqBS89ND2vRro0A/blktOySU8TZzShj0oH/07T u4SxTcfKAPJjctIcR2dWcS7lYuOHJGFkHadkH6QineJ+YfrdhPMAF6UkaKHJ3sGF0EhW PrnA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:arc-authentication-results; bh=cLWSYNYJDcHSHglCglbEnYWSi8C4h7FOLHPJzFHjsYw=; b=OzVRuGs6UO8AweS7rs2v7Az8j0mnhjxXS1V+8jHwnM+Y0+pr2tVILFZ1n+WRBlfGkK 8GzDNudljnFGye5XGP5rDB6BJRLhVOhqkwlcAianJKcrLqt/z6w1GzbqogPqjnWbQzY0 FEVNK4748F72ZffDsnjvSzGPu1tZhPuTI1tRiz3kiFSVnWO8fLUCjR1dFZ+dGDtC11/j F6Q40W1Q14ztlFuWbnSnnvTYqfUCoXNI14crtnBPqzr8fgVC6kVWEMMeaCsvedKAwrEy psMF6OHca0CwxRM/qkM94JnjdSb694Im1QIglNtwNtrzwPZ7gKn/A7lt7HVVN4Imy4P5 RXvg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j1si1203471pff.7.2018.04.18.07.16.39; Wed, 18 Apr 2018 07:16:53 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753169AbeDROPW (ORCPT + 99 others); Wed, 18 Apr 2018 10:15:22 -0400 Received: from mx2.freebsd.org ([8.8.178.116]:49097 "EHLO mx2.freebsd.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751580AbeDROPU (ORCPT ); Wed, 18 Apr 2018 10:15:20 -0400 X-Greylist: delayed 576 seconds by postgrey-1.27 at vger.kernel.org; Wed, 18 Apr 2018 10:15:20 EDT Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx2.freebsd.org (Postfix) with ESMTPS id C0F588C176; Wed, 18 Apr 2018 14:05:43 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (unknown [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AA1BD768B5; Wed, 18 Apr 2018 14:05:41 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lf0-f42.google.com (mail-lf0-f42.google.com [209.85.215.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 6120817384; Wed, 18 Apr 2018 14:05:41 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lf0-f42.google.com with SMTP id j68-v6so2819160lfg.13; Wed, 18 Apr 2018 07:05:41 -0700 (PDT) X-Gm-Message-State: ALQs6tCG32yz7bn8cFSP/rtEnpL2YrqdlJFSa9U5Uyye4EAG6liVqYsl VTkiJkkUOOaigOOkfBAjmhF7D8LWlhkJWwABFwc= X-Received: by 2002:a19:984d:: with SMTP id a74-v6mr1753913lfe.47.1524060339927; Wed, 18 Apr 2018 07:05:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.129.90 with HTTP; Wed, 18 Apr 2018 07:05:19 -0700 (PDT) In-Reply-To: <20180109133412.uyai4s6vfnh37hn2@flea> References: <20171219210523.10428-1-kevans91@ksu.edu> <20171221145512.llxvzkcrjpquhczi@flea.lan> <20171221152630.2vf57x5o2yi5sv3n@flea.lan> <20171221190903.56ebae536acf51401c63802c@bidouilliste.com> <20171222083508.dfcp6egfvxykmogg@flea.lan> <20171222110727.520df7394234f6a5dc0b9ec0@bidouilliste.com> <20180104140119.5pyfihp4zs2poz35@flea.lan> <20180109133412.uyai4s6vfnh37hn2@flea> From: Kyle Evans Date: Wed, 18 Apr 2018 09:05:19 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2] ARM: dts: sunxi: Add sid for a83t To: Maxime Ripard Cc: Chen-Yu Tsai , Emmanuel Vadot , Mark Rutland , devicetree , linux-kernel , Russell King , linux-sunxi , Rob Herring , Srinivas Kandagatla , linux-arm-kernel Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 9, 2018 at 7:34 AM, Maxime Ripard 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 >> 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 wrote: >> >> > On Fri, 22 Dec 2017 09:35:08 +0100 >> >> > Maxime Ripard 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 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 >> >> >> > > > wrote: >> >> >> > > > > Hi Kyle, >> >> >> > > > > >> >> >> > > > > On Tue, Dec 19, 2017 at 03:05:23PM -0600, kevans91@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 >> >> >> > > > > >> >> >> > > > > 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 >> >> 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. > > Maxime > Hi, It's been two months and this still hasn't quite landed in sunxi/for-next. =( May I ask the status on this? Thanks, Kyle Evans