From: Alessio Sangalli <alesan@manoweb.com>
To: Ben Nizette <bn@niasdigital.com>
Cc: Ben Dooks <ben-linux@fluff.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Driver for tightly coupled memory
Date: Tue, 16 Sep 2008 15:49:53 -0700 [thread overview]
Message-ID: <48D03811.9070805@manoweb.com> (raw)
In-Reply-To: <1221604022.3598.4.camel@moss.renham>
Ben Nizette wrote:
> If a driver needs a quick FIFO it can attempt to get the RAM for said
> FIFO from the genalloc and fall back to main memory otherwise. Simple,
> flexible, easy :-)
Well, interesting, that is why I asked here before writing code.
In this case however, do you imply that a device driver will just do all
the genalloc stuff? In this case it has to know about the TCM details,
and problems may arise if more than one driver wants to use this
feature. Or, are you suggesting to write a small TCM driver that will do
the gen_pool_create() and gen_pool_add() and then export the struct
gen_pool for use by other drivers that may require it?
I mentioned implementing a FIFO because I already have a couple of
examples where this FIFO thing would be used.
Bye bye, thank you
Alessio
next prev parent reply other threads:[~2008-09-16 22:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 20:35 Driver for tightly coupled memory Alessio Sangalli
2008-09-16 9:35 ` Ben Dooks
2008-09-16 17:39 ` Alessio Sangalli
2008-09-16 22:27 ` Ben Nizette
2008-09-16 22:49 ` Alessio Sangalli [this message]
2008-09-16 23:04 ` Ben Nizette
2008-09-16 23:52 ` Alessio Sangalli
2008-09-17 2:42 ` Valdis.Kletnieks
2008-09-17 5:27 ` Alessio Sangalli
2008-09-17 5:39 ` Valdis.Kletnieks
2008-09-17 5:55 ` Alessio Sangalli
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=48D03811.9070805@manoweb.com \
--to=alesan@manoweb.com \
--cc=ben-linux@fluff.org \
--cc=bn@niasdigital.com \
--cc=linux-kernel@vger.kernel.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