From: Tony Lindgren <tony@atomide.com>
To: Drew Fustini <drew@beagleboard.org>
Cc: "Grygorii Strashko" <grygorii.strashko@ti.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
"Benoît Cousson" <bcousson@baylibre.com>,
"Rob Herring" <robh+dt@kernel.org>,
devicetree@vger.kernel.org,
"Santosh Shilimkar" <ssantosh@kernel.org>,
"Suman Anna" <s-anna@ti.com>,
"Haojian Zhuang" <haojian.zhuang@linaro.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, jkridner@beagleboard.org,
robertcnelson@gmail.com
Subject: Re: [PATCH] ARM: dts: AM33xx-l4: add gpio-ranges
Date: Wed, 17 Jun 2020 09:55:41 -0700 [thread overview]
Message-ID: <20200617165541.GH37466@atomide.com> (raw)
In-Reply-To: <20200617162740.GA4181112@x1>
* Drew Fustini <drew@beagleboard.org> [200617 16:28]:
> These gpio-ranges are correct for all the platforms that included
> am33xx-l4.dtsi.
>
> I think it makes sense to add gpio-ranges properties as they describe
> the relationship between a gpio line and pin control register that
> exists in the hardware.
>
> Are there changes you would like to see in this patch?
Looks good to me, will apply when I'm done with the fixes
now that we have -rc1 out.
Regards,
Tony
next prev parent reply other threads:[~2020-06-17 16:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 13:14 [PATCH] ARM: dts: AM33xx-l4: add gpio-ranges Drew Fustini
2020-06-02 13:44 ` Grygorii Strashko
2020-06-02 13:51 ` Tony Lindgren
2020-06-02 16:34 ` Drew Fustini
2020-06-17 16:27 ` Drew Fustini
2020-06-17 16:55 ` Tony Lindgren [this message]
2020-06-02 18:24 ` Drew Fustini
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=20200617165541.GH37466@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=drew@beagleboard.org \
--cc=grygorii.strashko@ti.com \
--cc=haojian.zhuang@linaro.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=s-anna@ti.com \
--cc=ssantosh@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.