public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Nizette <bn@niasdigital.com>
To: Alessio Sangalli <alesan@manoweb.com>
Cc: Ben Dooks <ben-linux@fluff.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Driver for tightly coupled memory
Date: Wed, 17 Sep 2008 09:04:50 +1000	[thread overview]
Message-ID: <1221606290.3598.41.camel@moss.renham> (raw)
In-Reply-To: <48D03811.9070805@manoweb.com>


On Tue, 2008-09-16 at 15:49 -0700, Alessio Sangalli wrote:
> 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?

Generally the genalloc pool will be set up exactly once, at boot, by the
platform code.  Then yes indeed the pool can be exported for driver use.

	--Ben.

  reply	other threads:[~2008-09-16 23:05 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
2008-09-16 23:04         ` Ben Nizette [this message]
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=1221606290.3598.41.camel@moss.renham \
    --to=bn@niasdigital.com \
    --cc=alesan@manoweb.com \
    --cc=ben-linux@fluff.org \
    --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