From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5C70DC3527C for ; Mon, 9 May 2022 08:57:17 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237388AbiEII63 (ORCPT ); Mon, 9 May 2022 04:58:29 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47766 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236994AbiEIIdG (ORCPT ); Mon, 9 May 2022 04:33:06 -0400 Received: from ssl.serverraum.org (ssl.serverraum.org [176.9.125.105]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A9D051ED2AF; Mon, 9 May 2022 01:28:56 -0700 (PDT) Received: from ssl.serverraum.org (web.serverraum.org [172.16.0.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ssl.serverraum.org (Postfix) with ESMTPSA id 3D5E522239; Mon, 9 May 2022 10:28:10 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walle.cc; s=mail2016061301; t=1652084892; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=hrOfN70yR3Xmn60iX12X/vbExJnwtfnTCJkusHb3SdA=; b=DQWCSooUC5U5bBhhytCawhmFXz8gb3vpIlFwcze4HcHjgEm8ezacosCjVWtl/EpOKNuuPa ynDzk2fwl2H8DjkuOvxRcBAgDLWZnHxNxHAXlKrcGTFwzc3yyGHRYC2+rMBdHnrbL5Q+OK 9ZMW0JopppSeIOnASmu/MRTq0SPCljk= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 09 May 2022 10:28:09 +0200 From: Michael Walle To: Srinivas Kandagatla Cc: Sean Anderson , linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, Li Yang , linux-kernel@vger.kernel.org, Rob Herring , Shawn Guo , Krzysztof Kozlowski , Andrew Lunn Subject: Re: [PATCH v3 0/9] nvmem: sfp: binding updates and additions In-Reply-To: <3b8fc56f64508f7604f3b9e14b048568@walle.cc> References: <20220428181703.2194171-1-sean.anderson@seco.com> <7aa5d553-04ad-5198-153c-39a9375a6a12@linaro.org> <3b8fc56f64508f7604f3b9e14b048568@walle.cc> User-Agent: Roundcube Webmail/1.4.13 Message-ID: <8602f6adb0fcf591e2923c736b345abd@walle.cc> X-Sender: michael@walle.cc Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 2022-05-03 15:43, schrieb Michael Walle: > Am 2022-04-29 17:56, schrieb Srinivas Kandagatla: >> On 28/04/2022 19:16, Sean Anderson wrote: >>> This adds several properties to the Layerscape Security Fuse >>> Processor >>> (SFP) necessary for writing. Although the Linux driver does not use >>> these bindings, I plan to use them in U-Boot [1]. It also adds a new >>> compatibles for Trust Architecture (TA) 2.1 devices. In addition, it >>> also adds an SFP binding for all TA 2.1 and 3.0 devices. >>> >>> I would like to get this series merged for 5.18. As noted in patch 2, >>> making the clock property mandatory is not an ABI break, but if this >>> is >>> not applied then it would become an ABI break. The absolute minimum >>> patches to apply for this would be patches 2 and 5. The rest >>> (including >>> the regmap changes) could be deferred if necessary. >>> >>> [1] >>> https://lore.kernel.org/u-boot/7c8e206a-cd40-2a77-6282-7f4bead2b13a@seco.com/T/#m591f8425b6f096ab3d54e6f7bd258e41cfa4c43b >>> >>> Changes in v3: >>> - Update commit message to note that this binding has not yet been >>> present in a relase, so it is OK to make otherwise breaking >>> changes. >>> >>> Changes in v2: >>> - Mention "regulator" in the description for ta-prog-sfp-supply >>> - Convert sfp driver to use regmap >>> - Fix various typos in commit messages >>> >>> Sean Anderson (9): >>> dt-bindings: nvmem: sfp: Fix typo >>> dt-bindings: nvmem: sfp: Add clock properties >>> dt-bindings: nvmem: sfp: Add TA_PROG_SFP supply >>> dt-bindings: nvmem: sfp: Add compatible binding for TA 2.1 SFPs >>> arm64: dts: ls1028a: Update SFP binding to include clock >>> ARM: dts: layerscape: Add SFP binding for TA 2.1 devices >>> ARM: dts: Add SFP binding for TA 3.0 devices >>> nvmem: sfp: Use regmap >>> nvmem: sfp: Add support for TA 2.1 devices >>> >> >> I have applied all the patches except 5/9, 6/9, and 7/9 dts patches >> which need to go via dts maintainer tree. > > Ahh. At least the device tree binding change (and the device tree > changes itself) should be applied as fixes for the 5.18 release, > so we don't have any conflicting descriptions. My fixes tag was never > picked up, unfortunately: > https://lore.kernel.org/linux-devicetree/4a45db184fbadc278624571dfbeb5004@walle.cc/ > > Srinivas, I've seen you picked it up into your for-next branch. > Can we fix that? > > I'd guess the layerscape device tree change also need a Fixes: tag. Ping. We are now -rc7 :/ -michael