From: Sricharan R <sricharan@codeaurora.org>
To: Stephen Boyd <sboyd@kernel.org>,
agross@kernel.org, devicetree@vger.kernel.org,
linus.walleij@linaro.org, linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-soc@vger.kernel.org, robh+dt@kernel.org,
sivaprak@codeaurora.org
Subject: Re: [PATCH V2 0/7] Add minimal boot support for IPQ6018
Date: Mon, 30 Dec 2019 14:37:11 +0530 [thread overview]
Message-ID: <ac5700ed-5b0e-5e75-a44a-cab7c543875b@codeaurora.org> (raw)
In-Reply-To: <20191227013353.4CB292080D@mail.kernel.org>
Hi Stephen,
On 12/27/2019 7:03 AM, Stephen Boyd wrote:
> Quoting Sricharan R (2019-12-19 02:41:42)
>> The IPQ6018 is Qualcomm\u2019s 802.11ax SoC for Routers,
>> Gateways and Access Points.
>>
>> This series adds minimal board boot support for ipq6018-cp01 board.
>>
>> [v2]
>> * Splitted dt bindings and driver into different patches. Added missing bindings
>> and some style changes.
>> * Added ipq6018 schema
>> * Addressed review comments for gcc clock bindings.
>> * Removed all clk critical flags, removed 1/1 factor clocks, moved to new
>> way of specifying clk parents, and addressed other review comments.
>> * Sorted nodes based on address, name, label. Removed unused clock nodes,
>> Addressed other review comments.
>
> Can you just send the clk and clk binding to me in a different series?
> I don't want to review all the other patches in the same thread.
>
Sure, will send separately.
Regards,
Sricharan
--
"QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
prev parent reply other threads:[~2019-12-30 9:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 10:41 [PATCH V2 0/7] Add minimal boot support for IPQ6018 Sricharan R
2019-12-19 10:41 ` [PATCH V2 1/7] dt-bindings: pinctrl: qcom: Add ipq6018 pinctrl bindings Sricharan R
2019-12-29 3:41 ` Bjorn Andersson
2019-12-30 9:12 ` Sricharan R
2019-12-19 10:41 ` [PATCH V2 2/7] pinctrl: qcom: Add ipq6018 pinctrl driver Sricharan R
2019-12-29 3:35 ` Bjorn Andersson
2019-12-30 9:10 ` Sricharan R
2019-12-19 10:41 ` [PATCH V2 3/7] dt-bindings: qcom: Add ipq6018 bindings Sricharan R
2019-12-19 10:41 ` [PATCH V2 4/7] clk: qcom: Add DT bindings for ipq6018 gcc clock controller Sricharan R
2019-12-19 18:24 ` Rob Herring
2019-12-19 10:41 ` [PATCH V2 5/7] clk: qcom: Add ipq6018 Global Clock Controller support Sricharan R
2019-12-27 1:33 ` Stephen Boyd
2019-12-30 9:06 ` Sricharan R
2019-12-19 10:41 ` [PATCH V2 6/7] arm64: dts: Add ipq6018 SoC and CP01 board support Sricharan R
2019-12-29 3:29 ` Bjorn Andersson
2019-12-30 9:10 ` Sricharan R
2019-12-19 10:41 ` [PATCH V2 7/7] arm64: defconfig: Enable qcom ipq6018 clock and pinctrl Sricharan R
2019-12-27 1:33 ` [PATCH V2 0/7] Add minimal boot support for IPQ6018 Stephen Boyd
2019-12-30 9:07 ` Sricharan R [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=ac5700ed-5b0e-5e75-a44a-cab7c543875b@codeaurora.org \
--to=sricharan@codeaurora.org \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sivaprak@codeaurora.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).