From: Mugunthan V N <mugunthanvnm@ti.com>
To: <netdev@vger.kernel.org>
Cc: <linux-omap@vger.kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Sekhar Nori <nsekhar@ti.com>
Subject: Re: [net-next PATCH] driver: net: cpsw: add no_bd_ram dt parsing
Date: Mon, 12 Oct 2015 13:50:48 +0530 [thread overview]
Message-ID: <561B6D60.9060301@ti.com> (raw)
In-Reply-To: <1444385206-7011-1-git-send-email-mugunthanvnm@ti.com>
On Friday 09 October 2015 03:36 PM, Mugunthan V N wrote:
> cpdma is capable of placing the dma descriptors in ddr using
> dma_alloc_coherent() when the internal bd ram size is not enough.
> To utilize this feature pass the DT parameter "no_bd_ram" and
> increase bd_ram_size and number of rx descriptors.
>
> Signed-off-by: Mugunthan V N <mugunthanvnm@ti.com>
Dave
Please drop this patch as it is not working on AM437x platform. Will
send a v2 after fixing it.
Regards
Mugunthan V N
prev parent reply other threads:[~2015-10-12 8:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 10:06 [net-next PATCH] driver: net: cpsw: add no_bd_ram dt parsing Mugunthan V N
2015-10-12 8:20 ` Mugunthan V N [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=561B6D60.9060301@ti.com \
--to=mugunthanvnm@ti.com \
--cc=davem@davemloft.net \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nsekhar@ti.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).