[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdYHXwUsN8as7dKOvb00Ec4th45FyBV7TyBOfO4sR=78MA@mail.gmail.com>
Date: Mon, 24 Aug 2020 22:55:22 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Paul Cercueil <paul@...pouillou.net>
Cc: Thierry Reding <thierry.reding@...il.com>,
Sam Ravnborg <sam@...nborg.org>,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>,
Rob Herring <robh+dt@...nel.org>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
Noralf Tronnes <noralf@...nnes.org>,
Laurent Pinchart <Laurent.pinchart@...asonboard.com>,
od@...c.me,
"open list:DRM PANEL DRIVERS" <dri-devel@...ts.freedesktop.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 5/6] drm/panel: Add panel driver for NewVision NV3052C
based LCDs
On Sat, Aug 22, 2020 at 6:33 PM Paul Cercueil <paul@...pouillou.net> wrote:
> +static const struct nv3052c_reg nv3052c_regs[] = {
> + { 0xff, 0x30 },
> + { 0xff, 0x52 },
> + { 0xff, 0x01 },
> + { 0xe3, 0x00 },
> + { 0x40, 0x00 },
(...)
Well that's pretty opaque :D
I suppose no datasheet (why do vendors keep doing this to us...)
In other kernel code I have referred to this as a "jam table", e.g.
drivers/net/dsa/rtl8366rb.c.
I didn't make this up, the name comes from Bunnie Huang's
book on hacking the Xbox, and he says it is common hardware
engineer lingo.
https://www.iacr.org/workshops/ches/ches2002/presentations/Huang.pdf
What about naming it nv3052c_jam_table[] or nv3052c_jam[]?
Yours,
Linus Walleij
Powered by blists - more mailing lists