Re: Driver for tightly coupled memory

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Alessio Sangalli
Date: Tuesday, September 16, 2008 - 3:49 pm

Ben Nizette wrote:


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


--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Driver for tightly coupled memory, Alessio Sangalli, (Mon Sep 15, 1:35 pm)
Re: Driver for tightly coupled memory, Ben Dooks, (Tue Sep 16, 2:35 am)
Re: Driver for tightly coupled memory, Alessio Sangalli, (Tue Sep 16, 10:39 am)
Re: Driver for tightly coupled memory, Ben Nizette, (Tue Sep 16, 3:27 pm)
Re: Driver for tightly coupled memory, Alessio Sangalli, (Tue Sep 16, 3:49 pm)
Re: Driver for tightly coupled memory, Ben Nizette, (Tue Sep 16, 4:04 pm)
Re: Driver for tightly coupled memory, Alessio Sangalli, (Tue Sep 16, 4:52 pm)
Re: Driver for tightly coupled memory, Valdis.Kletnieks, (Tue Sep 16, 7:42 pm)
Re: Driver for tightly coupled memory, Alessio Sangalli, (Tue Sep 16, 10:27 pm)
Re: Driver for tightly coupled memory, Valdis.Kletnieks, (Tue Sep 16, 10:39 pm)
Re: Driver for tightly coupled memory, Alessio Sangalli, (Tue Sep 16, 10:55 pm)