From: Mike Frysinger <vapier.adi@gmail.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: "Hennerich, Michael" <Michael.Hennerich@analog.com>,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
uclinux-dist-devel@blackfin.uclinux.org
Subject: Re: [Uclinux-dist-devel] [PATCH] wireless: adf702x: new driver for ADF7020/21 parts
Date: Tue, 19 Jan 2010 02:37:24 -0500 [thread overview]
Message-ID: <8bd0f97a1001182337w5b8bf071v1ec90a8a2f5949e5@mail.gmail.com> (raw)
In-Reply-To: <1261497729.2845.8.camel@achroite.uk.solarflarecom.com>
On Tue, Dec 22, 2009 at 11:02, Ben Hutchings wrote:
> On Tue, 2009-12-22 at 11:46 +0000, Hennerich, Michael wrote:
>> >> +static irqreturn_t adf702x_rx_interrupt(int irq, void *dev_id)
>> >> +{
>> >[...]
>> >> + lp->rx_size = adf702x_getrxsize(lp, offset);
>> >> + if (offset == 1) {
>> >> + set_dma_x_count(lp->dma_ch_rx, lp->rx_size);
>> >> + set_dma_start_addr(lp->dma_ch_rx,
>> >> + (unsigned long)lp->rx_buf);
>> >> + } else {
>> >> + lp->rx_buf[0] = lp->rx_buf[3];
>> >> + set_dma_x_count(lp->dma_ch_rx, lp->rx_size - 1);
>> >> + set_dma_start_addr(lp->dma_ch_rx,
>> >> + (unsigned long)&lp->rx_buf[1]);
>> >> + }
>> >> + enable_dma(lp->dma_ch_rx);
>> >> + SSYNC();
>> >
>> >Is this some odd kind of memory barrier?
>>
>> Well - it's an instruction that ensures that the write buffers are flushed and all instructions executed.
>
> I suspect you only need a write memory barrier here (wmb()) not a
> pipeline flush.
it's not a pipeline flush, it's another Blackfin fun piece -- it does
a system sync with the DMA registers
-mike
next prev parent reply other threads:[~2010-01-19 7:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 2:12 [PATCH] wireless: adf702x: new driver for ADF7020/21 parts Mike Frysinger
2009-12-22 3:05 ` Marcel Holtmann
2009-12-22 10:38 ` Hennerich, Michael
2009-12-22 12:46 ` Marcel Holtmann
2009-12-22 12:56 ` Hennerich, Michael
2009-12-22 13:09 ` [Uclinux-dist-devel] " Mike Frysinger
2009-12-22 3:44 ` Ben Hutchings
2009-12-22 11:46 ` Hennerich, Michael
2009-12-22 16:02 ` Ben Hutchings
2010-01-19 7:37 ` Mike Frysinger [this message]
2010-01-19 7:39 ` [PATCH v2] " Mike Frysinger
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=8bd0f97a1001182337w5b8bf071v1ec90a8a2f5949e5@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=uclinux-dist-devel@blackfin.uclinux.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).