linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Jarkko Nikula <jhnikula@gmail.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Girdwood, Liam" <lrg@ti.com>,
	"ABRAHAM, KISHON VIJAY" <kishon@ti.com>
Subject: Re: [PATCH] OMAP4: McBSP: Clear rx_irq at probe time
Date: Tue, 31 May 2011 00:57:02 -0700	[thread overview]
Message-ID: <20110531075701.GN11352@atomide.com> (raw)
In-Reply-To: <201105181539.46959.peter.ujfalusi@ti.com>

* Peter Ujfalusi <peter.ujfalusi@ti.com> [110518 05:36]:
> Hi Tony,
> 
> On Tuesday 17 May 2011 15:57:00 Tony Lindgren wrote:
> > This file should be under drivers/ somewhere, can you
> > guys please take care of that?
> 
> Do you have a place in mind?

How about drivers/mcbsp?

> We have several things under arch/arm/plat-omap, like i2c, dma, fb, gpio, 
> mcbsp, usb...

These are all going away into drivers. Only the code to initialize
platform dta should be under arch/arm/*omap*/.

> Should we create a directory for omap specific drivers under drivers?

No, this was discussed few weeks ago on LAKML. The drivers should be
grouped by type instead.

> For example drivers/omap/ and move the mcbsp there first, without any API 
> change?

This is up to Greg, but I'd assume that a generic framework is the preferred
way to go.

> If needed we can think of changing the interface within McBSP if it is needed 
> for other use later.
> IMHO invention a common framework (as Jarkko was suggesting) for similar 
> interfaces need more work, and synchronization between other platforms.

Sure, but that's the only option we have to merge any new code.

Regards,

Tony

  reply	other threads:[~2011-05-31  7:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 10:33 [PATCH] OMAP4: McBSP: Clear rx_irq at probe time Peter Ujfalusi
2011-05-17 12:29 ` Jarkko Nikula
2011-05-17 12:57   ` Tony Lindgren
2011-05-18  5:52     ` Peter Ujfalusi
2011-05-18  7:59       ` Jarkko Nikula
2011-05-31  7:52         ` Tony Lindgren
2011-05-18 12:39     ` Peter Ujfalusi
2011-05-31  7:57       ` Tony Lindgren [this message]
2011-06-08  7:51         ` Peter Ujfalusi
2011-06-13 13:35           ` Tony Lindgren
2011-06-14 11:19             ` Péter Ujfalusi
2011-06-14 12:05               ` Jarkko Nikula
2011-06-14 12:40                 ` Tony Lindgren

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=20110531075701.GN11352@atomide.com \
    --to=tony@atomide.com \
    --cc=jhnikula@gmail.com \
    --cc=kishon@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=peter.ujfalusi@ti.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;
as well as URLs for NNTP newsgroup(s).