From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-renesas-soc@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org,
Herve Codina <herve.codina@bootlin.com>
Subject: Re: [PATCH 2/2] ARM: dts: renesas: r9a06g032-rzn1d400-eb: enable USB host port
Date: Mon, 5 May 2025 22:27:10 +0200 [thread overview]
Message-ID: <aBkfHudni5WoJLtt@shikoro> (raw)
In-Reply-To: <CAMuHMdW2NHeatmSr4ePj6fPcbT5XNZJr967L3NJ_i6xYwgxaBA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]
> According to Sections 10.6.5.1 (1) ("Meanings of USB_OCI and USB_PPON
> Signals") and Table 10.131 ("OCI and PPON") of the RZ/N1D System Control
> and Peripheral Manual, USB_PPON2 and USB_OC2 are only used when both
> ports are configured for host mode. When port 1 is configured for
> function mode, port 2 uses USB_PPON1 and USB_OC1 instead, so you
> shouldn't need pin control for USB_PPON2 and USB_OC2.
> However, that does not match the schematics, which show that USB_PPON2
> and USB_OC2 are wired to port 2's power switch.
> Can you enlighten me?
Both pins I enabled here are routed to the Config CPLD (check the DB
datasheet, page 9). This handles the configuration and routes whatever
is selected to the EB then. The pins on the EB are always named PPON2
and OC2. Because these pins are always routed to the CPLD, I think it
makes sense to have them described like this always. I didn't see
another way to use them anyhow. It could be argued, though, that these
pinmux properties belong to the DB, then. Maybe this makes more sense?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-05-05 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 10:01 [PATCH 0/2] ARM: dts: renesas: r9a06g032-rzn1d400: enable USB Wolfram Sang
2025-04-25 10:01 ` [PATCH 1/2] ARM: dts: renesas: r9a06g032-rzn1d400-db: enable USB device port Wolfram Sang
2025-05-05 13:48 ` Geert Uytterhoeven
2025-04-25 10:01 ` [PATCH 2/2] ARM: dts: renesas: r9a06g032-rzn1d400-eb: enable USB host port Wolfram Sang
2025-05-05 14:03 ` Geert Uytterhoeven
2025-05-05 20:27 ` Wolfram Sang [this message]
2025-05-08 17:46 ` Geert Uytterhoeven
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=aBkfHudni5WoJLtt@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=herve.codina@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh@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