From: jacopo mondi <jacopo@jmondi.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: "Simon Horman" <horms@verge.net.au>,
"Jacopo Mondi" <jacopo+renesas@jmondi.org>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Kieran Bingham" <kieran.bingham+renesas@ideasonboard.com>,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
"Magnus Damm" <damm+renesas@opensource.se>,
"Ulrich Hecht" <ulrich.hecht+renesas@gmail.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH v2 5/8] pinctrl: sh-pfc: r8a77990: Add VIN pins, groups and functions
Date: Tue, 11 Sep 2018 10:54:24 +0200 [thread overview]
Message-ID: <20180911085424.GR28160@w540> (raw)
In-Reply-To: <CAMuHMdXbdm4=TzAkoc2KmS+m69ppOM6GXCgHTCoDS1-1MZ=RgQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1902 bytes --]
Hi Geert,
On Tue, Sep 11, 2018 at 10:15:23AM +0200, Geert Uytterhoeven wrote:
> Hi Jacopo,
>
> On Tue, Sep 11, 2018 at 9:44 AM jacopo mondi <jacopo@jmondi.org> wrote:
> > On Mon, Sep 10, 2018 at 03:01:15PM +0200, Simon Horman wrote:
> > > On Wed, Sep 05, 2018 at 05:29:42PM +0200, Jacopo Mondi wrote:
> > > > This patch adds VIN{4,5} pins, groups and functions to the R8A77990 SoC.
>
> > Currently there are two open questions on this PFC patch:
>
> > 2) VIN5 synchronism signals (V/HSYNC, CLKENB, FIELD) are marked as
> > "_A" only, while VIN4 ones have not _A or _B extensions and are
> > shared between _A and _B group. The VIN5_#_A extension is an
> > indication that synchronism signals for group _B are not
> > multiplexed but active be default according to Morimoto-san, that
> > is about to confirm this with HW team. In that case, we need to
> > decide if to provide an 'vin5_sync_b' group anyway to let user
> > select it from DTS. Otherwise it won't be possible to select
> > synchronism pins for VIN5_B group (which is maybe fine if they're
> > not multiplexed at all).
>
> If the a "B" sync group exists, the pins are probably configurable as GPIOs,
> too, so we probably do need a group for them in the driver.
>
The chip manual does not report any _b group, and I don't have any E3
pin-related documentation like I have for M3-W/N
(r01uh0802ej0100-r-car-3rd-pin.pdf,
ASOM-C18-201_R-CarM3_pinfunction.xls etc etc)
How to find it out? Morimoto-san have you heard any news from HW team?
Thanks
j
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2018-09-11 13:52 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 15:29 [PATCH/RFT v2 0/8] arm64: dts: renesas: Ebisu: Add HDMI and CVBS input Jacopo Mondi
2018-09-05 15:29 ` [PATCH v2 1/8] media: dt-bindings: rcar-vin: Add R8A77990 support Jacopo Mondi
2018-09-10 12:42 ` Simon Horman
2018-09-10 13:58 ` Laurent Pinchart
2018-09-10 18:15 ` Niklas Söderlund
2018-09-05 15:29 ` [PATCH v2 2/8] media: rcar-vin: Add support for R-Car R8A77990 Jacopo Mondi
2018-09-10 14:02 ` Laurent Pinchart
2018-09-10 18:18 ` Niklas Söderlund
2018-09-05 15:29 ` [PATCH v2 3/8] media: dt-bindings: rcar-csi2: Add R8A77990 Jacopo Mondi
2018-09-10 12:45 ` Simon Horman
2018-09-10 14:04 ` Laurent Pinchart
2018-09-10 18:19 ` Niklas Söderlund
2018-09-05 15:29 ` [PATCH v2 4/8] media: rcar-csi2: Add R8A77990 support Jacopo Mondi
2018-09-10 14:05 ` Laurent Pinchart
2018-09-10 18:20 ` Niklas Söderlund
2018-09-05 15:29 ` [PATCH v2 5/8] pinctrl: sh-pfc: r8a77990: Add VIN pins, groups and functions Jacopo Mondi
2018-09-10 13:01 ` Simon Horman
2018-09-11 7:44 ` jacopo mondi
2018-09-11 8:15 ` Geert Uytterhoeven
2018-09-11 8:54 ` jacopo mondi [this message]
2018-09-11 9:44 ` jacopo mondi
2018-09-28 7:46 ` jacopo mondi
2018-10-02 9:25 ` Geert Uytterhoeven
2018-10-19 16:55 ` jacopo mondi
2018-10-20 19:04 ` Geert Uytterhoeven
2018-09-05 15:29 ` [PATCH v2 6/8] arm64: dts: r8a77990: Add VIN and CSI-2 device nodes Jacopo Mondi
2018-09-06 9:10 ` Simon Horman
2018-09-06 9:16 ` Simon Horman
2018-09-10 14:12 ` Laurent Pinchart
2018-09-17 14:37 ` Laurent Pinchart
2018-10-30 10:14 ` jacopo mondi
2018-10-30 12:57 ` Laurent Pinchart
2018-10-31 12:48 ` Simon Horman
2018-10-31 13:18 ` jacopo mondi
2018-10-31 14:37 ` Simon Horman
2018-11-05 10:32 ` jacopo mondi
2018-11-06 14:02 ` Simon Horman
2018-09-05 15:29 ` [PATCH v2 7/8] arm64: dts: r8a77990: Add I2C " Jacopo Mondi
2018-09-05 16:12 ` Laurent Pinchart
2018-09-06 9:12 ` Simon Horman
2018-09-05 15:29 ` [PATCH v2 8/8] arm64: dts: renesas: ebisu: Add HDMI and CVBS input Jacopo Mondi
2018-09-10 14:21 ` Laurent Pinchart
2018-09-12 9:29 ` Simon Horman
2018-09-12 11:08 ` jacopo mondi
2018-09-17 7:09 ` Simon Horman
2018-09-17 15:22 ` [PATCH/RFT v2 0/8] arm64: dts: renesas: Ebisu: " Laurent Pinchart
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=20180911085424.GR28160@w540 \
--to=jacopo@jmondi.org \
--cc=damm+renesas@opensource.se \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=jacopo+renesas@jmondi.org \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=ulrich.hecht+renesas@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox