From: Rob Herring <robh@kernel.org>
To: Piyush Mehta <piyush.mehta@amd.com>
Cc: gregkh@linuxfoundation.org, michal.simek@amd.com,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
peter.chen@kernel.org, linus.walleij@linaro.org,
paul@crapouillou.net, arnd@arndb.de, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
git@amd.com
Subject: Re: [RFC PATCH 1/3] dt-binding: usb: ulpi-phy: add ulpi-phy binding
Date: Mon, 2 Oct 2023 12:00:25 -0500 [thread overview]
Message-ID: <20231002170025.GA1928031-robh@kernel.org> (raw)
In-Reply-To: <20230929064852.16642-2-piyush.mehta@amd.com>
On Fri, Sep 29, 2023 at 12:18:50PM +0530, Piyush Mehta wrote:
> Create an ulpi-phy binding to read and write PHY registers with explicit
> control of the address and data using the usb.VIEWPORT register.
>
> Signed-off-by: Piyush Mehta <piyush.mehta@amd.com>
> ---
> This binding patch was created to support generic platforms. This binding
> will be modified in accordance with patch [3/3] procedures. One of the
> approch may be Create a zynq phy platform driver in "driver/usb/phy" with
> driver source "phy-ulpi-zynq-usb.c" and then the binding will be particular
> to the Xilinx/AMD zynq platform.
>
> This binding was built with the Zynq hardware design example in consideration
> of as a generic platform. The viewport provide access the Chipidea controller
> to interface with the ULPI PHY.
> ---
> .../devicetree/bindings/usb/ulpi-phy.yaml | 48 +++++++++++++++++++
> 1 file changed, 48 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/usb/ulpi-phy.yaml
>
> diff --git a/Documentation/devicetree/bindings/usb/ulpi-phy.yaml b/Documentation/devicetree/bindings/usb/ulpi-phy.yaml
> new file mode 100644
> index 000000000000..490b2f610129
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/ulpi-phy.yaml
> @@ -0,0 +1,48 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/usb/ulpi-phy.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: ULPI PHY- Generic platform
> +
> +maintainers:
> + - Piyush Mehta <piyush.mehta@amd.com>
> +
> +properties:
> + compatible:
> + const: ulpi-phy
> +
> + reg:
> + maxItems: 1
> +
> + '#phy-cells':
> + const: 0
> +
> + external-drv-vbus:
> + description:
> + If present, configure ulpi-phy external supply to drive 5V on VBus.
> + type: boolean
> +
> + view-port:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description:
> + Address to read and write PHY registers with explicit control of
> + the address and data using the usb.VIEWPORT register.
> +
> +required:
> + - compatible
> + - reg
> + - view-port
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + phy0@e0002000 {
> + compatible = "ulpi-phy";
> + #phy-cells = <0x00>;
> + reg = <0xe0002000 0x1000>;
> + view-port = <0x170>;
I don't understand. Do you have an MMIO address and the VIEWPORT
address to the PHY? You need both?
There's already a defined binding for ULPI bus:
Documentation/devicetree/bindings/usb/ulpi.txt
Why can't you use/expand that?
Rob
next prev parent reply other threads:[~2023-10-02 17:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 6:48 [RFC PATCH 0/3] usb: phy: Add platform driver support for ULPI phys Piyush Mehta
2023-09-29 6:48 ` [RFC PATCH 1/3] dt-binding: usb: ulpi-phy: add ulpi-phy binding Piyush Mehta
2023-09-29 14:04 ` Conor Dooley
2023-09-30 15:15 ` Krzysztof Kozlowski
2023-10-02 17:00 ` Rob Herring [this message]
2023-10-04 11:45 ` Mehta, Piyush
2023-12-01 13:07 ` Mehta, Piyush
2023-09-29 6:48 ` [RFC PATCH 2/3] usb: chipidea: add usb2 phy interface for Zynq platform Piyush Mehta
2023-09-29 6:48 ` [RFC PATCH 3/3] usb: phy: Add platform driver support for ULPI phys Piyush Mehta
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=20231002170025.GA1928031-robh@kernel.org \
--to=robh@kernel.org \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=paul@crapouillou.net \
--cc=peter.chen@kernel.org \
--cc=piyush.mehta@amd.com \
/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.