From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
To: vkoul@kernel.org
Cc: robh+dt@kernel.org, kishon@ti.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
devel@driverdev.osuosl.org, neil@brown.name
Subject: [PATCH v5 0/4] MT7621 PCIe PHY
Date: Thu, 19 Nov 2020 16:43:33 +0100 [thread overview]
Message-ID: <20201119154337.9195-1-sergio.paracuellos@gmail.com> (raw)
This series adds support for the PCIe PHY found in the Mediatek
MT7621 SoC.
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.
This series are rebased on the top of linux-next:
commit 4e78c578cb98 ("Add linux-next specific files for 20201030")
Changes in v5:
- PATCH 1/4: Recollect Rob's Reviewed-by of bindings.
- PATCH 4/4: Recollect Greg's Acked-by for removing stuff from
staging area.
- Make Vinod's review comments changes in [0]:
* Use FIELD_GET and FIELD_PREP apis and avoid multiple *_VAL and
*_SHIFT custom definitions.
* Remove phy-read and phy-write internal functions and directly
call regmap_read and regmap_write in 'mt7621_phy_rmw'.
* Change some traces from info to debug log level.
* Note that I have maintained 'mt7621_phy_rmw' instead of use
'regmap_update_bits'. This is because in order to get a reliable
boot registers must be written event the contained value in
that register is the same. I have preferred doing in this way
instead of using 'regmap_update_bits_base' passing 'false' for
async and 'true' for the force write. If this way of using
'regmap_update_bits_base' is preferred just let me know.
Changes in v4:
- Bindings moved from txt to yaml so previous Rob's Reviewed-by
is not in the new patch with the yaml file.
- 'phy-cells' property means now if phy is dual-ported.
- Avoid custom 'xlate' function and properly set registers
when the phy is dual ported.
- Add use of 'builtin_platform_driver'.
- Added a patch including myself as maintainer in the
MAINTAINERS file.
- Add a patch removing patch from staging to make easier
the complete inclusion and avoid possible problems might
appear in 'linux-next' if the series are included.
Changes in v3:
- Recollect Rob's Reviewed-by of bindings.
- Make Kishon Vijay suggested changes in v2:
(See https://lkml.org/lkml/2019/4/17/53)
- Kconfig:
* Add depends on COMPILE_TEST
* Select REGMAP_MMIO
- Make use of 'soc_device_attribute' and 'soc_device_match'
- Use regmap mmio API instead of directly 'readl' and 'writel'.
- Use 'platform_get_resource' instead of 'of_address_to_resource'.
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
[0]: http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2020-November/148864.html
Sergio Paracuellos (4):
dt-bindings: phy: Add binding for Mediatek MT7621 PCIe PHY
phy: ralink: Add PHY driver for MT7621 PCIe PHY
MAINTAINERS: add MT7621 PHY PCI maintainer
staging: mt7621-pci-phy: remove driver from staging
.../phy}/mediatek,mt7621-pci-phy.yaml | 0
MAINTAINERS | 6 +
drivers/phy/ralink/Kconfig | 8 ++
drivers/phy/ralink/Makefile | 1 +
.../ralink/phy-mt7621-pci.c} | 103 +++++++-----------
drivers/staging/Kconfig | 2 -
drivers/staging/Makefile | 1 -
drivers/staging/mt7621-pci-phy/Kconfig | 8 --
drivers/staging/mt7621-pci-phy/Makefile | 2 -
drivers/staging/mt7621-pci-phy/TODO | 4 -
10 files changed, 53 insertions(+), 82 deletions(-)
rename {drivers/staging/mt7621-pci-phy => Documentation/devicetree/bindings/phy}/mediatek,mt7621-pci-phy.yaml (100%)
rename drivers/{staging/mt7621-pci-phy/pci-mt7621-phy.c => phy/ralink/phy-mt7621-pci.c} (76%)
delete mode 100644 drivers/staging/mt7621-pci-phy/Kconfig
delete mode 100644 drivers/staging/mt7621-pci-phy/Makefile
delete mode 100644 drivers/staging/mt7621-pci-phy/TODO
--
2.25.1
next reply other threads:[~2020-11-19 15:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 15:43 Sergio Paracuellos [this message]
2020-11-19 15:43 ` [PATCH v5 1/4] dt-bindings: phy: Add binding for Mediatek MT7621 PCIe PHY Sergio Paracuellos
2020-11-19 15:43 ` [PATCH v5 2/4] phy: ralink: Add PHY driver for " Sergio Paracuellos
2020-11-19 15:43 ` [PATCH v5 3/4] MAINTAINERS: add MT7621 PHY PCI maintainer Sergio Paracuellos
2020-11-19 15:43 ` [PATCH v5 4/4] staging: mt7621-pci-phy: remove driver from staging Sergio Paracuellos
2020-11-20 16:20 ` [PATCH v5 0/4] MT7621 PCIe PHY Sergio Paracuellos
2020-11-21 12:10 ` Vinod Koul
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=20201119154337.9195-1-sergio.paracuellos@gmail.com \
--to=sergio.paracuellos@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neil@brown.name \
--cc=robh+dt@kernel.org \
--cc=vkoul@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).