From: "Unembossed Name" <severe.siberian.man@mail.ru>
To: <linux-media@vger.kernel.org>,
"Devin Heitmueller" <dheitmueller@kernellabs.com>
Subject: XC5000C 0x14b4 status
Date: Fri, 26 Jun 2015 03:58:48 +0700 [thread overview]
Message-ID: <DB7ACFD5239247FCB3C1CA323B56E88D@unknown> (raw)
Hi,
I was working on a Linux driver for a hybrid TV-tuner with SAA7134 PCI bridge, XC5000C RF tuner and Si2168 DVB demodulator by a
"combining" all existent at that time drivers together.
During that work, I had an issue with XC5000C.
Episodically, after attaching to DVB and reading XREG_PRODUCT_ID register, it
was possible to receive 0x14b4 instead of usual 0x1388 status. And as a result get a "xc5000: Device not found at addr 0x%02x
(0x%x)\n" in dmesg.
To workaround these, I added a few strings to a source of a driver to make it's behaviour the same for 0x14b4, as for 0x1388.
After that RF tuner identification became always successful.
I had a conversation with a hardware vendor.
Now I can say, that such behaviour, most likely, because of "early" firmware for XC5000C.
This hardware vendor is using for his Windows driver a latest firmware, and reading Product ID register always gives 0x14b4 status.
As he says, 0x1388 status is only for previous XC5000 IC. (Without C at end of a P/N)
Is this possible to patch xc5000.c with something like this:
#define XC_PRODUCT_ID_FW_LOADED 0x1388
+#define XC_PRODUCT_ID_FW_LOADED_XC5000C 0x14b4
case XC_PRODUCT_ID_FW_LOADED:
+ case XC_PRODUCT_ID_FW_LOADED_XC5000C:
printk(KERN_INFO
"xc5000: Successfully identified at address 0x%02x\n",
Or to try to get a chip vendor's permission for using a latest firmware for XC5000C in Linux, and then anyway, patch the driver?
Best regards.
next reply other threads:[~2015-06-25 21:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 20:58 Unembossed Name [this message]
2015-06-26 9:22 ` XC5000C 0x14b4 status Mauro Carvalho Chehab
2015-06-26 10:59 ` Unembossed Name
2015-06-26 11:04 ` Devin Heitmueller
2015-06-26 11:21 ` Steven Toth
2015-06-26 12:19 ` Unembossed Name
2015-06-26 14:15 ` Steven Toth
2015-06-26 14:59 ` Unembossed Name
2015-06-26 11:51 ` Unembossed Name
2015-06-26 11:00 ` Devin Heitmueller
2015-06-26 11:39 ` Unembossed Name
2015-06-29 22:55 ` Unembossed Name
2015-06-30 0:42 ` Unembossed Name
2015-07-01 21:41 ` Unembossed Name
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=DB7ACFD5239247FCB3C1CA323B56E88D@unknown \
--to=severe.siberian.man@mail.ru \
--cc=dheitmueller@kernellabs.com \
--cc=linux-media@vger.kernel.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