All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Drew Fustini <drew@beagleboard.org>,
	Rob Herring <robh+dt@kernel.org>,
	Jason Kridner <jkridner@beagleboard.org>,
	Robert Nelson <robertcnelson@gmail.com>,
	Trent Piepho <tpiepho@gmail.com>,
	Christina Quast <cquast@hanoverdisplays.com>,
	Linux-OMAP <linux-omap@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: am33xx: modify AM33XX_IOPAD for #pinctrl-cells = 2
Date: Thu, 1 Oct 2020 11:12:38 +0300	[thread overview]
Message-ID: <20201001081238.GV9471@atomide.com> (raw)
In-Reply-To: <CACRpkdb3J8y8jy9RVgY5J1ypEs15dDU7pcaEGdk5okrydTvmKg@mail.gmail.com>

* Linus Walleij <linus.walleij@linaro.org> [201001 08:08]:
> On Tue, Sep 22, 2020 at 12:57 AM Drew Fustini <drew@beagleboard.org> wrote:
> 
> > Modify the AM33XX_IOPAD macro so that it works now that #pinctrl-cells =
> > <2>. The third parameter is just a zero and the pinctrl-single driver
> > will just OR this with the second parameter so it has no actual effect.
> >
> > There are no longer any dts files using this macro (following my patch
> > to am335x-guardian.dts), but this will keep dts files not in mainline
> > from breaking.
> >
> > Fixes: 27c90e5e48d0 ("ARM: dts: am33xx-l4: change #pinctrl-cells from 1 to 2")
> > Suggested-by: Tony Lindgren <tony@atomide.com>
> > Reported-by: Trent Piepho <tpiepho@gmail.com>
> > Link: https://lore.kernel.org/linux-devicetree/20200921064707.GN7101@atomide.com/
> > Signed-off-by: Drew Fustini <drew@beagleboard.org>
> 
> I didn't get a review tag on this one, Tony is this something I
> should be applying?

Thanks for checking, looks like I already applied into my fixes branch:

b753e41d9999 ("ARM: dts: am33xx: modify AM33XX_IOPAD for #pinctrl-cells = 2")

Regards,

Tony

      reply	other threads:[~2020-10-01  8:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-21 22:50 [PATCH] ARM: dts: am33xx: modify AM33XX_IOPAD for #pinctrl-cells = 2 Drew Fustini
2020-10-01  8:08 ` Linus Walleij
2020-10-01  8:12   ` Tony Lindgren [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=20201001081238.GV9471@atomide.com \
    --to=tony@atomide.com \
    --cc=cquast@hanoverdisplays.com \
    --cc=devicetree@vger.kernel.org \
    --cc=drew@beagleboard.org \
    --cc=jkridner@beagleboard.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=robertcnelson@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=tpiepho@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 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.