From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Dario Binacchi <dariobin@libero.it>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Haojian Zhuang <haojian.zhuang@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Tony Lindgren <tony@atomide.com>,
linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] am335x: set pinmux registers from pins debug file
Date: Wed, 19 May 2021 14:31:37 +0300 [thread overview]
Message-ID: <CAHp75Vc0kmwuT21=bvpfUj+qAO1XmKEXUpxEEhx3TRZrQbR4Gw@mail.gmail.com> (raw)
In-Reply-To: <20210517200002.6316-1-dariobin@libero.it>
On Wed, May 19, 2021 at 3:58 AM 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.
Even for debugfs it would be nice to have a piece of documentation.
Because pin control is a quite sensitive area and if something goes
wrong, it may damage the hardware.
> [1] https://www.ti.com/lit/ug/spruh73q/spruh73q.pdf
--
With Best Regards,
Andy Shevchenko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-05-19 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 20:00 Dario Binacchi
2021-05-17 20:00 ` [PATCH v2 2/2] pinctrl: single: set pinmux " Dario Binacchi
2021-05-18 6:05 ` Tony Lindgren
2021-05-18 8:57 ` Dario Binacchi
2021-05-21 9:25 ` Tony Lindgren
2021-05-19 11:31 ` Andy Shevchenko [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='CAHp75Vc0kmwuT21=bvpfUj+qAO1XmKEXUpxEEhx3TRZrQbR4Gw@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=dariobin@libero.it \
--cc=haojian.zhuang@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
--subject='Re: [PATCH v2 0/2] am335x: set pinmux registers from pins debug file' \
/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
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).