From: Linus Walleij <linus.walleij@linaro.org>
To: Dario Binacchi <dariobin@libero.it>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>,
Drew Fustini <drew@beagleboard.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Haojian Zhuang <haojian.zhuang@linaro.org>,
Jonathan Corbet <corbet@lwn.net>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux-OMAP <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v3 0/3] am335x: set pinmux registers from pins debug file
Date: Tue, 25 May 2021 02:18:25 +0200 [thread overview]
Message-ID: <CACRpkdanh32PREaYhN1dW1p0GDamSZ04WgRr-afm+6L-c1fJCg@mail.gmail.com> (raw)
In-Reply-To: <20210520202730.4444-1-dariobin@libero.it>
On Thu, May 20, 2021 at 10:27 PM Dario Binacchi <dariobin@libero.it> wrote:
> The patch was born from the need to change the slew rate of the LCD pins
> of a custom AM335x board during EMC tests. The AM335x, as described in a
> note in section 9.1 of its reference manual [1], is unable to write
> pinmux registers from user space. The series now makes it possible to
> write these registers from the pins debug file.
I am going to hold this series back pending more discussion on the ABI
and whether it is useful.
Yours,
Linus Walleij
prev parent reply other threads:[~2021-05-25 0:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 20:27 [PATCH v3 0/3] am335x: set pinmux registers from pins debug file Dario Binacchi
2021-05-20 20:27 ` [PATCH v3 3/3] pinctrl: single: set pinmux " Dario Binacchi
2021-05-21 6:44 ` Vladimir Zapolskiy
2021-05-25 0:18 ` Linus Walleij [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACRpkdanh32PREaYhN1dW1p0GDamSZ04WgRr-afm+6L-c1fJCg@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=andy.shevchenko@gmail.com \
--cc=corbet@lwn.net \
--cc=dariobin@libero.it \
--cc=drew@beagleboard.org \
--cc=haojian.zhuang@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).