All of lore.kernel.org
 help / color / mirror / Atom feed
From: jacopo mondi <jacopo@jmondi.org>
To: Chris Brandt <Chris.Brandt@renesas.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-renesas-soc@vger.kernel.org"
	<linux-renesas-soc@vger.kernel.org>,
	Simon Horman <horms+renesas@verge.net.au>,
	Jacopo Mondi <jacopo+renesas@jmondi.org>
Subject: Re: [PATCH 1/2] pinctrl: rza1: add support for RZ/A1L
Date: Tue, 3 Oct 2017 18:17:38 +0200	[thread overview]
Message-ID: <20171003161738.GK4037@w540> (raw)
In-Reply-To: <SG2PR06MB1165669027CDC7F76808EADB8A720@SG2PR06MB1165.apcprd06.prod.outlook.com>

Hi Chris,

On Tue, Oct 03, 2017 at 03:40:51PM +0000, Chris Brandt wrote:
> Hi Jacopo,
>
>
> Yes, that 'are' listed in the table. But for a good reason.
>
> The TIOC pins can be uses as an output (PWM for example) or as a input
> (input capture for example), so they are not really a fixed direction.
> That is why the user needs to specify how they plan to use them in the DT.
> And...that's also why it doesn't make sense to put them in the
> rza1l_swio_pins[] array (we have no idea how they want to use them).
>
> So, the hardware manual has the TIOC pins in the SWIO table to tell the
> user 'hey, you have to manually set these pins to either input or output
> yourself because we can't magically know what you want to use them for.
>
> But...
> The reason for the rza1l_swio_pins[] array is for weird pin
> configurations that are fixed (like LCD LVDS output pins need to be configured as
> inputs).
>
>
> > Thanks for double checking. Your source from Japan is more
> > authoritative than manuals and defintely more accurate than me ;)
>
> So, after all that, I don't think we found any issues with my patch.
> Correct???

Correct! :)
After your clarification above, for both patches:

Reviewed-by: Jacopo Mondi <jacopo+renesas@jmondi.org>

Thanks
   j

>
>
> Thanks!
>
> Chris
>

  reply	other threads:[~2017-10-03 16:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03  7:33 [PATCH 0/2] pinctrl: rza1: add support for RZ/A1L Chris Brandt
2017-10-03  7:33 ` Chris Brandt
2017-10-03  7:33 ` [PATCH 1/2] " Chris Brandt
2017-10-03  8:31   ` jacopo mondi
2017-10-03 13:36     ` Chris Brandt
2017-10-03 15:04       ` jacopo mondi
2017-10-03 15:40         ` Chris Brandt
2017-10-03 15:40           ` Chris Brandt
2017-10-03 16:17           ` jacopo mondi [this message]
     [not found] ` <20171003073334.18917-1-chris.brandt-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2017-10-03  7:33   ` [PATCH 2/2] dt-bindings: pinctrl: " Chris Brandt
2017-10-03  7:33     ` Chris Brandt
     [not found]     ` <20171003073334.18917-3-chris.brandt-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2017-10-04 13:58       ` Geert Uytterhoeven
2017-10-04 13:58         ` Geert Uytterhoeven
2017-10-04 14:16         ` Chris Brandt
2017-10-04 14:27           ` Geert Uytterhoeven
2017-10-04 14:43             ` Chris Brandt
2017-10-04 14:49               ` Geert Uytterhoeven
2017-10-04 14:57                 ` Chris Brandt

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=20171003161738.GK4037@w540 \
    --to=jacopo@jmondi.org \
    --cc=Chris.Brandt@renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=horms+renesas@verge.net.au \
    --cc=jacopo+renesas@jmondi.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@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 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.