From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: [PATCH v2 0/4] Rework secure-monitor driver Date: Tue, 24 Sep 2019 11:45:23 -0700 Message-ID: <7hd0fp7cu4.fsf@baylibre.com> References: <20190731082339.20163-1-ccaione@baylibre.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20190731082339.20163-1-ccaione@baylibre.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: srinivas.kandagatla@linaro.org, narmstrong@baylibre.com, robh+dt@kernel.org, tglx@linutronix.de, jbrunet@baylibre.com, linux-arm-kernel@lists.infradead.org, linux-amlogic@lists.infradead.org, devicetree@vger.kernel.org Cc: Carlo Caione List-Id: devicetree@vger.kernel.org Carlo Caione writes: > The secure-monitor driver is currently in really bad shape, not my > proudest piece of code (thanks Jerome for pointing that out ;). I tried > to rework it a bit to make it a bit more tolerable. > > I needed to change a bit the APIs and consequently adapt the only user > we have, that is the nvmem/efuses driver. To not break bisectability I > added one single commit to change both the drivers. > > The remaining commits are cosmetic and DTS/docs fixes. > > Changelog: > - Changed patches order to not break bisect > - Removed non-functional changes (PATCH 1/5) of the nvmem driver > - Fix gxbb/gxl DTS > > Carlo Caione (4): > firmware: meson_sm: Mark chip struct as static const > nvmem: meson-efuse: bindings: Add secure-monitor phandle > arm64: dts: meson: Link nvmem and secure-monitor nodes > firmware: meson_sm: Rework driver as a proper platform driver Queued for v5.5, Thanks, Kevin