public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Knut Petersen <Knut_Petersen@t-online.de>
To: Hans Verkuil <hansverk@cisco.com>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [REGRESSION 3.11-rc] wm8775 9-001b: I2C: cannot write ??? to register R??
Date: Tue, 27 Aug 2013 11:35:59 +0200	[thread overview]
Message-ID: <521C72FF.5070902@t-online.de> (raw)
In-Reply-To: <521C5493.1050407@cisco.com>

On 27.08.2013 09:26, Hans Verkuil wrote:
> On 08/25/2013 05:45 PM, Knut Petersen wrote:
>> Booting current git kernel dmesg shows a set of new  warnings:
>>
>>      "wm8775 9-001b: I2C: cannot write ??? to register R??"
>>
>> Nevertheless, the hardware seems to work fine.
>>
>> This is a new problem, introduced after kernel 3.10.
>> If necessary I can bisect.
> Can you try this patch? I'm pretty sure this will fix it.

Indeed, it does cure the problem. Thanks.

Tested-by: Knut Petersen <Knut_Petersen@t-online.de>


>
> Regards,
>
> 	Hans
>
> diff --git a/drivers/media/pci/cx88/cx88.h b/drivers/media/pci/cx88/cx88.h
> index afe0eae..28893a6 100644
> --- a/drivers/media/pci/cx88/cx88.h
> +++ b/drivers/media/pci/cx88/cx88.h
> @@ -259,7 +259,7 @@ struct cx88_input {
>   };
>   
>   enum cx88_audio_chip {
> -	CX88_AUDIO_WM8775,
> +	CX88_AUDIO_WM8775 = 1,
>   	CX88_AUDIO_TVAUDIO,
>   };
>   
>
>


  reply	other threads:[~2013-08-27  9:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-25 15:45 [REGRESSION 3.11-rc] wm8775 9-001b: I2C: cannot write ??? to register R?? Knut Petersen
2013-08-27  7:26 ` Hans Verkuil
2013-08-27  9:35   ` Knut Petersen [this message]
2013-08-27  9:51     ` Hans Verkuil
2013-08-28  5:34       ` Knut Petersen
2013-08-31  8:00     ` [REGRESSION 3.11-rc1+] " Knut Petersen
2013-08-31 16:51       ` Linus Torvalds

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=521C72FF.5070902@t-online.de \
    --to=knut_petersen@t-online.de \
    --cc=hansverk@cisco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@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