All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Jacopo Mondi <jacopo@jmondi.org>
Cc: Jacopo Mondi <jacopo+renesas@jmondi.org>,
	Chris Brandt <chris.brandt@renesas.com>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>
Subject: Re: [PATCH] pinctrl: rza1: Switch to using "output-enable"
Date: Tue, 25 Aug 2020 09:10:02 +0200	[thread overview]
Message-ID: <CAMuHMdVaaNx2MbUiNKmvy=SnaDFEqpDVUNE7f+ftw4kw7Z=5gw@mail.gmail.com> (raw)
In-Reply-To: <20200824083007.x3l6ujn3mi5xhrsy@uno.localdomain>

Hi Jacopo,

On Mon, Aug 24, 2020 at 10:26 AM Jacopo Mondi <jacopo@jmondi.org> wrote:
> On Fri, Aug 21, 2020 at 01:14:01PM +0200, Geert Uytterhoeven wrote:
> > For pins requiring software driven IO output operations, the RZ/A1 Pin
> > Controller uses either the "output-high" or "output-low" DT property to
> > enable the corresponding output buffer.  The actual line value doesn't
> > matter, as it is ignored.
> >
> > Commit 425562429d4f3b13 ("pinctrl: generic: Add output-enable property")
> > introduced a new DT property for this specific use case.
> >
> > Update the RZ/A1 Pin Controller DT bindings and driver to use this new
> > property instead.  Preserve backwards compatibility with old DTBs in the
> > driver, as this comes at a very small cost.
> >
> > Notes:
> >   - The DT binding examples already used the new property,
> >   - There are no upstream users of the old properties.
> >
>
> Did we introduce output-enable after the rza1 pinctrl and forgot to
> update ? Good catch anyway

"output-enable" was introduced in response to early review comments
on the rza1 pinctrl driver, and both changes went upstream through
the same sh-pfc pull request.  Seems like part of the update was just
forgotten.

> Great! For both parts:
> Acked-by: Jacopo Mondi <jacopo@jmondi.org>

Thanks!

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

  reply	other threads:[~2020-08-25  7:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-21 11:14 [PATCH] pinctrl: rza1: Switch to using "output-enable" Geert Uytterhoeven
2020-08-21 12:02 ` Chris Brandt
2020-08-24  8:30 ` Jacopo Mondi
2020-08-25  7:10   ` Geert Uytterhoeven [this message]
2020-09-08 20:53 ` Rob Herring

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='CAMuHMdVaaNx2MbUiNKmvy=SnaDFEqpDVUNE7f+ftw4kw7Z=5gw@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=chris.brandt@renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jacopo+renesas@jmondi.org \
    --cc=jacopo@jmondi.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-renesas-soc@vger.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.