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 91480C352A1 for ; Tue, 6 Dec 2022 17:02:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235237AbiLFRCc (ORCPT ); Tue, 6 Dec 2022 12:02:32 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40544 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233884AbiLFRCb (ORCPT ); Tue, 6 Dec 2022 12:02:31 -0500 Received: from mail-wr1-x431.google.com (mail-wr1-x431.google.com [IPv6:2a00:1450:4864:20::431]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C36432A73B for ; Tue, 6 Dec 2022 09:02:29 -0800 (PST) Received: by mail-wr1-x431.google.com with SMTP id h7so18383670wrs.6 for ; Tue, 06 Dec 2022 09:02:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=6TfdMZJx6YwYGMzVOHSPGcZQcm/YvSKhyLP6Zb9LW3U=; b=f8K+WmGUuSv8KswBqRGfezQk9LzOPL2MIF5hXavcrXyDmnppRVRbUmum7GmqK0ilHd e7i/rRxDuNaug60YHu+zo1baN8lGd+/QKrT2dRibC6K7zbh/KdMAm3HwrnxQjC50YDKi OsL4WLNJeo5ssdO0AsAeZiovFmmE1hI9YNlgEi/xwQ+Vh57UnCHDY9sKit0u6cMlebVH DFNJt+KjeAeFoNFGqv+ooLw1JWXUCaDuj7xJLIw4Nx3kEPjVOpFG62qXyWAjX+2+wvnL lnlor2txuaOFufx+UQkHYeBF9q2vguDA6pBj4/m3k0iC+nCdeT+MsrMJ3BeKOBVuVZfc b24w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=6TfdMZJx6YwYGMzVOHSPGcZQcm/YvSKhyLP6Zb9LW3U=; b=DBmSfbx9mO7jDOMGdFq4A+7oNxswO5nElC8RXnNujXoKcVfkH/KXzeM39raJbat6i9 n9/ohHaBuPt8P3KfUQ5MBmQs9i06bmF73hZmJdYa9Txs8MyLdCXX+pHYSmGgMymP4g12 TSsax186kExye81Jb9JpFwepwE/7pVOU75KOMLIt6zrSq7D9wp6zZTlFgGZ7c2lWYwux kA1sdviwsEhOztxDjlQxCSgsu1VhJpaO07ol9a4HEZrGv22BWfanDVLvw+JMTpt9O02s gcLwDTtjFJXuIKDGBgfkbDV3M6bPLnP1Fa1da2/x0n/CrMKx3A0m/piC66BNcl7PVLcj ao1w== X-Gm-Message-State: ANoB5pnd/D9TgwGtcQeGPQ3OtbmpP5NMkRABrah9RsUg40Bdg3Oywofc crTmPKX55FS5npsE5NMGbyxo2g== X-Google-Smtp-Source: AA0mqf42cYPf54pb3sxtziLBo7bdoS9uWV6Lhv4ERuK8x1zeExLMMZE086K/IaYZpTuoyHCqCnHi1w== X-Received: by 2002:a5d:4810:0:b0:242:4cf5:f391 with SMTP id l16-20020a5d4810000000b002424cf5f391mr9902226wrq.174.1670346148292; Tue, 06 Dec 2022 09:02:28 -0800 (PST) Received: from [192.168.10.46] (146725694.box.freepro.com. [130.180.211.218]) by smtp.googlemail.com with ESMTPSA id w12-20020a05600c474c00b003b435c41103sm32934264wmo.0.2022.12.06.09.02.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 06 Dec 2022 09:02:27 -0800 (PST) Message-ID: <617ffbbe-5043-d27f-6579-d5f5544f03d1@linaro.org> Date: Tue, 6 Dec 2022 18:02:26 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: [PATCH v3 00/11] enable VTM node for all TI's K3 SoCs Content-Language: en-US To: Bryan Brattlof , "Rafael J. Wysocki" , Amit Kucheria , Zhang Rui , Rob Herring , Krzysztof Kozlowski , Nishanth Menon , Vignesh Raghavendra , Tero Kristo Cc: Keerthy , Linux PM , Device Trees , LKML , LKML ARM References: <20221031232702.10339-1-bb@ti.com> From: Daniel Lezcano In-Reply-To: <20221031232702.10339-1-bb@ti.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 01/11/2022 00:26, Bryan Brattlof wrote: > Hello again everyone! > > This series enables the VTM nodes for all of Texas Instrument's K3 SoCs > > Most of this series updates the k3_j72xx_bandgap driver to conditionally > map an eFuse region used by the j721e to work around an issue in its VTM > implementation and allows us to save the SPARE_FUSE region on other SoCs > > We can then update the device tree bindings for the driver and finally > define the VTM nodes for each device > > Thanks for reviewing again > ~Bryan patch 1-6 applied, thanks -- Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog