From: Bhupesh Sharma <bhupesh.sharma@linaro.org>
To: linux-arm-msm@vger.kernel.org
Cc: bhupesh.sharma@linaro.org, bhupesh.linux@gmail.com,
agross@kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, robh+dt@kernel.org,
bjorn.andersson@linaro.org
Subject: [PATCH v4 0/2] Add ethernet dts nodes for Qualcomm SA8155p-ADP board
Date: Fri, 25 Mar 2022 22:05:35 +0530 [thread overview]
Message-ID: <20220325163537.1579969-1-bhupesh.sharma@linaro.org> (raw)
Changes since v3:
-----------------
- v3 can be seen here: https://lore.kernel.org/lkml/20220303084824.284946-4-bhupesh.sharma@linaro.org/T/
- Bjorn has accepted a couple of patches from v3 already, so drop them
from this v4 version.
- Dropped the EMAC GDSC quirk patch from this series, as Bjorn has
already submitted a fix via [1].
- Keep only 'linux-arm-msm specific dts' patches in this subset, so that
they can be easily reviewed and merged.
Changes since v2:
-----------------
- v2 can be seen here: https://lore.kernel.org/linux-arm-msm/20220302110508.69053-1-bhupesh.sharma@linaro.org/T
- Fixed review comments from Dmitry - created a new [PATCH 2/6]
to fix some identation issues with sm8150 gcc driver.
Changes since v1:
-----------------
- v1 can be seen here: https://lore.kernel.org/netdev/20220126221725.710167-1-bhupesh.sharma@linaro.org/t/
- Fixed review comments from Bjorn - broke the v1 series into two
separate series - one each for 'net' tree and 'arm clock/dts' tree
- so as to ease review of the same from the respective maintainers.
- This series is intended for the 'arm msm clock/dts' tree.
- Other changes:
- Dropped [PATCH 7/8] from v1.
- Added more background on the emac gdsc issue, requiring it to be in
ALWAYS_ON state in [PATCH 5/5].
- Collected Ack from Rob for [PATCH 1/5].
- Broke down v1's [PATCH 3/8] into 3 separate patches (one each for emac,
pci and ufs gdsc defines) - one of which is carried as [PATCH 2/5]
in this series, which is used to enable emac GDSC.
The SA8155p-ADP board supports on-board ethernet (Gibabit Interface),
with support for both RGMII and RMII buses.
This patchset adds the support for the same.
Note that this patchset is based on an earlier sent patchset
for adding PDC controller support on SM8150 (see [2]).
[1]. https://lore.kernel.org/lkml/YjxkNzJMGt0f2XYF@kroah.com/T/
[2]. https://lore.kernel.org/linux-arm-msm/20220226184028.111566-1-bhupesh.sharma@linaro.org/T/
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>
Vinod Koul (2):
arm64: dts: qcom: sm8150: add ethernet node
arm64: dts: qcom: sa8155p-adp: Enable ethernet node
arch/arm64/boot/dts/qcom/sa8155p-adp.dts | 146 +++++++++++++++++++++++
arch/arm64/boot/dts/qcom/sm8150.dtsi | 27 +++++
2 files changed, 173 insertions(+)
--
2.35.1
next reply other threads:[~2022-03-25 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 16:35 Bhupesh Sharma [this message]
2022-03-25 16:35 ` [PATCH v4 1/2] arm64: dts: qcom: sm8150: add ethernet node Bhupesh Sharma
2022-03-25 16:35 ` [PATCH v4 2/2] arm64: dts: qcom: sa8155p-adp: Enable " Bhupesh Sharma
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=20220325163537.1579969-1-bhupesh.sharma@linaro.org \
--to=bhupesh.sharma@linaro.org \
--cc=agross@kernel.org \
--cc=bhupesh.linux@gmail.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).