From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: mx28: Fix sgtl5000 codec probe
Date: Sat, 22 Jun 2013 15:24:33 +0200 [thread overview]
Message-ID: <201306221524.33879.marex@denx.de> (raw)
In-Reply-To: <CAOMZO5DUsGpffGOkEjZX3JaKcJxV6GsH_pOyX=dhHxq3vB9xQA@mail.gmail.com>
Dear Fabio Estevam,
> On Sat, Jun 22, 2013 at 12:47 AM, Fabio Estevam <festevam@gmail.com> wrote:
> > On Fri, Jun 21, 2013 at 11:31 PM, Marek Vasut <marex@denx.de> wrote:
> >> Should the SAIF block reset not happen in the driver?
> >
> > We need to clear SFTRST and CLKGATE here in order to get MCLK output.
>
> Just to clarify: the sgtl500 i2c probe happens prior to the mxs saif
> probe, so that's why we can't wait for the mxs-saif to turn on the
> clocks.
Yuck, I see. This is really ugly :(
Just an idea here, can we not maybe defer the SGTL5000 I2C probe?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-06-22 13:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 21:21 [PATCH 1/2] clk: mxs: clk-imx28: Provide a dummy clock Fabio Estevam
2013-06-21 21:22 ` [PATCH 2/2] ARM: dts: mx28: Fix sgtl5000 codec probe Fabio Estevam
2013-06-22 2:31 ` Marek Vasut
2013-06-22 3:47 ` Fabio Estevam
2013-06-22 3:54 ` Fabio Estevam
2013-06-22 13:24 ` Marek Vasut [this message]
2013-06-22 14:04 ` Fabio Estevam
2013-06-24 7:29 ` Shawn Guo
2013-06-24 13:54 ` Fabio Estevam
2013-06-24 14:07 ` Shawn Guo
2013-06-24 14:18 ` Fabio Estevam
2013-06-24 14:47 ` Shawn Guo
2013-06-25 8:12 ` Shawn Guo
2013-06-25 10:28 ` Fabio Estevam
2013-06-25 12:19 ` Shawn Guo
2013-06-25 12:22 ` Fabio Estevam
2013-06-25 12:52 ` Shawn Guo
2013-06-25 13:04 ` 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=201306221524.33879.marex@denx.de \
--to=marex@denx.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).