linux-kernel - Re: [PATCH 0/4] auxdisplay: Add support for TM1637 7-segment display driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aWYTTKmKHFzPo0xZ@smile.fi.intel.com>
Date: Tue, 13 Jan 2026 11:41:32 +0200
From: Andy Shevchenko <andriy.shevchenko@...el.com>
To: Sirat <email@...at.me>
Cc: Andy Shevchenko <andy.shevchenko@...il.com>, andy@...nel.org,
	geert@...ux-m68k.org, robh@...nel.org, krzk+dt@...nel.org,
	conor+dt@...nel.org, linux-kernel@...r.kernel.org,
	devicetree@...r.kernel.org
Subject: Re: [PATCH 0/4] auxdisplay: Add support for TM1637 7-segment display
 driver

On Tue, Jan 13, 2026 at 03:19:32PM +0600, Sirat wrote:

> Regarding Jean-François's series: I did check that out. It seems focused on
> the TM16xx variants that speak proper I2C or SPI (like TM1650/TM1638).

> The TM1637 has no slave address,

IIRC we have drivers for I2C peripherals that do not support the address.
Seems gpio-pca9570.c is the one I remember.

> and data is sent LSB-first which makes it
> incompatible with standard I2C adapters,

Does it? What prevents from reversing bits? (We have bitrev.h APIs)

> so I can't really piggyback on that driver's I2C backend.

Please, reconsider.

...

And please, do not top-post!

-- 
With Best Regards,
Andy Shevchenko