From: w.sang@pengutronix.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: mx28: check for gated clocks when setting saif divider
Date: Thu, 17 Nov 2011 10:29:46 +0100 [thread overview]
Message-ID: <20111117092946.GA2535@pengutronix.de> (raw)
In-Reply-To: <20111117011833.GD14656@S2100-06.ap.freescale.net>
> > I chose this approach because this is the common pattern
> > in all other clocks. There might be a better way of handling this, but
> > then we'd need to adapt all other clocks as well. What we definately
> > should not have is one kind of handling the 'already enabled' case for a
> > few clocks and another kind for others.
> >
> What about leaving it as it is for now, and try to consolidate when
> we rework the code for common clock framework migration?
In general, very fine with me. I seem to recall saif-drivers will need a
hack then, but Aisheng surely knows better.
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20111117/454a0c31/attachment.sig>
next prev parent reply other threads:[~2011-11-17 9:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-10 10:29 [PATCH] arm: mx28: check for gated clocks when setting saif divider Wolfram Sang
2011-11-16 13:22 ` Wolfram Sang
2011-11-16 13:35 ` Dong Aisheng-B29396
2011-11-16 13:51 ` Wolfram Sang
2011-11-16 14:23 ` Dong Aisheng-B29396
2011-11-17 1:18 ` Shawn Guo
2011-11-17 9:29 ` Wolfram Sang [this message]
2011-11-17 9:42 ` Dong Aisheng-B29396
2012-01-19 3:24 ` Shawn Guo
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=20111117092946.GA2535@pengutronix.de \
--to=w.sang@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).