All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Singh Sandeep-B37400 <B37400@freescale.com>
Cc: "devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Francois Romieu <romieu@fr.zoreil.com>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [2/3][PATCH][v2] TDM Framework
Date: Wed, 1 Aug 2012 05:37:38 -0700	[thread overview]
Message-ID: <20120801123738.GA28291@kroah.com> (raw)
In-Reply-To: <3F1D9DCAAB49B94D88DBE05911FA4E6E515F98@039-SN1MPN1-001.039d.mgd.msft.net>

On Wed, Aug 01, 2012 at 12:13:19PM +0000, Singh Sandeep-B37400 wrote:
> > On Mon, Jul 30, 2012 at 09:50:57AM +0000, Singh Sandeep-B37400 wrote:
> > > 1. You should send some kernel mode TDM clients. Without those the
> > framework
> > >    is pretty useless.
> > > [Sandeep] We do have a test client but not good enough to be pushed in
> > > open source, should we add it to documentation??
> > 
> > Then how do you know if the framework is "correct" and good enough for
> > real clients?  We don't add frameworks, or apis, to the kernel without
> > users, so you will have to come up with some users before we can accept
> > it.
> We can only say that this framework is available in FSL BSPs and being used by VoIP companies.
> But running a complete voice stack itself is beyond the scope of Freescale.
> So vendors integrate their solutions with FSL solution.
> To test the framework we have a small application in our BSP (this is a very basic test client) which tests the TDM driver and the SLIC interface from voice  transfer perspective.
> We can get this added in the Linux codebase in some test directory. What could be a good place for this?

tools/ is a good place for that.

