From: friesendrywall@gmail.com (Erik Friesen)
To: linux-arm-kernel@lists.infradead.org
Subject: SGTL5000 misc
Date: Wed, 3 Feb 2016 10:11:39 -0500 [thread overview]
Message-ID: <CAEuupivdftoopCOX3f7KRbV9poKdjdD3s9hfcbgB2TYjHmrjvw@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5C4QUHnJr=pisnYWCYZ0zUt+7HO846aPQui0zcLyX0N-Q@mail.gmail.com>
There is no difference in code that I can tell between the two. I am
not asking to have this fixed, rather just some ideas on how I can
implement this. If alsa-devel list is the preferred asking place, I'll
go there.
The riotboard used kernel 4.3.0-rc2-00019-gbcee19f with the same results.
On Wed, Feb 3, 2016 at 9:51 AM, Fabio Estevam <festevam@gmail.com> wrote:
> On Wed, Feb 3, 2016 at 12:46 PM, Erik Friesen <friesendrywall@gmail.com> wrote:
>> It appears sgtl5000.c is patched the same in my kernel as the commit mentioned.
>>
>> The problem the way I see it, is that there is no mechanism to deal
>> with a reboot on the codec itself.
>
> There is no reset line nor reset command on the sgtl5000.
>
>> This alsa stuff has too many layers. At least coming from a non os
>> embedded angle it seems that way.
>
> I would suggest you to try 4.4.1 and if you still see an issue with
> the codec, then report it back to the alsa-devel at alsa-project.org
> list.
next prev parent reply other threads:[~2016-02-03 15:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 13:42 SGTL5000 misc Erik Friesen
2016-02-03 14:23 ` Fabio Estevam
2016-02-03 14:33 ` Erik Friesen
2016-02-03 14:38 ` Fabio Estevam
2016-02-03 14:46 ` Erik Friesen
2016-02-03 14:51 ` Fabio Estevam
2016-02-03 15:11 ` Erik Friesen [this message]
2016-02-03 22:05 ` Erik Friesen
2016-02-03 22:20 ` Fabio Estevam
2016-02-05 3:08 ` Erik Friesen
2016-02-05 10:00 ` Fabio Estevam
2016-02-06 17:22 ` Erik Friesen
2016-02-06 17:33 ` Fabio Estevam
2016-02-06 19:29 ` Erik Friesen
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=CAEuupivdftoopCOX3f7KRbV9poKdjdD3s9hfcbgB2TYjHmrjvw@mail.gmail.com \
--to=friesendrywall@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.