From: The Bit Pit <thebitpit@earthlink.net>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: Devin Heitmueller <dheitmueller@kernellabs.com>
Subject: Re: Driver for KWorld UB435Q Version 3 (ATSC) USB id: 1b80:e34c
Date: Mon, 06 May 2013 15:16:57 -0500 [thread overview]
Message-ID: <51880FB9.7000006@earthlink.net> (raw)
In-Reply-To: <CAGoCfiy5qWrqH1ptGc4LKvbN1w-TtsV+ogCr7qWX6zn9L=MaSQ@mail.gmail.com>
On 05/03/2013 04:29 PM, Devin Heitmueller wrote:
> The lgdt3305 is probably on the second i2c bus -- typical for em2874
> based devices. The tuner is probably gated behind the 3305. It's also
> likely that the 3305 is being held in reset by default. You'll
> probably need to tweak a GPIO to take it out of reset before it will
> answer i2c.
Thanks, I found it on the second i2c bus. I tweaked the GPIO to get is
going. It attached OK.
> One is probably the eeprom.
Right! It is the eeprom at 0x50 on bus 0. After I figured out how to
access bus 1, it reports:
[39839.472893] em2874 #0: found i2c device @ 0xc0 on bus 1 [tuner (analog)]
This I assume is the tda18272.
The next challenge is a driver for the tuner tda18272. There is a
driver for tda18271. The 10 page product data sheet block diagrams are
different for the tda18271 and tda18272.
I tried to attach the tda18272 as a tda18271 and got:
[39839.510613] tda18271 10-0060: creating new instance
[39839.510615]435 em2874 #0 at em28xx_i2c_xfer: write nonstop addr=c0
len=1: 00
[39839.510992] em2874 #0 at em28xx_i2c_xfer: read stop addr=c0 len=16:
c7 60 11 52 00 02 0c 00 20 80 00 00 c9 0f 3f 35
[39839.512636] Unknown device (199) detected @ 10-0060, device not
supported.
[39839.512640] tda18271_attach: [10-0060|M] error -22 on line 1285
[39839.512642] tda18271 10-0060: destroying instance
There are a few references to 18272 in usb/dvb-usb-v2/rtl28xxu.c - All
I could see is code to detect the tda18272. I don't understand this code
yet.
If they are similar enough maybe 18271 driver could be modified to
handle the 18272.
Can anyone send me register specs for the tda18272 and tda18271 so I can
figure out how they could be merged. Better yet, maybe someone has
already done this.
Thank you,
Wilson Michaels
next prev parent reply other threads:[~2013-05-06 20:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 19:50 Driver for KWorld UB435Q Version 3 (ATSC) USB id: 1b80:e34c The Bit Pit
2013-05-03 21:29 ` Devin Heitmueller
2013-05-06 20:16 ` The Bit Pit [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-07 18:23 The Bit Pit
2014-02-07 18:39 ` Steven Toth
2014-02-07 20:17 ` The Bit Pit
2014-02-07 20:51 ` Steven Toth
2014-02-07 20:24 ` Manu Abraham
2014-02-07 20:48 ` Steven Toth
2014-03-03 19:46 ` Mauro Carvalho Chehab
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=51880FB9.7000006@earthlink.net \
--to=thebitpit@earthlink.net \
--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