Re: Kernel 5.2.8 - au0828 - Tuner Is Busy

From: shuah
Date: Mon Aug 19 2019 - 17:44:13 EST

On 8/19/19 2:49 PM, shuah wrote:
On 8/16/19 7:15 PM, Nathan Royce wrote:
On Fri, Aug 16, 2019 at 1:42 PM Greg Kroah-Hartman
<gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
If you revert that one commit, does things start working again?


greg k-h
Hey Greg, I just got finished building it after running "$ git revert
812658d88d26" and verifying it reverted by comparing one of the files
from git log -p, but alas, no joy.

On Fri, Aug 16, 2019 at 5:41 PM Brad Love <brad@xxxxxxxxxxxxxxxx> wrote:

Hi Nathan,

I don't have a "woodbury", but I have a Hauppauge 950Q sitting around
and tested it on latest mainline kernel. w_scan is ok and streaming is
fine. There's no unexpected errors. The 950Q uses the same au0828 bridge
and au8522 demod as woodbury, but a different tuner. Your problem
wouldn't appear to be a general au0828 issue.

Thanks Brad!

You might have to check out git bisect. That will be the quickest way to
get to the bottom, if you've got points A and B, and are
building/running your own kernel.


Thanks Brad, I'll explore bisecting and hopefully will be able to
narrow down the cause.
I wasn't running my own kernel, but rather using the Arch Linux kernel
and modding the one module and putting it in "extramodules".

Hi Nathan,

Just catching up with this thread. Let me know what you find. Can you
build your own kernel and see what you can find?

You said you make changes to the

"Whenever I update my kernel, I edit the
./drivers/media/usb/au0828/au0828-cards.c file adding an entry for my
0x400 device.
I've been doing it for years and it's been working fine... until now..."

Please send me the changes you make to the file. I see the following
WOODBURY devices. I am assuming you add 0x400 entry.

{ USB_DEVICE(0x05e1, 0x0480),
.driver_info = AU0828_BOARD_HAUPPAUGE_WOODBURY },
{ USB_DEVICE(0x2040, 0x8200),
.driver_info = AU0828_BOARD_HAUPPAUGE_WOODBURY },

There is another table in sound/usb/quirks-table.h for AU0828
devices. In addition to 812658d88d26, 66354f18fe5f makes change
to this table to add a flag. I see two entries in that table:

AU0828_DEVICE(0x05e1, 0x0480, "Hauppauge", "Woodbury"),
AU0828_DEVICE(0x2040, 0x8200, "Hauppauge", "Woodbury"),

Since these drivers are now coupled doing resource sharing,
could it be that with your change to au02828 device table,
your changes are bow incomplete.

I don't have a Woodbury device though. This is something to

Did you consider sending patch to add your device variant,
so you don't have to keep making this change whenever you
go to a new kernel?

-- Shuah