From: Florian Fainelli <florian@openwrt.org>
To: Thierry Reding <thierry.reding@avionic-design.de>
Cc: David Brownell <david-b@pacbell.net>,
spi-devel-general@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [spi-devel-general] [PATCH v2] spi: Add support for the OpenCores SPI controller.
Date: Wed, 29 Apr 2009 11:15:34 +0200 [thread overview]
Message-ID: <200904291115.34847.florian@openwrt.org> (raw)
In-Reply-To: <20090429063104.GB7784@avionic-design.de>
Le Wednesday 29 April 2009 08:31:04 Thierry Reding, vous avez écrit :
> * David Brownell wrote:
> > On Tuesday 28 April 2009, Florian Fainelli wrote:
> > > > > Is this the http://www.opencores.org/?do=project&who=spi core?
> > > >
> > > > Yes, it is.
> > > >
> > > > > Its summary says "Variable length of transfer word up to 32 bits";
> > > > > does that mean "configurable when core is synthesized" instead of
> > > > > truly "variable"?
> > >
> > > This is indeed configured at synthesis time.
> >
> > Now I'm confused again. Thierry says (below) that the number of bits
> > can be set per-"transfer".
> >
> > Now, I can easily understand that a *maximum* would be configured
> > at synthesis time ... if there's a 32-bit CPU or DMA engine, it'd
> > make very limited sense to interact using 128-bit I/O words.
The maximum size of the FIFO is configured at synthesis time should have made
this clear before, sorry for the confusion.
>
> I can't really comment on the synthesis because I'm not involved with that
> part. What I was saying that the core provides a field in the control
> register which defines the number of bits to transfer from/to the
> transmit/receive registers. The maximum number of bits that can be
> specified in this way is 128.
Yes, which matches the FIFO size configured in the IP at synthesis time.
>
> > Is there both a configurable maximum, *and* a word-size setting that
> > can be changed on the fly? That's what I would expect; it's what
> > most other designs do. The only time I've seen fixed "you must use
> > N-bit words" designs is on cost-eradicated 8-bit microcontrollers.
>
> Perhaps that maximum number of bits that can be set through the control
> register is what can be configured at synthesis time.
Provided that your FIFO is 128-bits, you can of course ask the core to do up
to the FIFO-size transfers for instance provided that you do not exceed the
size of the FIFO. The later can obviously not be changed on-the-fly since
physical resources of the FPGA for this should be reserved at synthesis time.
Of course, one could use partial reconfiguration to increase the size, but
that's slightly off-topic ;)
--
Best regards, Florian Fainelli
Email : florian@openwrt.org
http://openwrt.org
-------------------------------
next prev parent reply other threads:[~2009-04-29 9:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 8:07 [PATCH] spi: Add support for the OpenCores SPI controller Thierry Reding
2009-03-30 8:44 ` Florian Fainelli
[not found] ` <1238054874-28215-1-git-send-email-thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>
2009-04-04 19:27 ` David Brownell
2009-04-04 19:27 ` David Brownell
2009-04-28 11:01 ` [PATCH v2] " Thierry Reding
[not found] ` <1240916464-4187-1-git-send-email-thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>
2009-04-28 11:15 ` Thierry Reding
2009-04-28 11:15 ` [spi-devel-general] " Thierry Reding
[not found] ` <20090428111532.GA14422-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>
2009-04-28 11:58 ` David Brownell
2009-04-28 11:58 ` [spi-devel-general] " David Brownell
2009-04-28 12:20 ` Thierry Reding
2009-04-28 13:41 ` Florian Fainelli
2009-04-28 20:54 ` David Brownell
2009-04-29 6:31 ` Thierry Reding
2009-04-29 9:15 ` Florian Fainelli [this message]
2009-04-28 21:03 ` David Brownell
2009-04-29 6:22 ` Thierry Reding
[not found] ` <20090428122011.GB6325-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>
2009-04-28 21:03 ` David Brownell
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=200904291115.34847.florian@openwrt.org \
--to=florian@openwrt.org \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=thierry.reding@avionic-design.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 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.