From: Marek Vasut <marek.vasut@gmail.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-gpio@vger.kernel.org,
Takeshi Kihara <takeshi.kihara.df@renesas.com>,
Marek Vasut <marek.vasut+renesas@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Simon Horman <horms+renesas@verge.net.au>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 1/2] pinctrl: sh-pfc: r8a77990: Add SDHI pins, groups and functions
Date: Tue, 6 Nov 2018 12:35:25 +0100 [thread overview]
Message-ID: <76819f63-39fa-3371-9551-fd76faf8baf2@gmail.com> (raw)
In-Reply-To: <20181106111448.5rc3yzfdzuv7w562@ninjato>
On 11/06/2018 12:14 PM, Wolfram Sang wrote:
>
>> static const struct {
>> - struct sh_pfc_pin_group common[123];
>> + struct sh_pfc_pin_group common[140];
>> struct sh_pfc_pin_group automotive[0];
>> } pinmux_groups = {
>
> ...
>
>> static const struct {
>> - struct sh_pfc_function common[29];
>> + struct sh_pfc_function common[32];
>> struct sh_pfc_function automotive[0];
>> } pinmux_functions = {
>
>
> It is Geert's call, but maybe those are a seperate patch?
These must be part of this patch, since adding
+ SH_PFC_PIN_GROUP(sdhi0_data1),
entries grows the size of the array. If you were to split this patch,
the PFC driver would break, as the size of the array won't match the
size of the content.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2018-11-06 21:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 21:40 [PATCH 1/2] pinctrl: sh-pfc: r8a77990: Add SDHI pins, groups and functions Marek Vasut
2018-11-05 21:40 ` [PATCH 2/2] pinctrl: sh-pfc: r8a77990: Add voltage switch operations for SDHI Marek Vasut
2018-11-06 5:24 ` Yoshihiro Shimoda
2018-11-06 11:15 ` Wolfram Sang
2018-11-06 11:33 ` Marek Vasut
2018-11-08 13:04 ` Geert Uytterhoeven
2018-11-06 5:23 ` [PATCH 1/2] pinctrl: sh-pfc: r8a77990: Add SDHI pins, groups and functions Yoshihiro Shimoda
2018-11-06 11:14 ` Wolfram Sang
2018-11-06 11:35 ` Marek Vasut [this message]
2018-11-08 12:58 ` Geert Uytterhoeven
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=76819f63-39fa-3371-9551-fd76faf8baf2@gmail.com \
--to=marek.vasut@gmail.com \
--cc=geert+renesas@glider.be \
--cc=horms+renesas@verge.net.au \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=takeshi.kihara.df@renesas.com \
--cc=wsa@the-dreams.de \
--cc=yoshihiro.shimoda.uh@renesas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.