From: "Eric Bénard" <eric@eukrea.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: fsl-udc (USB gadget) anyone?
Date: Mon, 16 Aug 2010 09:58:09 +0200 [thread overview]
Message-ID: <4C68EF91.9020206@eukrea.com> (raw)
In-Reply-To: <20100816070904.GG27749@pengutronix.de>
Hi Sacha, Hi Baruch,
Le 16/08/2010 09:09, Sascha Hauer a écrit :
> On Mon, Aug 16, 2010 at 09:37:04AM +0300, Baruch Siach wrote:
>> Hi Barebox list,
>>
>> I see that there are no in-tree fsl-udc driver users. Does anyone here have
>> experience with this driver on an i.MX based system? What pre-probe()
>> initialization does this driver require at the platform code?
>
>
> We are using it on a custom i.MX25 board (which is not in mainline
> because hardly anyone could make use of the code). Here is the platform
> initialization code (mixed with ehci host support). It works fine in DFU
> mode, serial support is probably not working. I have tried serial
> support, but had problems integrating it properly in barebox.
interesting, I've tested it on an i.MX27 and I had to do the following
change to get DFU working fine, else the 1st packet's last bytes were
always wrong when flashing data to the NOR (or simply copying data into
RAM) :
http://www.spinics.net/lists/u-boot-v2/msg01166.html
Do you think this fix is wrong ?
The init is the following :
static struct fsl_usb2_platform_data udc_info = {
.operating_mode = FSL_USB2_DR_DEVICE,
.phy_mode = FSL_USB2_PHY_ULPI,
};
static struct device_d udc_dev = {
.name = "fsl-udc",
.map_base = IMX_OTG_BASE,
.platform_data = &udc_info,
};
Eric
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-08-16 7:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 6:37 Baruch Siach
2010-08-16 7:09 ` Sascha Hauer
2010-08-16 7:58 ` Eric Bénard [this message]
2010-08-17 14:13 ` Baruch Siach
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=4C68EF91.9020206@eukrea.com \
--to=eric@eukrea.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@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