From: Jarkko Nikula <jhnikula@gmail.com>
To: "Péter Ujfalusi" <peter.ujfalusi@ti.com>
Cc: Tony Lindgren <tony@atomide.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, 14 Jun 2011 15:05:30 +0300 [thread overview]
Message-ID: <20110614150530.87e594a5.jhnikula@gmail.com> (raw)
In-Reply-To: <27857936.rzNg0PjYWH@barack>
On Tue, 14 Jun 2011 14:19:34 +0300
Péter Ujfalusi <peter.ujfalusi@ti.com> wrote:
> We have discussion ongoing about the mcbsp code move, and so far the current
> understanding/plan is (Jarkko/Liam correct me if I'm wrong):
> - Fix the OMAP4 support
> - move the code under sound/soc/omap/
> - the reason for this is that McBSP block can be only used for streaming type
> of modes (from omap2430 onwards McBSP does not have clock stop functionality).
> This makes other type of usage hard to say the least.
> - Clean up the code (remove the SPI mode, remove unused code paths at the same
> time)
> - Consolidate the interface for audio only use
Yeah, now is perfect time to tell if there is any need for something
else than audio.
OMAP1xxx/59xx and 2420 are already something like more
than 5 years old obsolete components and we haven't seen that any of
them would need SPI/clock stop functionality. Actually we haven't seen
any other use for McBSP than audio.
> - Only OMAP3 has sidetone (on OMAP2 EAC block has the sidetone), might need
> some change, but I think the current way can be reused.
>
Yeah, they probably need work on kernel side (hwmod stuff etc) but I
think for keeping userspace intact over the cleanup we might want to
keep these special sysfs nodes for sidetone filter coefficients, dma
operating mode and FIFO threshold as it over the cleanup.
--
Jarkko
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-06-14 12:04 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
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 [this message]
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=20110614150530.87e594a5.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=kishon@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=tony@atomide.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).