From: andy.shevchenko@gmail.com
To: Nikita Shubin <nikita.shubin@maquefel.me>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v7 05/39] pinctrl: add a Cirrus ep93xx SoC pin controller
Date: Sun, 4 Feb 2024 18:56:54 +0200 [thread overview]
Message-ID: <Zb_B1mpHrfAhL6Zl@surfacebook.localdomain> (raw)
In-Reply-To: <20240118-ep93xx-v7-5-d953846ae771@maquefel.me>
Thu, Jan 18, 2024 at 11:20:48AM +0300, Nikita Shubin kirjoitti:
> Add a pin control (only multiplexing) driver for ep93xx SoC so
> we can fully convert ep93xx to device tree.
>
> This driver is capable of muxing ep9301/ep9302/ep9307/ep9312/ep9315
> variants, this is chosen based on "compatible" in device tree.
...
> +static const unsigned int ide_9312_pins[] = {
> + 78, 301, 302, 321, 322, 342,
> + 257, 295, 296, 334,
> + 4, 24, 25, 45, 46, 66, 314, 333,
> +};
In other cases you locate 8 per each line, why this one is unaligned with that
pattern?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-02-04 16:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 8:20 [PATCH v7 00/39] ep93xx device tree conversion Nikita Shubin via B4 Relay
2024-01-18 8:20 ` [PATCH v7 02/39] gpio: ep93xx: split device in multiple Nikita Shubin via B4 Relay
2024-01-18 8:20 ` [PATCH v7 05/39] pinctrl: add a Cirrus ep93xx SoC pin controller Nikita Shubin via B4 Relay
2024-02-04 16:56 ` andy.shevchenko [this message]
2024-01-18 8:21 ` [PATCH v7 26/39] gpio: ep93xx: add DT support for gpio-ep93xx Nikita Shubin via B4 Relay
2024-01-18 9:30 ` [PATCH v7 00/39] ep93xx device tree conversion Uwe Kleine-König
2024-01-18 9:36 ` Nikita Shubin
2024-02-04 17:03 ` andy.shevchenko
2024-02-13 9:48 ` Nikita Shubin
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=Zb_B1mpHrfAhL6Zl@surfacebook.localdomain \
--to=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikita.shubin@maquefel.me \
/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