From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
To: kishon@ti.com
Cc: linux-kernel@vger.kernel.org,
driverdev-devel@linuxdriverproject.org,
devicetree@vger.kernel.org, john@phrozen.org,
linux-mips@vger.kernel.org, robh+dt@kernel.org, neil@brown.name
Subject: [PATCH v2 0/2] MT7621 PCIe PHY
Date: Sat, 30 Mar 2019 06:50:36 +0100 [thread overview]
Message-ID: <20190330055038.18958-1-sergio.paracuellos@gmail.com> (raw)
This series adds support for the PCIe PHY found in the Mediatek
MT7621 SoC.
This is the first attempt to get feedback of what is missing in
this driver to be promoted from staging.
There is also a 'mt7621-pci' driver which is the controller part
which is still in staging and is a client of this phy.
Both drivers have been tested together in a gnubee1 board.
Changes in v2:
- Reorder patches to get bindings first in the series.
- Don't use child nodes in the device tree. Use #phy-cells=1 instead.
- Update driver code with new 'xlate' function for the new device tree.
- Minor changes in driver's macros changing some spaces to tabs.
Thanks in advance for your time.
Best regards,
Sergio Paracuellos
Sergio Paracuellos (2):
dt-bindings: phy: Add binding for Mediatek MT7621 PCIe PHY
phy: ralink: Add PHY driver for MT7621 PCIe PHY
.../bindings/phy/mediatek,mt7621-pci-phy.txt | 28 ++
drivers/phy/ralink/Kconfig | 7 +
drivers/phy/ralink/Makefile | 1 +
drivers/phy/ralink/phy-mt7621-pci.c | 401 ++++++++++++++++++
4 files changed, 437 insertions(+)
create mode 100644 Documentation/devicetree/bindings/phy/mediatek,mt7621-pci-phy.txt
create mode 100644 drivers/phy/ralink/phy-mt7621-pci.c
--
2.19.1
next reply other threads:[~2019-03-30 5:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-30 5:50 Sergio Paracuellos [this message]
2019-03-30 5:50 ` [PATCH v2 1/2] dt-bindings: phy: Add binding for Mediatek " Sergio Paracuellos
2019-04-06 6:05 ` Rob Herring
2019-03-30 5:50 ` [PATCH v2 2/2] phy: ralink: Add PHY driver for " Sergio Paracuellos
2019-04-13 6:41 ` Sergio Paracuellos
2019-04-17 5:57 ` Kishon Vijay Abraham I
2019-04-17 7:33 ` Sergio Paracuellos
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=20190330055038.18958-1-sergio.paracuellos@gmail.com \
--to=sergio.paracuellos@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=john@phrozen.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=neil@brown.name \
--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
all inboxes | Powered by JetHome®