From: Chris Morgan <macromorgan@hotmail.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Ryan Walklin <ryan@testtoast.com>, Chen-Yu Tsai <wens@csie.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
devicetree@vger.kernel.org, linux-sunxi@lists.linux.dev
Subject: Re: [PATCH v2 4/5] arm64: dts: allwinner: h700: Add RG35XX-H DTS
Date: Sat, 20 Apr 2024 22:09:40 -0500 [thread overview]
Message-ID: <DM4PR05MB9229B7D4654478D28D1BC2B6A5132@DM4PR05MB9229.namprd05.prod.outlook.com> (raw)
In-Reply-To: <20240421020627.6d186f8f@minigeek.lan>
On Sun, Apr 21, 2024 at 02:06:27AM +0100, Andre Przywara wrote:
> On Sat, 20 Apr 2024 22:43:58 +1200
> Ryan Walklin <ryan@testtoast.com> wrote:
>
> Hi,
>
> > The RG35XX-H adds thumbsticks, a stereo speaker, and a second USB port to the RG35XX-Plus, and has a horizontal form factor.
> >
> > Enabled in this DTS:
> > - Thumbsticks
> > - Second USB port
> >
> > Changelog v1..v2:
> > - Update copyright
> > - Spaces -> Tabs
> > - Add GP ADC joystick axes and mux [1]
> > - Add EHCI/OHCI1 for second USB port and add vbus supply
> >
> > Signed-off-by: Ryan Walklin <ryan@testtoast.com>
> >
> > [1]: https://lore.kernel.org/linux-sunxi/20240417170423.20640-1-macroalpha82@gmail.com/T/#t
>
> As mention on patch 2/5, this might be better an optional dependency,
> so the GPADC part might be a separate patch.
>
> >
> > Signed-off-by: Ryan Walklin <ryan@testtoast.com>
> > ---
> > .../sun50i-h700-anbernic-rg35xx-h.dts | 126 ++++++++++++++++++
> > 1 file changed, 126 insertions(+)
> > create mode 100644 arch/arm64/boot/dts/allwinner/sun50i-h700-anbernic-rg35xx-h.dts
> >
> > diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h700-anbernic-rg35xx-h.dts b/arch/arm64/boot/dts/allwinner/sun50i-h700-anbernic-rg35xx-h.dts
> > new file mode 100644
> > index 000000000000..d62cf5cd9d9b
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/allwinner/sun50i-h700-anbernic-rg35xx-h.dts
> > @@ -0,0 +1,126 @@
> > +// SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +/*
> > + * Copyright (C) 2024 Ryan Walklin <ryan@testtoast.com>.
> > + * Copyright (C) 2024 Chris Morgan <macroalpha82@gmail.com>.
> > + */
> > +
> > +#include "sun50i-h700-anbernic-rg35xx-plus.dts"
> > +
> > +/ {
> > + model = "Anbernic RG35XX H";
> > + compatible = "anbernic,rg35xx-h", "allwinner,sun50i-h700";
> > +
> > + adc-joystick {
> > + compatible = "adc-joystick";
> > + io-channels = <&adc_mux 0>,
> > + <&adc_mux 1>,
> > + <&adc_mux 2>,
> > + <&adc_mux 3>;
> > + pinctrl-0 = <&joy_mux_pin>;
> > + pinctrl-names = "default";
> > + poll-interval = <60>;
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > +
> > + axis@0 {
> > + reg = <0>;
> > + abs-flat = <32>;
> > + abs-fuzz = <32>;
> > + abs-range = <4096 0>;
> > + linux,code = <ABS_X>;
> > + };
> > +
> > + axis@1 {
> > + reg = <1>;
> > + abs-flat = <32>;
> > + abs-fuzz = <32>;
> > + abs-range = <0 4096>;
> > + linux,code = <ABS_Y>;
> > + };
> > +
> > + axis@2 {
> > + reg = <2>;
> > + abs-flat = <32>;
> > + abs-fuzz = <32>;
> > + abs-range = <0 4096>;
> > + linux,code = <ABS_RX>;
> > + };
> > +
> > + axis@3 {
> > + reg = <3>;
> > + abs-flat = <32>;
> > + abs-fuzz = <32>;
> > + abs-range = <4096 0>;
> > + linux,code = <ABS_RY>;
> > + };
> > + };
> > +
> > + adc_mux: adc-mux {
> > + compatible = "io-channel-mux";
> > + channels = "left_x", "left_y", "right_x", "right_y";
> > + #io-channel-cells = <1>;
> > + io-channels = <&gpadc 0>;
> > + io-channel-names = "parent";
> > + mux-controls = <&gpio_mux>;
> > + settle-time-us = <100>;
> > + };
> > +
> > + gpio_keys: gpio-keys-thumb {
>
> Is there any reason to not just use the existing gpio-keys node?
> Either put a label on it in patch 2/5, and reference that below,
> outside of the root node, or use an absolute path reference.
I would also second just putting an alias and adding these to it.
I myself as a preference tend to set the GPIO volume buttons as
a seperate node only so I can enable key repeat on them, otherwise
one node is best.
>
> > + compatible = "gpio-keys";
> > +
> > + button-thumbl {
> > + label = "GPIO Thumb Left";
> > + gpios = <&pio 4 8 GPIO_ACTIVE_LOW>; /* PE8 */
> > + linux,input-type = <EV_KEY>;
> > + linux,code = <BTN_THUMBL>;
> > + };
> > +
> > + button-thumbr {
> > + label = "GPIO Thumb Right";
> > + gpios = <&pio 4 9 GPIO_ACTIVE_LOW>; /* PE9 */
> > + linux,input-type = <EV_KEY>;
> > + linux,code = <BTN_THUMBR>;
> > + };
> > + };
> > +
> > + gpio_mux: mux-controller {
> > + compatible = "gpio-mux";
> > + mux-gpios = <&pio 8 1 GPIO_ACTIVE_LOW>,
> > + <&pio 8 2 GPIO_ACTIVE_LOW>; /* PI1, PI2 */
> > + #mux-control-cells = <0>;
> > + };
> > +};
> > +
> > +&gpadc {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > + status = "okay";
> > +
> > + channel@0 {
> > + reg = <0>;
> > + };
> > +};
> > +
> > +&pio {
After extensive testing with a multimeter and fudging the regulator
voltages up or down, I've been able to figure out the regulator
assignments for each of the different power domains. Schematics would
have helped, but sadly this had to be done the hard way. Based on
past experience with Anbernic I would strongly suspect all devices
have this assignment, but I know for sure my 35XXH does.
vcc-pa-supply = <®_cldo3>;
vcc-pc-supply = <®_cldo3>;
vcc-pe-supply = <®_cldo3>;
vcc-pf-supply = <®_cldo3>;
vcc-pg-supply = <®_aldo4>;
vcc-ph-supply = <®_cldo3>;
vcc-pi-supply = <®_cldo3>;
On my board the reg_cldo3 is a constant 3.3v output, and the reg_aldo4
is a constant 1.8v output.
> > + joy_mux_pin: joy-mux-pin {
> > + pins = "PI0";
> > + function = "gpio_out";
> > + };
> > +};
> > +
> > +&ehci1 {
> > + status = "okay";
> > +};
> > +
> > +&ohci1 {
> > + status = "okay";
> > +};
> > +
> > +&usbotg {
> > + dr_mode = "peripheral";
> > + status = "okay";
> > +};
> > +
> > +&usbphy {
> > + usb1_vbus-supply = <®_vcc_usb>;
>
> This is the dodgy USB supply chain. Any chance we can narrow this down,
> to maybe one GPIO controlled regulator? Also, where does the boost
> controller come into play here?
I haven't figured out the boost regulator yet, but for the host port
I've been able to ascertain there's no less than 2 GPIO controlled
regulators in play. PE5 must be driven high or the USB host port will
not power on at all. If PE5 is driven high then the port kicks on, but
at 3.3v. Once I also enable PI7 the port then reaches 4.6v. I'm not sure
how to get it to a proper 5v yet, I'm still working that part out.
Maybe PE5 is a reset of some kind that's active low, I don't know. I
just know so far/for sure that if PE5 is low then nothing registers on
the USB host port; if PE5 is high but PI7 is low the port sort-of works
at 3.3v, and if both PE5 and PI7 are high the port works consistently
and at 4.6v.
>
> Cheers,
> Andre
>
> > +};
>
Thank you,
Chris
next prev parent reply other threads:[~2024-04-21 3:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 10:43 [PATCH v2 0/5] arm64: dts: allwinner: Add Anbernic RG35XX (Plus/H/2024) support Ryan Walklin
2024-04-20 10:43 ` [PATCH v2 1/5] dt-bindings: arm: sunxi: document Anbernic RG35XX handheld gaming device variants Ryan Walklin
2024-04-20 10:43 ` [PATCH v2 2/5] arm64: dts: allwinner: h700: Add RG35XX 2024 DTS Ryan Walklin
2024-04-20 10:59 ` Krzysztof Kozlowski
2024-04-21 2:05 ` Ryan Walklin
2024-04-21 0:49 ` Andre Przywara
2024-04-21 2:28 ` Ryan Walklin
2024-04-22 10:17 ` Andre Przywara
2024-04-21 4:00 ` Chris Morgan
2024-04-21 8:43 ` Ryan Walklin
2024-04-22 12:34 ` Andre Przywara
2024-04-22 11:06 ` Andre Przywara
2024-04-21 20:01 ` Jernej Škrabec
2024-04-20 10:43 ` [PATCH v2 3/5] arm64: dts: allwinner: h700: Add RG35XX-Plus DTS Ryan Walklin
2024-04-21 0:53 ` Andre Przywara
2024-04-21 16:53 ` Chris Morgan
2024-04-20 10:43 ` [PATCH v2 4/5] arm64: dts: allwinner: h700: Add RG35XX-H DTS Ryan Walklin
2024-04-21 1:06 ` Andre Przywara
2024-04-21 3:09 ` Chris Morgan [this message]
2024-04-21 8:18 ` Ryan Walklin
2024-04-22 10:17 ` Andre Przywara
2024-04-20 10:43 ` [PATCH v2 5/5] arm64: dts: allwinner: h700: Add RG35XX DTBs to Makefile Ryan Walklin
2024-04-21 1:07 ` Andre Przywara
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=DM4PR05MB9229B7D4654478D28D1BC2B6A5132@DM4PR05MB9229.namprd05.prod.outlook.com \
--to=macromorgan@hotmail.com \
--cc=andre.przywara@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=robh@kernel.org \
--cc=ryan@testtoast.com \
--cc=samuel@sholland.org \
--cc=wens@csie.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.