From: Icenowy Zheng <icenowy@aosc.io>
To: "Enric Balletbo i Serra" <enric.balletbo@collabora.com>,
"Ond�0�0ej Jirman" <megous@megous.com>,
"Vasily Khoruzhick" <anarsoul@gmail.com>,
"Enric Balletbo Serra" <eballetbo@gmail.com>,
"Jernej Skrabec" <jernej.skrabec@siol.net>,
"Nicolas Boichat" <drinkcat@chromium.org>,
"Laurent Pinchart" <Laurent.pinchart@ideasonboard.com>,
"Neil Armstrong" <narmstrong@baylibre.com>,
"David Airlie" <airlied@linux.ie>, "Torsten Duwe" <duwe@suse.de>,
"Jonas Karlman" <jonas@kwiboo.se>,
linux-kernel <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
"Andrzej Hajda" <a.hajda@samsung.com>,
"Maxime Ripard" <maxime@cerno.tech>,
"Hsin-Yi Wang" <hsinyi@chromium.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Collabora Kernel ML" <kernel@collabora.com>
Subject: Re: [PATCH v2 2/2] drm/bridge: anx7688: Add anx7688 bridge driver support
Date: Fri, 06 Mar 2020 16:53:46 +0800 [thread overview]
Message-ID: <5d72a8c6824b31163a303b5ef1526efe05121e5d.camel@aosc.io> (raw)
In-Reply-To: <2a5a4a62-3189-e053-21db-983a4c766d44@collabora.com>
在 2020-03-06星期五的 09:46 +0100,Enric Balletbo i Serra写道:
> Hi Ondrej,
>
> On 5/3/20 20:35, Ondřej Jirman wrote:
> > Hi,
> >
> > On Thu, Mar 05, 2020 at 10:29:33AM -0800, Vasily Khoruzhick wrote:
> > > On Thu, Mar 5, 2020 at 7:28 AM Enric Balletbo i Serra
> > > <enric.balletbo@collabora.com> wrote:
> > > > Hi Vasily,
> > >
> > > CC: Icenowy and Ondrej
> > > > Would you mind to check which firmware version is running the
> > > > anx7688 in
> > > > PinePhone, I think should be easy to check with i2c-tools.
> > >
> > > Icenowy, Ondrej, can you guys please check anx7688 firmware
> > > version?
> >
> > i2cget 0 0x28 0x00 w
> > 0xaaaa
> >
> > i2cget 0 0x28 0x02 w
> > 0x7688
> >
> > i2cget 0 0x28 0x80 w
> > 0x0000
> >
>
> Can you check the value for 0x81 too?
root@ice-pinephone [ ~ ] # i2cdump 0 0x28
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and
worse!
I will probe file /dev/i2c-0, address 0x28, mode byte
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: aa aa 88 76 ac 00 00 00 00 00 00 00 00 00 05 05 ???v?.........??
10: 30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0...............
20: 00 00 00 00 00 00 00 00 00 00 00 24 f2 e4 ff 00 ...........$??..
30: 06 40 00 04 94 11 20 ff ff 03 00 bf ff ff 10 01 ?@.??? ..?.?..??
40: 72 a4 00 09 00 08 05 84 15 40 17 00 00 0a 00 e0 r?.?.????@?..?.?
50: 00 00 00 0a 10 00 e0 df ff ff 00 00 00 10 71 00 ...??.??.....?q.
60: 10 10 04 29 2d 21 10 01 09 13 00 03 e8 13 88 00 ???)-!????.????.
70: 00 19 18 83 16 5c 11 00 ff 00 00 0d 04 38 42 07 .????\?....??8B?
80: 00 00 00 00 00 74 1b 19 44 08 75 00 00 00 00 00 .....t??D?u.....
90: 01 02 00 00 00 00 03 00 ff 30 00 59 01 00 00 00 ??....?..0.Y?...
a0: 00 ff fe ff ff 00 00 00 00 00 00 00 00 00 00 02 ..?............?
b0: 00 00 00 00 00 00 40 00 28 00 00 00 00 44 08 00 ......@.(....D?.
c0: 00 00 00 00 80 00 10 01 0a 10 18 00 00 fd 00 00 ....?.?????..?..
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
e0: 50 10 08 50 00 02 00 70 00 00 30 10 0b 02 1c 01 P??P.?.p..0?????
f0: 00 0b 07 00 94 11 7f 00 00 00 00 00 00 01 0e ff .??.???......??.
root@ice-pinephone [ ~ ] # i2cdump 0 0x2c
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and
worse!
I will probe file /dev/i2c-0, address 0x2c, mode byte
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 29 1f 88 76 00 ac 11 00 11 20 10 10 00 00 00 00 )??v.??.? ??....
10: 03 00 ff 8f ff 7f 00 00 00 00 05 00 10 0a 0c 00 ?..?.?....?.???.
20: 00 00 00 00 99 06 c0 00 00 00 00 00 00 00 02 00 ....???.......?.
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
40: 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ?...............
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
70: b8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ?...............
80: 01 25 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ?%..............
90: 0f 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ??..............
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>
> Thanks,
> Enric
>
>
> > regards,
> > o.
> >
> > > > Thanks in advance,
> > > > Enric
> > > >
> > > > [snip]
next prev parent reply other threads:[~2020-03-06 8:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 14:54 [PATCH v2 1/2] Documentation: bindings: Add ANX7688 HDMI to DP bridge binding Enric Balletbo i Serra
2020-02-13 14:54 ` [PATCH v2 2/2] drm/bridge: anx7688: Add anx7688 bridge driver support Enric Balletbo i Serra
2020-02-14 12:18 ` Andrzej Hajda
2020-02-14 13:29 ` Nicolas Boichat
2020-02-15 0:36 ` Nicolas Boichat
2020-02-14 21:36 ` Vasily Khoruzhick
2020-02-14 21:53 ` Enric Balletbo Serra
2020-02-14 22:17 ` Vasily Khoruzhick
2020-02-14 22:20 ` Enric Balletbo Serra
2020-02-14 22:22 ` Vasily Khoruzhick
2020-03-05 15:28 ` Enric Balletbo i Serra
2020-03-05 18:29 ` Vasily Khoruzhick
2020-03-05 18:35 ` Icenowy Zheng
2020-03-06 8:46 ` Enric Balletbo i Serra
2020-03-05 19:35 ` Ondřej Jirman
2020-03-06 8:46 ` Enric Balletbo i Serra
2020-03-06 8:53 ` Icenowy Zheng [this message]
2020-03-06 12:07 ` Ondřej Jirman
2020-03-06 12:11 ` Nicolas Boichat
2020-03-06 12:46 ` Ondřej Jirman
2020-03-06 12:03 ` Ondřej Jirman
2020-03-06 12:18 ` Enric Balletbo i Serra
2020-02-15 0:57 ` Nicolas Boichat
2020-02-19 15:30 ` [PATCH v2 1/2] Documentation: bindings: Add ANX7688 HDMI to DP bridge binding Rob Herring
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=5d72a8c6824b31163a303b5ef1526efe05121e5d.camel@aosc.io \
--to=icenowy@aosc.io \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=airlied@linux.ie \
--cc=anarsoul@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=drinkcat@chromium.org \
--cc=duwe@suse.de \
--cc=eballetbo@gmail.com \
--cc=enric.balletbo@collabora.com \
--cc=hsinyi@chromium.org \
--cc=jernej.skrabec@siol.net \
--cc=jonas@kwiboo.se \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=maxime@cerno.tech \
--cc=megous@megous.com \
--cc=narmstrong@baylibre.com \
--cc=tglx@linutronix.de \
/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).