And sorry, I was thinking you had kernel drivers that attached to this
framework, not userspace programs.  Actually, what is the user/kernel
interface for this framework, I seem to have missed that entirely.  You
will have to document that quite well, and run it by the linux-api
mailing list.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: greg@kroah.com (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [2/3][PATCH][v2] TDM Framework
Date: Wed, 1 Aug 2012 05:37:38 -0700	[thread overview]
Message-ID: <20120801123738.GA28291@kroah.com> (raw)
In-Reply-To: <3F1D9DCAAB49B94D88DBE05911FA4E6E515F98@039-SN1MPN1-001.039d.mgd.msft.net>

On Wed, Aug 01, 2012 at 12:13:19PM +0000, Singh Sandeep-B37400 wrote:
> > On Mon, Jul 30, 2012 at 09:50:57AM +0000, Singh Sandeep-B37400 wrote:
> > > 1. You should send some kernel mode TDM clients. Without those the
> > framework
> > >    is pretty useless.
> > > [Sandeep] We do have a test client but not good enough to be pushed in
> > > open source, should we add it to documentation??
> > 
> > Then how do you know if the framework is "correct" and good enough for
> > real clients?  We don't add frameworks, or apis, to the kernel without
> > users, so you will have to come up with some users before we can accept
> > it.
> We can only say that this framework is available in FSL BSPs and being used by VoIP companies.
> But running a complete voice stack itself is beyond the scope of Freescale.
> So vendors integrate their solutions with FSL solution.
> To test the framework we have a small application in our BSP (this is a very basic test client) which tests the TDM driver and the SLIC interface from voice  transfer perspective.
> We can get this added in the Linux codebase in some test directory. What could be a good place for this?

tools/ is a good place for that.

And sorry, I was thinking you had kernel drivers that attached to this
framework, not userspace programs.  Actually, what is the user/kernel
interface for this framework, I seem to have missed that entirely.  You
will have to document that quite well, and run it by the linux-api
mailing list.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Singh Sandeep-B37400 <B37400@freescale.com>
Cc: Francois Romieu <romieu@fr.zoreil.com>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"galak@kernel.crashing.org" <galak@kernel.crashing.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [2/3][PATCH][v2] TDM Framework
Date: Wed, 1 Aug 2012 05:37:38 -0700	[thread overview]
Message-ID: <20120801123738.GA28291@kroah.com> (raw)
In-Reply-To: <3F1D9DCAAB49B94D88DBE05911FA4E6E515F98@039-SN1MPN1-001.039d.mgd.msft.net>

On Wed, Aug 01, 2012 at 12:13:19PM +0000, Singh Sandeep-B37400 wrote:
> > On Mon, Jul 30, 2012 at 09:50:57AM +0000, Singh Sandeep-B37400 wrote:
> > > 1. You should send some kernel mode TDM clients. Without those the
> > framework
> > >    is pretty useless.
> > > [Sandeep] We do have a test client but not good enough to be pushed in
> > > open source, should we add it to documentation??
> > 
> > Then how do you know if the framework is "correct" and good enough for
> > real clients?  We don't add frameworks, or apis, to the kernel without
> > users, so you will have to come up with some users before we can accept
> > it.
> We can only say that this framework is available in FSL BSPs and being used by VoIP companies.
> But running a complete voice stack itself is beyond the scope of Freescale.
> So vendors integrate their solutions with FSL solution.
> To test the framework we have a small application in our BSP (this is a very basic test client) which tests the TDM driver and the SLIC interface from voice  transfer perspective.
> We can get this added in the Linux codebase in some test directory. What could be a good place for this?

tools/ is a good place for that.

And sorry, I was thinking you had kernel drivers that attached to this
framework, not userspace programs.  Actually, what is the user/kernel
interface for this framework, I seem to have missed that entirely.  You
will have to document that quite well, and run it by the linux-api
mailing list.

thanks,

greg k-h

  reply	other threads:[~2012-08-01 12:37 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-27 14:05 [2/3][PATCH][v2] TDM Framework sandeep
2012-07-27 14:05 ` sandeep
2012-07-27 14:05 ` sandeep at freescale.com
2012-07-27 14:05 ` [1/3][PATCH][v2] Adding documentation for TDM sandeep
2012-07-27 14:05   ` sandeep
2012-07-27 14:05   ` sandeep at freescale.com
2012-07-27 14:05   ` [3/3][PATCH][v2] Added TDM device support and Freescale Starlite driver sandeep
2012-07-27 14:05     ` sandeep
2012-07-27 14:05     ` sandeep at freescale.com
2012-07-27 14:11 ` [2/3][PATCH][v2] TDM Framework John Stoffel
2012-07-27 14:11   ` John Stoffel
2012-07-27 14:11   ` John Stoffel
2012-07-30  9:29   ` Singh Sandeep-B37400
2012-07-30  9:29     ` Singh Sandeep-B37400
2012-07-30  9:29     ` Singh Sandeep-B37400
2012-07-30 14:10     ` John Stoffel
2012-07-30 14:10       ` John Stoffel
2012-07-30 14:10       ` John Stoffel
2012-07-31  6:40       ` Singh Sandeep-B37400
2012-07-31  6:40         ` Singh Sandeep-B37400
2012-07-31  6:40         ` Singh Sandeep-B37400
2012-07-27 14:51 ` Russell King - ARM Linux
2012-07-27 14:51   ` Russell King - ARM Linux
2012-07-27 14:51   ` Russell King - ARM Linux
2012-07-30 13:00   ` Singh Sandeep-B37400
2012-07-30 13:00     ` Singh Sandeep-B37400
2012-07-30 13:00     ` Singh Sandeep-B37400
2012-07-27 15:25 ` Francois Romieu
2012-07-27 15:25   ` Francois Romieu
2012-07-27 15:25   ` Francois Romieu
2012-07-30  9:50   ` Singh Sandeep-B37400
2012-07-30  9:50     ` Singh Sandeep-B37400
2012-07-30  9:50     ` Singh Sandeep-B37400
2012-07-30 16:01     ` Greg KH
2012-07-30 16:01       ` Greg KH
2012-07-30 16:01       ` Greg KH
2012-08-01 12:13       ` Singh Sandeep-B37400
2012-08-01 12:13         ` Singh Sandeep-B37400
2012-08-01 12:13         ` Singh Sandeep-B37400
2012-08-01 12:37         ` Greg KH [this message]
2012-08-01 12:37           ` Greg KH
2012-08-01 12:37           ` Greg KH
2012-08-21 14:13           ` Mark Brown
2012-08-21 14:13             ` Mark Brown
2012-08-21 14:13             ` Mark Brown
2012-07-30 15:45   ` Mark Brown
2012-07-30 15:45     ` Mark Brown
2012-07-30 15:45     ` Mark Brown
2012-07-31  6:41     ` Singh Sandeep-B37400
2012-07-31  6:41       ` Singh Sandeep-B37400
2012-07-31  6:41       ` Singh Sandeep-B37400
2012-07-27 17:59 ` Greg KH
2012-07-27 17:59   ` Greg KH
2012-07-27 17:59   ` Greg KH
2012-07-30  9:10   ` Aggrwal Poonam-B10812
2012-07-30  9:10     ` Aggrwal Poonam-B10812
2012-07-30  9:10     ` Aggrwal Poonam-B10812
2012-07-30 16:04     ` Greg KH
2012-07-30 16:04       ` Greg KH
2012-07-30 16:04       ` Greg KH
2012-07-27 18:12 ` Greg KH
2012-07-27 18:12   ` Greg KH
2012-07-27 18:12   ` Greg KH
2012-07-30  9:13   ` Aggrwal Poonam-B10812
2012-07-30  9:13     ` Aggrwal Poonam-B10812
2012-07-30  9:13     ` Aggrwal Poonam-B10812

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=20120801123738.GA28291@kroah.com \
    --to=greg@kroah.com \
    --cc=B37400@freescale.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=romieu@fr.zoreil.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 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.