From: "Uwe Kleine-König" <uwe@kleine-koenig.org>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: Antti Palosaari <crope@iki.fi>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org
Subject: Re: [PATCH 1/3] si2157: get chip id during probing
Date: Mon, 8 Jul 2019 10:43:08 +0200 [thread overview]
Message-ID: <545607da-accf-06c5-f5ae-43d28781f554@kleine-koenig.org> (raw)
In-Reply-To: <3ff87deb-9125-4696-8aa0-141ea7d773b9@kleine-koenig.org>
[-- Attachment #1.1: Type: text/plain, Size: 922 bytes --]
Hello Andreas,
On 7/7/19 11:01 PM, Uwe Kleine-König wrote:
> Hello,
>
> On 7/7/19 10:58 PM, Uwe Kleine-König wrote:
>> From: Andreas Kemnade <andreas@kemnade.info>
>>
>> If the si2157 is behind a e.g. si2168, the si2157 will
>> at least in some situations not be readable after the si268
>> got the command 0101. It still accepts commands but the answer
>> is just ffffff. So read the chip id before that so the
>> information is not lost.
>>
>> The following line in kernel output is a symptome
>> of that problem:
>> si2157 7-0063: unknown chip version Si21255-\xffffffff\xffffffff\xffffffff
>>
>> Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
I wonder if you (or anyone else here reading this mail) has access to
the datasheets of the involved chips? (i.e. si2168, si2157)
I'd like to try understanding and eventually fix the addressed problem
here properly.
Best regards
Uwe
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-07-08 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-07 20:58 [PATCH 1/3] si2157: get chip id during probing Uwe Kleine-König
2019-07-07 21:01 ` Uwe Kleine-König
2019-07-08 8:43 ` Uwe Kleine-König [this message]
[not found] ` <20190709200329.7a47f453@kemnade.info>
2019-07-09 19:26 ` Uwe Kleine-König
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=545607da-accf-06c5-f5ae-43d28781f554@kleine-koenig.org \
--to=uwe@kleine-koenig.org \
--cc=andreas@kemnade.info \
--cc=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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;
as well as URLs for NNTP newsgroup(s).