From: Takashi Iwai <tiwai@suse.de>
To: niraj kulkarni <kulkarniniraj14@gmail.com>
Cc: alsa-devel@alsa-project.org,
David Henningsson <david.henningsson@canonical.com>
Subject: Re: Fw: [Bug 1155202] [Intel DZ77SL-50K, Intel PantherPoint HDMI, Digital Out, HDMI] No sound at all
Date: Mon, 10 Feb 2014 18:27:09 +0100 [thread overview]
Message-ID: <s5hzjly98uq.wl%tiwai@suse.de> (raw)
In-Reply-To: <CACWODjR3HFTFh5iGGS0WZapL7d+kSqiYf=O7QsQu=7dAqQ7TLA@mail.gmail.com>
At Mon, 10 Feb 2014 17:10:16 +0530,
niraj kulkarni wrote:
>
> Sorry, I did not see that part earlier. Putting udelay(2) is also working
> fine.
OK, thanks for testing. I'm going to test the patch with other
machines and then merge to the upstream.
Takashi
>
> Niraj
>
>
> On Mon, Feb 10, 2014 at 2:31 PM, Takashi Iwai <tiwai@suse.de> wrote:
>
> > At Mon, 10 Feb 2014 11:35:41 +0530,
> > niraj kulkarni wrote:
> > >
> > > Removing these 3 usleep ranges is working now. Although I have a doubt
> > for
> > > applying this patch on all chips. There have been a number of boards
> > > released after this particular board, but nobody else is facing this
> > > problem. Since spec does not specify a max on deasserting RST, some
> > boards
> > > might actually take more than 100uS to reset. Will this patch work for
> > > those boards?
> > >
> > > @@ -1149,7 +1149,7 @@
> > > timeout = jiffies + msecs_to_jiffies(100);
> > > while ((azx_readb(chip, GCTL) & ICH6_GCTL_RESET) &&
> > > time_before(jiffies, timeout))
> > > - usleep_range(500, 1000);
> > > + cpu_relax();
> > > }
> > >
> > > /* exit link reset */
> > > @@ -1162,7 +1162,7 @@
> > > timeout = jiffies + msecs_to_jiffies(100);
> > > while (!azx_readb(chip, GCTL) &&
> > > time_before(jiffies, timeout))
> > > - usleep_range(500, 1000);
> > > + cpu_relax();
> > > }
> > >
> > > /* reset codec link */
> > > @@ -1180,7 +1180,7 @@
> > > /* delay for >= 100us for codec PLL to settle per spec
> > > * Rev 0.9 section 5.5.1
> > > */
> > > - usleep_range(500, 1000);
> > > + //usleep_range(500, 1000);
> >
> > Why didn't you change as I suggested? In my patch, I placed udelay(2)
> > since the spec tells so. Didn't it interfere?
> >
> > Replacing usleep_range() with cpu_relax() should make still working on
> > other boards because it doesn't change the length of the timeout
> > itself. The timeout is set to very long (100ms). The only drawback
> > would be a higher CPU usage at probing, but the impact should be
> > negligible.
> >
> >
> > Takashi
> >
> [2 <text/html; ISO-8859-1 (quoted-printable)>]
>
next prev parent reply other threads:[~2014-02-10 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52ef1e8f.a4c3440a.53f1.fffff564SMTPIN_ADDED_BROKEN@mx.google.com>
2014-02-10 6:05 ` Fw: [Bug 1155202] [Intel DZ77SL-50K, Intel PantherPoint HDMI, Digital Out, HDMI] No sound at all niraj kulkarni
2014-02-10 9:01 ` Takashi Iwai
2014-02-10 11:40 ` niraj kulkarni
2014-02-10 17:27 ` Takashi Iwai [this message]
2014-01-22 14:20 [alsa-devel] " Niraj Kulkarni
2014-01-24 13:11 ` Takashi Iwai
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=s5hzjly98uq.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--cc=kulkarniniraj14@gmail.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