From: Linus Walleij <linus.walleij@linaro.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-msm@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>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/4] pinctrl: qcom: Support dispersed tiles
Date: Wed, 26 Sep 2018 09:31:12 +0200 [thread overview]
Message-ID: <CACRpkdamu83JidqT89iLOfqsuW_UxAUVxU=Faq_QownNb-R10Q@mail.gmail.com> (raw)
In-Reply-To: <20180924221748.21584-3-bjorn.andersson@linaro.org>
On Tue, Sep 25, 2018 at 12:15 AM Bjorn Andersson
<bjorn.andersson@linaro.org> wrote:
> On some new platforms the tiles have been placed too far apart to be
> covered in a single ioremap. Turn "regs" into an array of base addresses
> and make the pingroup carry the information about which tile the pin
> resides in.
>
> For existing platforms we map the first entry regs and the existing
> pingroups will all use tile 0, meaning that there's no functional
> change.
>
> Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Patch applied.
Yours,
Linus Walleij
next prev parent reply other threads:[~2018-09-26 7:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 22:17 [PATCH v2 0/4] Qualcomm QCS404 TLMM pinctrl driver Bjorn Andersson
2018-09-24 22:17 ` [PATCH v2 1/4] pinctrl: qcom: Introduce readl/writel accessors Bjorn Andersson
2018-09-26 7:30 ` Linus Walleij
2018-09-28 7:10 ` Linus Walleij
2018-09-28 7:11 ` Linus Walleij
2018-09-24 22:17 ` [PATCH v2 2/4] pinctrl: qcom: Support dispersed tiles Bjorn Andersson
2018-09-26 7:31 ` Linus Walleij [this message]
2018-09-24 22:17 ` [PATCH v2 3/4] dt-bindings: pinctrl: qcom: Add QCS404 pinctrl binding Bjorn Andersson
2018-09-26 7:32 ` Linus Walleij
2018-09-24 22:17 ` [PATCH v2 4/4] pinctrl: qcom: Add qcs404 pinctrl driver Bjorn Andersson
2018-09-26 7:33 ` Linus Walleij
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='CACRpkdamu83JidqT89iLOfqsuW_UxAUVxU=Faq_QownNb-R10Q@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).