From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: <tony@atomide.com>, <jarkko.nikula@bitmer.com>, <paul@pwsan.com>
Cc: <t-kristo@ti.com>, <linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: [PATCH v2 0/3] ARM: OMAP3: Fix McBSP2/3 hwmod setup for sidetone
Date: Fri, 18 Mar 2016 16:23:24 +0200 [thread overview]
Message-ID: <1458311007-19168-1-git-send-email-peter.ujfalusi@ti.com> (raw)
Hi,
Chanes since v1:
- removed the ASoC patch as Mark has applied it already
- Added my signed-off to the hwmod patch
- New patch to handle the case when the sidetone hwmod has been removed for
legacy boot.
The series addresses a long standing issue with McBSP2/3 regarding to hwmod
setup. When booting with DT a warning is printed that mcbsp2/3 is using two
hwmod.
The root of the issue is the way how the hwmod data was constructed in the first
place for OMAP3 McBSP2/3.
After re-reading the TRM it is clear that the sidetone should not have it's
own hwmod data as it is not a separate IP, it is part of the McBSP module. It
can not affect PRCM either since it's SYSCONFIG register's AUTOIDLE bit is only
sets the autoidle from the internal McBSP_iclk clock to the sidetone block of
the same McBSP.
Regards,
Peter
---
Peter Ujfalusi (3):
ARM: DTS: omap3: Remove mcbsp2/3_sidetone hwmod reference for McBSP2/3
ARM: OMAP2+: mcbsp: Prepare the device build code for sidetone hwmod
removal
ARM: OMAP3: hwmod data: Merge and remove the McBSP sidetone related
data
arch/arm/boot/dts/omap3.dtsi | 4 +-
arch/arm/mach-omap2/mcbsp.c | 28 ++++++-
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 120 ++++-------------------------
3 files changed, 43 insertions(+), 109 deletions(-)
--
2.7.3
next reply other threads:[~2016-03-18 14:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 14:23 Peter Ujfalusi [this message]
2016-03-18 14:23 ` [PATCH v2 1/3] ARM: DTS: omap3: Remove mcbsp2/3_sidetone hwmod reference for McBSP2/3 Peter Ujfalusi
2016-03-18 14:23 ` [PATCH v2 2/3] ARM: OMAP2+: mcbsp: Prepare the device build code for sidetone hwmod removal Peter Ujfalusi
2016-03-18 14:23 ` [PATCH v2 3/3] ARM: OMAP3: hwmod data: Merge and remove the McBSP sidetone related data Peter Ujfalusi
2016-03-19 19:38 ` [PATCH v2 0/3] ARM: OMAP3: Fix McBSP2/3 hwmod setup for sidetone Paul Walmsley
2016-03-21 8:57 ` Peter Ujfalusi
2016-03-21 17:44 ` Paul Walmsley
2016-04-01 9:33 ` Peter Ujfalusi
2016-04-02 0:17 ` Tony Lindgren
2016-04-04 12:45 ` Peter Ujfalusi
2016-04-04 15:12 ` Tony Lindgren
2016-04-05 13:15 ` Peter Ujfalusi
2016-04-11 21:28 ` Tony Lindgren
2016-04-12 9:52 ` Peter Ujfalusi
2016-04-12 16:37 ` Tony Lindgren
2016-04-13 11:57 ` Peter Ujfalusi
2016-04-13 15:28 ` Tony Lindgren
2016-04-14 7:34 ` Peter Ujfalusi
2016-04-14 16:55 ` Tony Lindgren
2016-04-14 19:37 ` Peter Ujfalusi
2016-04-14 20:34 ` Tony Lindgren
2016-04-15 10:23 ` Peter Ujfalusi
2016-04-15 15:16 ` Tony Lindgren
2016-04-15 19:50 ` Peter Ujfalusi
2016-04-18 23:51 ` Tony Lindgren
2016-04-22 13:12 ` Peter Ujfalusi
2016-04-22 22:24 ` 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=1458311007-19168-1-git-send-email-peter.ujfalusi@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jarkko.nikula@bitmer.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=t-kristo@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
all inboxes | Powered by JetHome®