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;
MIME-Version: 1.0
References: <20210517200002.6316-1-dariobin@libero.it> <20210517200002.6316-2-dariobin@libero.it>
In-Reply-To: <20210517200002.6316-2-dariobin@libero.it>
From:   Andy Shevchenko <andy.shevchenko@gmail.com>
Date:   Wed, 19 May 2021 14:29:37 +0300
Message-ID: <CAHp75Ve12r5buxv6T=aidQmYq++zwntpMTedRXMe5X4H8dmndg@mail.gmail.com>
Subject: Re: [PATCH v2 1/2] pinctrl: core: configure pinmux from pins debug file
To:     Dario Binacchi <dariobin@libero.it>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linus Walleij <linus.walleij@linaro.org>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Wed, May 19, 2021 at 3:58 AM Dario Binacchi <dariobin@libero.it> wrote:
>
> The MPUs of some architectures (e.g AM335x) must be in privileged
> operating mode to write on the pinmux registers. In such cases, where
> writes will not work from user space, now it can be done from the pins
> debug file if the platform driver exports the pin_dbg_set() helper among
> the registered operations.

NAK. Please get into discussion and encourage maintainers to participate.

(Esp. taking into account that v2 of this patch is the same as v1)

-- 
With Best Regards,
Andy Shevchenko