mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Subhasish Ghosh" <subhasish@mistralsolutions.com>
To: "Nori, Sekhar" <nsekhar@ti.com>
Cc: "Greg KH" <greg@kroah.com>,
	<davinci-linux-open-source@linux.davincidsp.com>,
	<linux-arm-kernel@lists.infradead.org>,
	"Watkins, Melissa" <m-watkins@ti.com>,
	<sachi@mistralsolutions.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Randy Dunlap" <randy.dunlap@oracle.com>,
	"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 08/11] tty: add pruss SUART driver
Date: Mon, 16 May 2011 10:47:18 +0530	[thread overview]
Message-ID: <78EB813416554F1A973EF20AA714ADF8@subhasishg> (raw)

Hi Sekhar,

>>> Say, if the driver is loaded as a module.
>>> If I allocate the sram in the platform code, how to I
>>> free it when the driver is unloaded. 
>> 
>> This is what I said in my last e-mail. What is
>> the issue you see with this approach?
>> 
>> | Thanks for the clarification. In this case, the driver
>> | should use platform callbacks to get/put fast fifo
>> | space. In case this callback is not populated by the
>> | platform or returns an error, the driver should fall
>> | back to allocating from DDR.
>> 
> 
> ok, so what you are suggesting is that I implement some
> callbacks (like .fifo_alloc, .fifo_dealloc) which can allocate
> memory using sram_alloc.
> My doubt is, if already such API's are there (by Russel) or you
> are suggesting to implement them.

I can add the fifo_alloc/dealloc as part of the suart platform_data,
Is that's what you are suggesting. If you may please point me out 
to any example. I am just not clear with this. 

             reply	other threads:[~2011-05-16  5:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16  5:17 Subhasish Ghosh [this message]
2011-05-17 18:32 ` Nori, Sekhar
2011-05-20  7:14   ` Subhasish Ghosh
     [not found] <1303474109-6212-1-git-send-email-subhasish@mistralsolutions.com>
2011-04-22 12:08 ` Subhasish Ghosh
2011-04-25 21:20   ` Greg KH
2011-04-26  6:51     ` Nori, Sekhar
2011-04-26 12:45       ` Greg KH
2011-04-27  5:23         ` Subhasish Ghosh
2011-04-27 11:19           ` Nori, Sekhar
2011-04-27 13:15             ` Subhasish Ghosh
2011-04-27 17:50               ` Nori, Sekhar
2011-05-02  8:34                 ` Subhasish Ghosh
2011-05-02 17:15                   ` Nori, Sekhar
2011-05-10 10:54             ` Subhasish Ghosh
2011-05-10 13:13               ` Nori, Sekhar
2011-05-13 12:10                 ` Subhasish Ghosh
2011-05-09 13:39   ` Subhasish Ghosh
2011-05-09 13:46     ` Alan Cox
2011-05-09 13:50       ` Subhasish Ghosh
2011-05-09 13:55         ` Alan Cox
2011-05-10  6:17           ` Subhasish Ghosh
2011-05-10 13:32             ` Alan Cox
2011-05-11  7:01               ` Subhasish Ghosh
2011-05-11 10:35                 ` Alan Cox

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=78EB813416554F1A973EF20AA714ADF8@subhasishg \
    --to=subhasish@mistralsolutions.com \
    --cc=akpm@linux-foundation.org \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=greg@kroah.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m-watkins@ti.com \
    --cc=nsekhar@ti.com \
    --cc=randy.dunlap@oracle.com \
    --cc=sachi@mistralsolutions.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

all inboxes | Powered by JetHome®