From: Michael Graichen <michael.graichen@hotmail.com>
To: Lucas Stach <l.stach@pengutronix.de>,
barebox <barebox@lists.infradead.org>
Subject: AW: [PATCH 1/1] zedboard: add support for usb
Date: Tue, 18 May 2021 08:05:29 +0000 [thread overview]
Message-ID: <AM9P192MB0870DF9401D3DE0A1610CCFAAB2C9@AM9P192MB0870.EURP192.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <5232b30053c40731238b1c67028810b716cc6e49.camel@pengutronix.de>
Hey Lucas,
[...]
> This change does 3 distinct things and should be split in 3 patches to
> do one thing at a time:
> - add Zynq EHCI support
> - add ULPI PHY ID
> - add Zedboard USB pinmux
no problem, I can split this is separate patches.
[...]
> Maybe update the defconfig too, if it doesn't blow up the image size
> too much?
This is the harder part. It actually needs support of CONFIG_USB_ULPI and CONFIG_USB_EHCI
+config USB_EHCI_ZYNQ
+ bool "Support for Xilinx Zynq on-chip EHCI USB controller"
+ depends on ARCH_ZYNQ
+ select USB_EHCI
+ select USB_ULPI
+ help
+ Enable support for Zynq on-chip EHCI USB controller
+
and that will blow up the image size, because ethernet is selected in zynq_defconfig right now.
If you want to do somethink usefull, like CONFIG_USB_STORAGE, with it its even worse.
That's why I came up with the two stage boot process from the other patch.
[...]
> pdata isn't used anywhere AFAICS, maybe drop it and simplify the code?
right, I'll remove that.
best regards
Michael
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2021-05-18 8:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 14:08 Michael Graichen
2021-05-05 8:19 ` Lucas Stach
2021-05-18 8:05 ` Michael Graichen [this message]
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=AM9P192MB0870DF9401D3DE0A1610CCFAAB2C9@AM9P192MB0870.EURP192.PROD.OUTLOOK.COM \
--to=michael.graichen@hotmail.com \
--cc=barebox@lists.infradead.org \
--cc=l.stach@pengutronix.de \
/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