From: Nicolas Boichat <drinkcat@chromium.org> To: "Ondřej Jirman" <megous@megous.com>, "Icenowy Zheng" <icenowy@aosc.io>, "Enric Balletbo i Serra" <enric.balletbo@collabora.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, 6 Mar 2020 20:11:07 +0800 [thread overview] Message-ID: <CANMq1KC1R4B66Nr01pADa3RV8NpkPqkM-1pe-1N1nQiMviX1Cg@mail.gmail.com> (raw) In-Reply-To: <20200306120726.t7aitfz5rq3m7m6y@core.my.home> On Fri, Mar 6, 2020 at 8:07 PM Ondřej Jirman <megous@megous.com> wrote: > > On Fri, Mar 06, 2020 at 04:53:46PM +0800, Icenowy Zheng wrote: > > 在 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 .??.???......??. > > My values for 0x28 address match this. ^ What about the values at 0x2c? > Interesting that it returns different register values for different > device addresses. Yes the registers have different meanings for the 2 addresses. Thanks,
WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Boichat <drinkcat@chromium.org> To: "Ondřej Jirman" <megous@megous.com>, "Icenowy Zheng" <icenowy@aosc.io>, "Enric Balletbo i Serra" <enric.balletbo@collabora.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, 6 Mar 2020 20:11:07 +0800 [thread overview] Message-ID: <CANMq1KC1R4B66Nr01pADa3RV8NpkPqkM-1pe-1N1nQiMviX1Cg@mail.gmail.com> (raw) In-Reply-To: <20200306120726.t7aitfz5rq3m7m6y@core.my.home> On Fri, Mar 6, 2020 at 8:07 PM Ondřej Jirman <megous@megous.com> wrote: > > On Fri, Mar 06, 2020 at 04:53:46PM +0800, Icenowy Zheng wrote: > > 在 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 .??.???......??. > > My values for 0x28 address match this. ^ What about the values at 0x2c? > Interesting that it returns different register values for different > device addresses. Yes the registers have different meanings for the 2 addresses. Thanks, _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-03-06 12:11 UTC|newest] Thread overview: 48+ 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 ` 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-13 14:54 ` Enric Balletbo i Serra 2020-02-14 12:18 ` Andrzej Hajda 2020-02-14 12:18 ` Andrzej Hajda 2020-02-14 13:29 ` Nicolas Boichat 2020-02-14 13:29 ` Nicolas Boichat 2020-02-15 0:36 ` Nicolas Boichat 2020-02-15 0:36 ` Nicolas Boichat 2020-02-14 21:36 ` Vasily Khoruzhick 2020-02-14 21:36 ` Vasily Khoruzhick 2020-02-14 21:53 ` Enric Balletbo Serra 2020-02-14 21:53 ` Enric Balletbo Serra 2020-02-14 22:17 ` Vasily Khoruzhick 2020-02-14 22:17 ` Vasily Khoruzhick 2020-02-14 22:20 ` Enric Balletbo Serra 2020-02-14 22:20 ` Enric Balletbo Serra 2020-02-14 22:22 ` Vasily Khoruzhick 2020-02-14 22:22 ` Vasily Khoruzhick 2020-03-05 15:28 ` Enric Balletbo i Serra 2020-03-05 15:28 ` Enric Balletbo i Serra 2020-03-05 18:29 ` Vasily Khoruzhick 2020-03-05 18:29 ` Vasily Khoruzhick 2020-03-05 18:35 ` Icenowy Zheng 2020-03-05 18:35 ` Icenowy Zheng 2020-03-06 8:46 ` Enric Balletbo i Serra 2020-03-06 8:46 ` Enric Balletbo i Serra 2020-03-05 19:35 ` Ondřej Jirman 2020-03-05 19:35 ` Ondřej Jirman 2020-03-06 8:46 ` Enric Balletbo i Serra 2020-03-06 8:46 ` Enric Balletbo i Serra 2020-03-06 8:53 ` Icenowy Zheng 2020-03-06 8:53 ` Icenowy Zheng 2020-03-06 12:07 ` Ondřej Jirman 2020-03-06 12:07 ` Ondřej Jirman 2020-03-06 12:11 ` Nicolas Boichat [this message] 2020-03-06 12:11 ` Nicolas Boichat 2020-03-06 12:46 ` Ondřej Jirman 2020-03-06 12:46 ` Ondřej Jirman 2020-03-06 12:03 ` Ondřej Jirman 2020-03-06 12:03 ` Ondřej Jirman 2020-03-06 12:18 ` Enric Balletbo i Serra 2020-03-06 12:18 ` Enric Balletbo i Serra 2020-02-15 0:57 ` Nicolas Boichat 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 2020-02-19 15:30 ` 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=CANMq1KC1R4B66Nr01pADa3RV8NpkPqkM-1pe-1N1nQiMviX1Cg@mail.gmail.com \ --to=drinkcat@chromium.org \ --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=duwe@suse.de \ --cc=eballetbo@gmail.com \ --cc=enric.balletbo@collabora.com \ --cc=hsinyi@chromium.org \ --cc=icenowy@aosc.io \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.