From: Bryan Wu <bryan.wu@analog.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Michael Buesch <mb@bu3sch.de>,
bryan.wu@analog.com, Mike Frysinger <vapier.adi@gmail.com>,
Jeff Garzik <jeff@garzik.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH try#2] Blackfin ethernet driver: on chip ethernet MAC controller driver
Date: Sun, 15 Jul 2007 20:10:30 +0800 [thread overview]
Message-ID: <1184501430.3140.75.camel@roc-laptop> (raw)
In-Reply-To: <20070715105358.GA18177@infradead.org>
On Sun, 2007-07-15 at 11:53 +0100, Christoph Hellwig wrote:
> On Sun, Jul 15, 2007 at 12:36:51PM +0200, Michael Buesch wrote:
> > On Sunday 15 July 2007 11:27:09 Bryan Wu wrote:
> > > +#if defined(CONFIG_BFIN_MAC_USE_L1)
> > > +# define bfin_mac_alloc(dma_handle, size) l1_data_sram_zalloc(size)
> > > +# define bfin_mac_free(dma_handle, ptr) l1_data_sram_free(ptr)
> > > +#else
> > > +# define bfin_mac_alloc(dma_handle, size) \
> > > + dma_alloc_coherent(NULL, size, dma_handle, GFP_NORMAL)
> >
> > What is GFP_NORMAL? It's not defined in latest linus' tree.
> > I think you should use GFP_KERNEL, if you can sleep, or GFP_ATOMIC,
> > if you can't.
>
> Actually this whole thing looks fishy. There should be a struct device
> for the dma allocation, through a platform_device. And the
> CONFIG_BFIN_MAC_USE_L1 should go away, the l1 sram should have a dma
> provider so this can be handled through the dma api.
We do have L1 memory DMA allocator and manager, it is depends on
Blackfin arch.
And this driver is Blackfin on-chip ethernet MAC controller.
So it is OK, any idea?
Thanks
- Bryan Wu
next prev parent reply other threads:[~2007-07-15 12:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-15 9:27 [PATCH try#2] Blackfin ethernet driver: on chip ethernet MAC controller driver Bryan Wu
2007-07-15 10:36 ` Michael Buesch
2007-07-15 10:53 ` Christoph Hellwig
2007-07-15 12:10 ` Bryan Wu [this message]
2007-07-15 12:07 ` Bryan Wu
2007-07-15 12:17 ` Michael Buesch
2007-07-15 14:01 ` Bryan Wu
2007-07-15 21:20 ` Michael Buesch
[not found] <fa.5lu+DP35wuS4CFlDsNA/BKJaNLI@ifi.uio.no>
[not found] ` <fa.IGI2ikYsGUxtIMQBx6oB1nxippo@ifi.uio.no>
[not found] ` <fa.FVZq5uXBDDioKCwtChqo2Evai8U@ifi.uio.no>
[not found] ` <fa.4ke11capcBR0kfkUX3qhQonKSzQ@ifi.uio.no>
[not found] ` <fa.d13aWxWKs5IcQxfZHLSYGoam7rQ@ifi.uio.no>
2007-07-15 18:27 ` Robert Hancock
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=1184501430.3140.75.camel@roc-laptop \
--to=bryan.wu@analog.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.org \
--cc=vapier.adi@gmail.com \
/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).