All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: gabriel@unseen.is, linux-samsung-soc@vger.kernel.org,
	dmaengine@vger.kernel.org, sylvester.nawrocki@gmail.com,
	Robert Baldyga <r.baldyga@samsung.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: exynos4412: Audio dies after one day on kernel 4.0
Date: Fri, 12 Jun 2015 18:36:24 +0530	[thread overview]
Message-ID: <20150612130624.GL28601@localhost> (raw)
In-Reply-To: <CAJKOXPeehj++Ojt2Zo4sgNjVASzZ8r_6OROM6FK_BRRQqVzcGg@mail.gmail.com>

On Wed, Jun 10, 2015 at 05:22:07PM +0900, Krzysztof Kozlowski wrote:

> > I can now say for sure that the commits 88987d2c75 and aee4d1fac8 are
> > the cause for the problem. Audio was working now for 7 days.
> 
> +CC Vinod
> 
> Gabriel,
> 
> I sent a patch which should fix the issue. Could you give it a try? Of
> course don't revert the other patches and don't use other workarounds.
> Just apply the patch on clean (vanilla would be the best) kernel.
> [RFT PATCH] dmaengine: Fix choppy sound because of unimplemented resume
I have already applied this one, can you check the -next and see if this
issue is seen

-- 
~Vinod

  reply	other threads:[~2015-06-12 13:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-30 17:32 exynos4412: Audio dies after one day on kernel 4.0 gabriel
2015-05-31  6:47 ` Krzysztof Kozlowski
2015-06-02 19:51   ` gabriel
2015-06-03  0:05     ` Krzysztof Kozlowski
2015-06-09 11:25       ` gabriel
2015-06-10  8:22         ` Krzysztof Kozlowski
2015-06-12 13:06           ` Vinod Koul [this message]
2015-06-12 21:48           ` gabriel
2015-06-13  5:47             ` Krzysztof Kozlowski
2015-06-13  8:15               ` Krzysztof Kozlowski
     [not found]                 ` <CANAwSgQKFTG+ts=kVrZ1fR1EBcZL+7dgXqH1WhoJ7kZzz8hS3Q@mail.gmail.com>
2015-06-22 23:57                   ` Krzysztof Kozlowski
2015-06-23  2:35                     ` Anand Moon

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=20150612130624.GL28601@localhost \
    --to=vinod.koul@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=gabriel@unseen.is \
    --cc=k.kozlowski@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=r.baldyga@samsung.com \
    --cc=sylvester.nawrocki@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 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.