From: "Álvaro Fernández Rojas" <noltari@gmail.com>
To: simon@octiron.net, simon@arlott.org, jonas.gorski@gmail.com,
kishon@ti.com, vkoul@kernel.org, robh+dt@kernel.org,
f.fainelli@gmail.com, bcm-kernel-feedback-list@broadcom.com,
p.zabel@pengutronix.de, krzk@kernel.org,
gregkh@linuxfoundation.org, alcooperx@gmail.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: "Álvaro Fernández Rojas" <noltari@gmail.com>
Subject: [PATCH v7 0/2] phy: bcm63xx-usbh: Add BCM63xx USBH driver
Date: Fri, 17 Jul 2020 11:47:54 +0200 [thread overview]
Message-ID: <20200717094756.9951-1-noltari@gmail.com> (raw)
Add BCM63xx USBH PHY driver for BMIPS.
v7: remove Simon from authors and introduce changes suggested by Rob:
- Move clock conditions to the main section.
- Set missing additionalProperties to false.
v6: introduce changes suggested by Rob and Vinod:
- Remove BMIPS_GENERIC default from kconfig.
- Print registered message as debug.
- Add another if case to device tree binding for SoCs with just 1 clock.
- Ignored "additionalProperties: false" suggestion since it triggers a
warning. This has been reported, but I haven't received any answer yet.
v5: use devm_reset_control_get_exclusive.
v4: fix dt-bindings documentation and improve device mode config.
v3: introduce changes suggested by Florian:
- Add support for device mode.
v2: introduce changes suggested by Florian:
- phy-cells changed to 1.
- Drop OF dependency (use device_get_match_data).
- Drop __initconst from variant tables.
- Use devm_clk_get_optional.
Álvaro Fernández Rojas (2):
dt-bindings: phy: add bcm63xx-usbh bindings
phy: bcm63xx-usbh: Add BCM63xx USBH driver
.../bindings/phy/brcm,bcm63xx-usbh-phy.yaml | 79 +++
drivers/phy/broadcom/Kconfig | 8 +
drivers/phy/broadcom/Makefile | 1 +
drivers/phy/broadcom/phy-bcm63xx-usbh.c | 456 ++++++++++++++++++
4 files changed, 544 insertions(+)
create mode 100644 Documentation/devicetree/bindings/phy/brcm,bcm63xx-usbh-phy.yaml
create mode 100644 drivers/phy/broadcom/phy-bcm63xx-usbh.c
--
2.27.0
WARNING: multiple messages have this Message-ID (diff)
From: "Álvaro Fernández Rojas" <noltari@gmail.com>
To: simon@octiron.net, simon@arlott.org, jonas.gorski@gmail.com,
kishon@ti.com, vkoul@kernel.org, robh+dt@kernel.org,
f.fainelli@gmail.com, bcm-kernel-feedback-list@broadcom.com,
p.zabel@pengutronix.de, krzk@kernel.org,
gregkh@linuxfoundation.org, alcooperx@gmail.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: "Álvaro Fernández Rojas" <noltari@gmail.com>
Subject: [PATCH v7 0/2] phy: bcm63xx-usbh: Add BCM63xx USBH driver
Date: Fri, 17 Jul 2020 11:47:54 +0200 [thread overview]
Message-ID: <20200717094756.9951-1-noltari@gmail.com> (raw)
Add BCM63xx USBH PHY driver for BMIPS.
v7: remove Simon from authors and introduce changes suggested by Rob:
- Move clock conditions to the main section.
- Set missing additionalProperties to false.
v6: introduce changes suggested by Rob and Vinod:
- Remove BMIPS_GENERIC default from kconfig.
- Print registered message as debug.
- Add another if case to device tree binding for SoCs with just 1 clock.
- Ignored "additionalProperties: false" suggestion since it triggers a
warning. This has been reported, but I haven't received any answer yet.
v5: use devm_reset_control_get_exclusive.
v4: fix dt-bindings documentation and improve device mode config.
v3: introduce changes suggested by Florian:
- Add support for device mode.
v2: introduce changes suggested by Florian:
- phy-cells changed to 1.
- Drop OF dependency (use device_get_match_data).
- Drop __initconst from variant tables.
- Use devm_clk_get_optional.
Álvaro Fernández Rojas (2):
dt-bindings: phy: add bcm63xx-usbh bindings
phy: bcm63xx-usbh: Add BCM63xx USBH driver
.../bindings/phy/brcm,bcm63xx-usbh-phy.yaml | 79 +++
drivers/phy/broadcom/Kconfig | 8 +
drivers/phy/broadcom/Makefile | 1 +
drivers/phy/broadcom/phy-bcm63xx-usbh.c | 456 ++++++++++++++++++
4 files changed, 544 insertions(+)
create mode 100644 Documentation/devicetree/bindings/phy/brcm,bcm63xx-usbh-phy.yaml
create mode 100644 drivers/phy/broadcom/phy-bcm63xx-usbh.c
--
2.27.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-07-17 9:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 9:47 Álvaro Fernández Rojas [this message]
2020-07-17 9:47 ` [PATCH v7 0/2] phy: bcm63xx-usbh: Add BCM63xx USBH driver Álvaro Fernández Rojas
2020-07-17 9:47 ` [PATCH v7 1/2] dt-bindings: phy: add bcm63xx-usbh bindings Álvaro Fernández Rojas
2020-07-17 9:47 ` Álvaro Fernández Rojas
2020-07-17 9:47 ` [PATCH v7 2/2] phy: bcm63xx-usbh: Add BCM63xx USBH driver Álvaro Fernández Rojas
2020-07-17 9:47 ` Álvaro Fernández Rojas
2020-07-17 10:35 ` [PATCH v7 0/2] " Simon Arlott
2020-07-17 10:35 ` Simon Arlott
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=20200717094756.9951-1-noltari@gmail.com \
--to=noltari@gmail.com \
--cc=alcooperx@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonas.gorski@gmail.com \
--cc=kishon@ti.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=simon@arlott.org \
--cc=simon@octiron.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.