From: E Shattow <e@freeshell.de>
To: Henry Bell <dmoo_dv@protonmail.com>
Cc: E Shattow <e@freeshell.de>,
Emil Renner Berthing <kernel@esmil.dk>,
Conor Dooley <conor@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/1] riscv: dts: starfive: jh7110-pine64-star64: enable usb0 host function
Date: Mon, 25 Nov 2024 23:38:16 -0800 [thread overview]
Message-ID: <20241126073836.17208-1-e@freeshell.de> (raw)
Enable host mode JH7110 on-chip USB for Pine64 Star64 by setting host mode
and connect vbus pinctrl.
This functionality depends on setting the USB over-current register to
disable at bootloader phase, for example U-Boot:
https://patchwork.ozlabs.org/project/uboot/patch/20241012031328.4268-6-minda.chen@starfivetech.com/
If the over-current register is not prepared for us then the result is no
change in functional outcome with this patch applied; there is an error
visible to the user and this usb configuration fails (same as it is now).
Changes since v2:
- Rebase on latest master
Changes since v1:
- Rebase on linux-next/master
- use tabs for code indent
E Shattow (1):
riscv: dts: starfive: jh7110-pine64-star64: enable usb0 host function
.../boot/dts/starfive/jh7110-pine64-star64.dts | 18 +++++++++++++++++-
1 file changed, 17 insertions(+), 1 deletion(-)
--
2.45.2
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2024-11-26 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 7:38 E Shattow [this message]
2024-11-26 7:38 ` [PATCH v3 1/1] riscv: dts: starfive: jh7110-pine64-star64: enable usb0 host function E Shattow
2024-11-26 17:59 ` Conor Dooley
2024-11-27 13:23 ` Emil Renner Berthing
2024-11-27 13:38 ` E Shattow
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=20241126073836.17208-1-e@freeshell.de \
--to=e@freeshell.de \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmoo_dv@protonmail.com \
--cc=kernel@esmil.dk \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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;
as well as URLs for NNTP newsgroup(s).