linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mpa@pengutronix.de (Markus Pargmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: clk: imx35 sound admux_gate bugfix
Date: Wed, 27 Mar 2013 17:37:28 +0100	[thread overview]
Message-ID: <20130327163728.GE6347@pengutronix.de> (raw)
In-Reply-To: <20130327155011.GY18316@opensource.wolfsonmicro.com>

On Wed, Mar 27, 2013 at 03:50:11PM +0000, Mark Brown wrote:
> On Wed, Mar 27, 2013 at 04:04:20PM +0100, Markus Pargmann wrote:
> > On Wed, Mar 27, 2013 at 12:37:00PM +0000, Mark Brown wrote:
> 
> > > This is a patch to the ASoC driver?  I just ignored it since it said it
> > > was an ARM patch...  Anyway, what I'd expect should be happening here is
> > > that the clock API walks up the tree enabling supply clocks - that would
> > > mean that either that code isn't there or there's a missing parent child
> > > relationship in the data.
> 
> > It changes some things in imx-ssi, sorry, perhaps I should have
> > splitted it into two patches.
> 
> > admux clock does not seem to be a physical parent of the ssi clock, so
> > I don't think it should be a parent in the clock tree. But imx-ssi (or
> > some other evice) needs this clock to work. As mentioned in the other
> > response, I will put it directly into clk-imx35.c so this won't be a
> > patch for ASoC in the next version.
> 
> If it's the IP that needs the clock then I'd expect the IP to be
> requesting it so changing the driver does make sense.  Do we actually
> know what the clock does?

No we don't know exactly. imx35 reference manual does not give any
further explanation about admux. But I just found this old patch:
http://lists.infradead.org/pipermail/linux-arm-kernel/2009-November/003843.html

So I tested to register admux as audmux clock for imx-audmux, which
seems to solve the problem. However, I am not sure why the old patch
of Sascha was not applied.

Regards,

Markus

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

      reply	other threads:[~2013-03-27 16:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 11:22 [PATCH 0/2] ARM: imx35 clk bugfixes Markus Pargmann
2013-03-27 11:22 ` [PATCH 1/2] ARM: clk: Bugfix imx35 iomux clock Markus Pargmann
2013-03-27 11:22 ` [PATCH 2/2] ARM: clk: imx35 sound admux_gate bugfix Markus Pargmann
2013-03-27 11:57   ` Philipp Zabel
2013-03-27 12:14     ` Markus Pargmann
2013-03-27 12:37     ` Mark Brown
2013-03-27 15:04       ` Markus Pargmann
2013-03-27 15:50         ` Mark Brown
2013-03-27 16:37           ` Markus Pargmann [this message]

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=20130327163728.GE6347@pengutronix.de \
    --to=mpa@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).