All of lore.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 08:27:02 +1000	[thread overview]
Message-ID: <1221604022.3598.4.camel@moss.renham> (raw)
In-Reply-To: <48CFEF3F.5040901@manoweb.com>


On Tue, 2008-09-16 at 10:39 -0700, Alessio Sangalli wrote:
> Ben Dooks wrote:
> > IIRC, there's no current support for using TCMs.
> 
> I think I will write a module that implements a software FIFO. One
> function to allocate a FIFO n words deep, a "push" and a "pop" and
> similar. The calling module will have to setup the FIFO and use it
> probably in ISRs or similar (the policy will totally remain in the
> caller module). Any comments on such approach?

I'd feel uncomfortable about picking an arbitrary function for the TCM
to accomplish.  Why don't you just set up a genalloc on that RAM and let
the user use it for what they will?

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 :-)

	--Ben.

  reply	other threads:[~2008-09-16 22:27 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 [this message]
2008-09-16 22:49       ` Alessio Sangalli
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=1221604022.3598.4.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.