From: Sergei Shtylyov <sergei.shtylyov@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 4/4] pinctrl: sh-pfc: r8a77965: Add VIN stf8 pins
Date: Tue, 15 Sep 2020 12:12:49 +0300 [thread overview]
Message-ID: <7e4d45b1-10d6-f275-c447-cdb0b278859d@gmail.com> (raw)
In-Reply-To: <CAMuHMdWksZj4_mNE5zsuO6-FGA8HmgCg+Lu=SWBMU=JWvDHK1Q@mail.gmail.com>
Hello!
On 15.09.2020 11:50, Geert Uytterhoeven wrote:
[...]
>> On 15.09.2020 2:37, Niklas Söderlund wrote:
>>> This patch adds VIN{4,5} sft8 pins to the R8A77965 SoC.
>>
>> Same question here. And what is SFT8 anyway? :-)
>
> https://lore.kernel.org/linux-renesas-soc/CAMuHMdXdDkPX447AibYNjUwGHkYxC3sE-18G2DNVQR2T-jxX2w@mail.gmail.com
So SFT is short for "shifted"? :-O
I'd also like to know the use case...
> Would you prefer "vin[45]_g8"?
Hm, probably...
> Or perhaps even "vin[45]_green8"?
>
> Gr{oetje,eeting}s,
>
> Geert
MBR, Sergei
prev parent reply other threads:[~2020-09-15 9:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 23:37 [PATCH 0/4] pinctrl: sh-pfc: Add VIN stf8 pins Niklas Söderlund
2020-09-14 23:37 ` [PATCH 1/4] pinctrl: sh-pfc: r8a77951: Add VIN pins, groups and functions Niklas Söderlund
2020-09-15 8:23 ` Sergei Shtylyov
2020-09-23 9:57 ` Geert Uytterhoeven
2020-09-14 23:37 ` [PATCH 2/4] pinctrl: sh-pfc: r8a7796: " Niklas Söderlund
2020-09-15 8:24 ` Sergei Shtylyov
2020-09-14 23:37 ` [PATCH 3/4] pinctrl: sh-pfc: r8a77990: Add VIN stf8 pins Niklas Söderlund
2020-09-15 8:17 ` Sergei Shtylyov
2020-09-14 23:37 ` [PATCH 4/4] pinctrl: sh-pfc: r8a77965: " Niklas Söderlund
2020-09-15 8:18 ` Sergei Shtylyov
2020-09-15 8:50 ` Geert Uytterhoeven
2020-09-15 9:12 ` Sergei Shtylyov [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=7e4d45b1-10d6-f275-c447-cdb0b278859d@gmail.com \
--to=sergei.shtylyov@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
/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).