Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp225872pxf; Thu, 11 Mar 2021 02:19:57 -0800 (PST) X-Google-Smtp-Source: ABdhPJzOsw/N6WeFOeWnDs4E4TDdFNdvrft5eC3sOGpfsiPGJoghDEg6Iy2dVyUqirwYbpnhyMHO X-Received: by 2002:a17:907:1692:: with SMTP id hc18mr2323083ejc.265.1615457997486; Thu, 11 Mar 2021 02:19:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1615457997; cv=none; d=google.com; s=arc-20160816; b=NhwDiHSZmi2n/2zbvzbfAwWTrjrFiVXWXjRlrlQIjJryHBw2kSK6mlJ7x3aQQx+a41 zFmWb2C1rI07TcKnX7JRvOL2geCzJBAVON4gQtMVr4JVh61rOdF7Ga+cYRcbkaTIIxXY ZteowDFlBJXlyBYQf3STbtrbyXIyCMkrIv7l4tzr4P5BREKTxp1tCNdwabqZzBFI4leD AtOCA5R670jXyb0sovy36+o3Zyd6w7hzxXRYjWty7u5jwj9iTYSRg9VJXrqdtpyMM1JS 9A0FvIkBqMtPiHul24bthWRFNkNzlWJ0ytFj/PgAbHAk+9HchYwb7kzj8ny5gdty6Bmc iXzg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=8hGdUEE+eEYUNHDhMQAxpXgOAIfEwgA5YC5ZKYTs8JM=; b=C1csuUE+obUAGiq2avn6wAwWh/FGMu3No2d4nec/hJqvdrIDH1Bs7ucj/YJKitu0LI dJmBGVqwjhUBLJ7jxWr2J/6TwJTUC08RcDr36zY+nDxNYroo5ywGOjqM4QYG6UJ/Tvqt MJKUFmwQJWibfnGc6Ao+vZUc6+/CMHYruXalscd2RYt/4SxRnWXz1bB0Y0bbnJZ2vvRm gfSQFNDkzJyi4DMbFmUQg+NmcDIKX5r3ju9UfduOxFNHfdTkPGudSPKXASabtSLS5UdB WdmVdbOM70J/ogz8HUlPrBq9IRuUSTEYpYCoLIaTIcz90U+az4vOWulRc/X8FNrnaLkU /JjA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id la25si1472965ejb.703.2021.03.11.02.19.34; Thu, 11 Mar 2021 02:19:57 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232227AbhCKKRb (ORCPT + 99 others); Thu, 11 Mar 2021 05:17:31 -0500 Received: from mout.kundenserver.de ([212.227.17.13]:37371 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232246AbhCKKRY (ORCPT ); Thu, 11 Mar 2021 05:17:24 -0500 Received: from [192.168.1.155] ([77.4.9.157]) by mrelayeu.kundenserver.de (mreue109 [212.227.15.183]) with ESMTPSA (Nemesis) id 1N2V8T-1ljcBP3SEp-013tag; Thu, 11 Mar 2021 11:17:16 +0100 Subject: Re: [RFC PATCH 07/12] gpio: amd-fch: add oftree probing support To: Linus Walleij , "Enrico Weigelt, metux IT consult" Cc: "linux-kernel@vger.kernel.org" , "Rafael J. Wysocki" , Bartosz Golaszewski , Rob Herring , Frank Rowand , Pantelis Antoniou , "open list:GPIO SUBSYSTEM" , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" References: <20210208222203.22335-1-info@metux.net> <20210208222203.22335-8-info@metux.net> From: "Enrico Weigelt, metux IT consult" Message-ID: Date: Thu, 11 Mar 2021 11:17:15 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: tl Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K1:Da5Wubz3qht31qNBK8msWmU8qQAtD6bVMmtMsHo+GTkYRtzJd6S 7Ol0A9BMSURMyP2Yu/miLKao45Xa13V5Kb3BWeOh7wqOEc9fB8UxguLXHW+rTwNElnvCzcu +qpaJRemDCDtrAaZOZQ5+Gu/dhQwzmDA7FyAhxa7HUfrSGX1sP4JjxG5OioUUIq6gZE/v1R 6pjZgNAue4tF/Ksqv6lMg== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:dWRgG5/anZU=:mP3bijunZIqP6TdOJBFCjd lHZxNgzlXuBEB0VIBDHth7kTL6LMYPRRTQ52DA93xCrbGNJNi4kLNwAdPZ6PcgZPAj0TS1d8x h+ht1TtF3bSY7yGmoTNlC0fSTlEtSH+Z6kxjkSsxPYp1x2nP9dMcDYJxGPGoZEPM8FC0u+G6f NFIkuE8riEmyELmYA5E+/dp5cUTyS3L/m0fVi8Ot/6IbEQA3xS+ynsf3TfcrpUS9J/B9T2lwO NJW87RP3heEWl/BJOoASlUdkcpObwHGg1QfSGsazWc5rDoIyEhr3utt5bqyVvhGwmBqeLjM9b vIXZUExk23HQDuZu58Po5Ht0rzNl8nOMMGp3jslfcTbrqQTl9yymho/pX0hGnjSkrRsPe0xOU dIUcCuFU0RD1oPHjrquHUIc+5etomd9WggZjqUamxsNng/EbwXCRoVWZzKMyq Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01.03.21 15:51, Linus Walleij wrote: Hi, > I don't know what the idea is with this but register are not normally defined > in the DTS files. The registers are determined from the compatible value. The idea is basically replacing the pdata struct by oftree node. (subsequent patches in this queue use this by doing the board setup via compiled-in dtb, instead of the currently hardcoded tables). On these SoCs, the gpio setup is a little bit more complex than just having a fixed range of registers (one per pin): the actual meaning depends und Soc model and board type - some regs aren't even gpios. (I'm still in progress of RE'ing the bios blob, to find out more, eg. pinmux setups, etc). Writing to the wrong regs can cause weird effects (actually not even sure whether it could lead to damage) In essence: only a specific subset of the register range can be used for GPIOs - the others shouldn't ever be touched. And this specific subset is soc/board specific. --mtx -- --- Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren GPG/PGP-Schlüssel zu. --- Enrico Weigelt, metux IT consult Free software and Linux embedded engineering info@metux.net -- +49-151-27565287