From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Lars Povlsen <lars.povlsen@microchip.com>,
Linus Walleij <linus.walleij@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>
Subject: Re: [PATCH] pinctrl: ocelot: Add platform dependency
Date: Mon, 11 May 2020 16:53:29 +0200 [thread overview]
Message-ID: <20200511145329.GV34497@piout.net> (raw)
In-Reply-To: <CAMuHMdXZMeY_Oz5fruxhfmS=6Tro0C3P+RoGiRZHpmACFrYXLg@mail.gmail.com>
On 11/05/2020 16:48:01+0200, Geert Uytterhoeven wrote:
> I can connect whatever other system using SPI, i2c, CAN, or Ethernet ;-)
> That doesn't mean I will directly program the other system's pin controller
> over that link, using the standard (MMIO) pinctrl driver.
>
Yes, my point is that you can access all the SoC registers over SPI and
so you will probably need to also control the pinctrl for example to be
able to actually use the on-SoC switch.
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-05-11 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 11:40 [PATCH] pinctrl: ocelot: Add platform dependency Geert Uytterhoeven
2020-05-07 11:45 ` Alexandre Belloni
2020-05-07 11:52 ` Geert Uytterhoeven
2020-05-07 12:27 ` Lars Povlsen
2020-05-07 12:44 ` Alexandre Belloni
2020-05-11 11:39 ` Geert Uytterhoeven
2020-05-11 14:20 ` Alexandre Belloni
2020-05-11 14:48 ` Geert Uytterhoeven
2020-05-11 14:53 ` Alexandre Belloni [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=20200511145329.GV34497@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=lars.povlsen@microchip.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
/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).