LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Kalra Ashish" <ashish.kalra@freescale.com>
To: "Kumar Gala" <galak@kernel.crashing.org>,
	"Andrew Morton" <akpm@linux-foundation.org>
Cc: "Phillips Kim" <Kim.Phillips@freescale.com>,
	"Aggrwal Poonam" <Poonam.Aggrwal@freescale.com>,
	<sfr@canb.auug.org.au>, <rubini@vision.unipv.it>,
	<linux-ppcdev@ozlabs.kernel.org>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	"Barkowski Michael" <Michael.Barkowski@freescale.com>,
	"Cutler Richard" <Rich.Cutler@freescale.com>,
	"Kalra Ashish" <ashish.kalra@freescale.com>,
	"Suresh PV" <pala@freescale.com>
Subject: RE: [PATCH 0/3] UCC TDM driver for MPC83xx platforms
Date: Wed, 16 Jan 2008 17:17:38 +0530	[thread overview]
Message-ID: <2A6F278C5B66C4459AF4013E77A40CD301149086@zin33exm20.fsl.freescale.net> (raw)
In-Reply-To: <5927F7A4-D42A-40F6-AE9C-EDA34738A752@kernel.crashing.org>

Hello All,
 
I am sure that the TDM bus driver model/framework will make us put a lot
more programming effort without
any assurance of the code being accepted by the Linux community,
especially as there are many
Telephony/VoIP stack implementations in Linux such as the Sangoma
WANPIPE Kernel suite which
have their own Zaptel TDM (channelized zero-copy) interface layer. There
are other High Speed serial (HSS)
API interfaces, again supporting channelized and/or prioritized API
interfaces. All these implementations 
are proprietary and have their own tightly coupled upper layers and
hardware abstraction layers. It is
difficult to predict that these stacks will move towards a generic TDM
bus driver interface. Therefore, i think
we can have our own tightly coupled interface with our VoIP framework
and let us the keep the driver as it is,
i.e., as a misc driver.

Ashish

-----Original Message-----
From: Kumar Gala [mailto:galak@kernel.crashing.org] 
Sent: Tuesday, January 15, 2008 9:01 AM
To: Andrew Morton
Cc: Phillips Kim; Aggrwal Poonam; sfr@canb.auug.org.au;
rubini@vision.unipv.it; linux-ppcdev@ozlabs.kernel.org;
netdev@vger.kernel.org; linux-kernel@vger.kernel.org; Barkowski Michael;
Kalra Ashish; Cutler Richard
Subject: Re: [PATCH 0/3] UCC TDM driver for MPC83xx platforms


On Jan 14, 2008, at 3:15 PM, Andrew Morton wrote:

> On Mon, 14 Jan 2008 12:00:51 -0600
> Kim Phillips <kim.phillips@freescale.com> wrote:
>
>> On Thu, 10 Jan 2008 21:41:20 -0700
>> "Aggrwal Poonam" <Poonam.Aggrwal@freescale.com> wrote:
>>
>>> Hello  All
>>>
>>> I am waiting for more feedback on the patches.
>>>
>>> If there are no objections please consider them for 2.6.25.
>>>
>> if this isn't going to go through Alessandro Rubini/misc drivers, can

>> it go through the akpm/mm tree?
>>
>
> That would work.  But it might be more appropriate to go Kumar-
> >paulus->Linus.

I'm ok w/taking the arch/powerpc bits, but I"m a bit concerned about  
the driver itself.  I'm wondering if we need a TDM framework in the  
kernel.

I guess if Poonam could possibly describe how this driver is actually  
used that would be helpful.  I see we have 8315 with a discrete TDM  
block and I'm guessing 82xx/85xx based CPM parts of some form of TDM  
as well.

- k

  parent reply	other threads:[~2008-01-16 11:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10 11:53 Aggrwal Poonam
2008-01-11  4:41 ` Aggrwal Poonam
2008-01-14 18:00   ` Kim Phillips
2008-01-14 21:15     ` Andrew Morton
2008-01-15  3:31       ` Kumar Gala
2008-01-15 12:05         ` Aggrwal Poonam
2008-01-16 11:47         ` Kalra Ashish [this message]
2008-01-18 11:58         ` Aggrwal Poonam
2008-01-18 12:18           ` Joakim Tjernlund
2008-01-11  4:54 ` Aggrwal Poonam
  -- strict thread matches above, loose matches on Subject: below --
2007-12-10 11:40 Aggrwal Poonam

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=2A6F278C5B66C4459AF4013E77A40CD301149086@zin33exm20.fsl.freescale.net \
    --to=ashish.kalra@freescale.com \
    --cc=Kim.Phillips@freescale.com \
    --cc=Michael.Barkowski@freescale.com \
    --cc=Poonam.Aggrwal@freescale.com \
    --cc=Rich.Cutler@freescale.com \
    --cc=akpm@linux-foundation.org \
    --cc=galak@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ppcdev@ozlabs.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pala@freescale.com \
    --cc=rubini@vision.unipv.it \
    --cc=sfr@canb.auug.org.au \
    --subject='RE: [PATCH 0/3] UCC TDM driver for MPC83xx platforms' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).