Message ID | 20240208165937.2221193-1-andriy.shevchenko@linux.intel.com |
---|---|
Headers |
Return-Path: <linux-kernel+bounces-58436-ouuuleilei=gmail.com@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a05:7300:50ea:b0:106:860b:bbdd with SMTP id r10csp397838dyd; Thu, 8 Feb 2024 11:19:07 -0800 (PST) X-Google-Smtp-Source: AGHT+IGyTHyAy8hki34L5OCX5Kx6H2h6hCu7p89uEXTpkY0D/F0OhJZr5hOibXf4IBMITcMWC2Zf X-Received: by 2002:a17:90a:df04:b0:296:1cf3:e5b0 with SMTP id gp4-20020a17090adf0400b002961cf3e5b0mr216634pjb.29.1707419947499; Thu, 08 Feb 2024 11:19:07 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1707419947; cv=pass; d=google.com; s=arc-20160816; b=tvwpUF708h6Kq6R9z2vIuZz0p5W9/S/IY1WbhcMIdULIhOtQO1zXBctLA1y5I6/o/n SjM2bptcM/ltuhNIc+7RK+Dczxg/8tquDmUYDZqWPJOD48dfGtIVm0qeeJh+xfoiRxSk SJhHGjB0WMsI6et/vHqa4T+jNKW/SIabuaplrmqhuloe1BR7oQBFRP+METTDF7UZ+q08 9zPzAOOX2XEsFzHC0e4tiM9ZWwpouYqZwUv8Uzr8A77BBk+hviAvNlPwhU5TPwkzJLq/ 1bf4JUW3H3nqN+Q1I0SVUyaPnsC9/m278vUSnq/dg4yCIqrWmyadfKKKoTKVCJmaWEr0 7ydw== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:message-id:date:subject:cc:to :from:dkim-signature; bh=hIfhgN6of5maDaxWadNrOhQx4yDuvpw3L22Dog0W8OE=; fh=afQ8v8rhQYWPj25ErUK/5cPUMdNM3a6KE8uqEehgJRk=; b=QyYnI0jSloNBhCWu41dMmEk3PDMQ1cv3skaFIgdbrWdSfTjakefg0qXO3r91hk5D+U qD+akFfghZlM/H5JCJzUpRy/Umoc9yFvDH8/9sq73iaeF/3yEVYUzWqCBStABCojLbIR qnhaB3HHgdzvoR94ndgZEWOJO2vmgLSZwhUh+c+BseZWn+r/bQKzGG00IcTcYHijH2k0 07UNhKBIwZNhjH2tyktk6CjWpajq2f/qeX4XQ4hSzMR/bOHTPwUVw/syhB341g/vAmWl Y/Hv27FzuUuTYB913A2vfXSNJhrnAyG/2BDPKstFF0neH5DexAMAdGF7ZZ1o7fObYu5F yvCg==; dara=google.com ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=SaNW+zAF; arc=pass (i=1 dkim=pass dkdomain=intel.com dmarc=pass fromdomain=linux.intel.com); spf=pass (google.com: domain of linux-kernel+bounces-58436-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-58436-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com X-Forwarded-Encrypted: i=2; AJvYcCWlJ7/Bl0F1s18VE4hrpQatwLENqp5iapIwUrVjx11xHdNoUiLAIc/ntT0uYYZ0UcsO63FTb3ZLlxdorexYJACD9VPjKw== Received: from sv.mirrors.kernel.org (sv.mirrors.kernel.org. [2604:1380:45e3:2400::1]) by mx.google.com with ESMTPS id g4-20020a17090a9b8400b00296049f2f70si177080pjp.28.2024.02.08.11.19.07 for <ouuuleilei@gmail.com> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 08 Feb 2024 11:19:07 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-58436-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=SaNW+zAF; arc=pass (i=1 dkim=pass dkdomain=intel.com dmarc=pass fromdomain=linux.intel.com); spf=pass (google.com: domain of linux-kernel+bounces-58436-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-58436-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sv.mirrors.kernel.org (Postfix) with ESMTPS id E3534286522 for <ouuuleilei@gmail.com>; Thu, 8 Feb 2024 17:19:15 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 0A57C85C7F; Thu, 8 Feb 2024 17:17:38 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="SaNW+zAF" Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 5D46C823D2; Thu, 8 Feb 2024 17:17:33 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.16 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707412654; cv=none; b=Ff00ga5sVIFC2dXj1R1p8N5lNMFf3nTfG/ZgWRF9zgffT3MOXvbagotPFwMeIrIzB22fLfVCcHfbFaHtkfWyVDWEZSDQvw2utJXBrE9BLulH9KXBV6HiwcSI1K1luJwzJBzTaky1RC9sm+jBkaQV2dR+FQQeT+ewfvgBnU0ksNI= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707412654; c=relaxed/simple; bh=nKnI1gzZu/2gi1frEJ0pSztmvg8qGxw/QhIDsCZBNC8=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=QQBdxBYh8B+ljwBMWOjCyPRXDkr9Tg3PKFIj/5V2UaY7XE6JWFPoVAhMmtHGt4SXWmntaz+/RVQGeg0X3ymWcvKMbw3/tliOph+Fm9KcpLny3da84cQRp8G274pTV+X+85QGTn4+UI/yCWjQgdV1FFOQg1rCboB2e/QcJoQNrhs= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=none smtp.mailfrom=linux.intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=SaNW+zAF; arc=none smtp.client-ip=192.198.163.16 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=linux.intel.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1707412653; x=1738948653; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=nKnI1gzZu/2gi1frEJ0pSztmvg8qGxw/QhIDsCZBNC8=; b=SaNW+zAF5ZtVGFI7w36idtmlP75RcwW6ykKU29RNCBMnCSibhdB+SY92 NC3oxDBMrj4EySKlTkKdPvvDED1IxhTLqytvIMffCfWCai6L+AbLwo+Cw AZvOhaIuiXcuTDYgc0oeFyyrwymQoWBD20ef7dFsEqRKQI8ZKp27MSCac KS/wp65O3QaTAR2pxcLrwro5qJKgvEIpL120nDUjoW+QBQRthuRPKc7uu 8bPNU2A0xF7xUV2TZaHMYVNmkmM678Z8tN7zSlFGrQJp3zPpjLvaQPb+U ZiRjlRndDWo8eEOToQ2vh9BwlFJaXhctDS+9D8Pqhb+HNv4AyZ3YNMO+X Q==; X-IronPort-AV: E=McAfee;i="6600,9927,10978"; a="1565656" X-IronPort-AV: E=Sophos;i="6.05,254,1701158400"; d="scan'208";a="1565656" Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmvoesa110.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Feb 2024 09:17:32 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10978"; a="934195369" X-IronPort-AV: E=Sophos;i="6.05,254,1701158400"; d="scan'208";a="934195369" Received: from black.fi.intel.com ([10.237.72.28]) by fmsmga001.fm.intel.com with ESMTP; 08 Feb 2024 09:17:29 -0800 Received: by black.fi.intel.com (Postfix, from userid 1003) id F1C88130F; Thu, 8 Feb 2024 18:59:40 +0200 (EET) From: Andy Shevchenko <andriy.shevchenko@linux.intel.com> To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Miguel Ojeda <ojeda@kernel.org>, Rob Herring <robh@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Conor Dooley <conor+dt@kernel.org>, Robin van der Gracht <robin@protonic.nl>, Paul Burton <paulburton@kernel.org>, Geert Uytterhoeven <geert+renesas@glider.be> Subject: [PATCH v1 00/15] auxdisplay: linedisp: Clean up and add new driver Date: Thu, 8 Feb 2024 18:58:43 +0200 Message-ID: <20240208165937.2221193-1-andriy.shevchenko@linux.intel.com> X-Mailer: git-send-email 2.43.0.rc1.1.gbec44491f096 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: <linux-kernel.vger.kernel.org> List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org> List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1790354179362650526 X-GMAIL-MSGID: 1790359578502919487 |
Series |
auxdisplay: linedisp: Clean up and add new driver
|
|
Message
Andy Shevchenko
Feb. 8, 2024, 4:58 p.m. UTC
Add a new initial driver for Maxim MAX6958/6959 chips. While developing that driver I realised that there is a lot of duplication between ht16k33 and a new one. Hence set of cleanups and refactorings. Note, the new driver has minimum support of the hardware and I have plans to cover more features in the future. Andy Shevchenko (15): auxdisplay: img-ascii-lcd: Make container_of() no-op for struct linedisp auxdisplay: linedisp: Free allocated resources in ->release() auxdisplay: linedisp: Use unique number for id auxdisplay: linedisp: Unshadow error codes in ->store() auxdisplay: linedisp: Add missing header(s) auxdisplay: linedisp: Move exported symbols to a namespace auxdisplay: linedisp: Group line display drivers together auxdisplay: linedisp: Provide struct linedisp_ops for future extension auxdisplay: linedisp: Add support for overriding character mapping auxdisplay: linedisp: Provide a small buffer in the struct linedisp auxdisplay: ht16k33: Move ht16k33_linedisp_ops down auxdisplay: ht16k33: Switch to use line display character mapping auxdisplay: ht16k33: Use buffer from struct linedisp dt-bindings: auxdisplay: Add Maxim MAX6958/6959 auxdisplay: Add driver for MAX695x 7-segment LED controllers .../bindings/auxdisplay/maxim,max6959.yaml | 35 +++ drivers/auxdisplay/Kconfig | 40 ++-- drivers/auxdisplay/Makefile | 13 +- drivers/auxdisplay/ht16k33.c | 145 +++++-------- drivers/auxdisplay/img-ascii-lcd.c | 24 ++- drivers/auxdisplay/line-display.c | 162 ++++++++++++-- drivers/auxdisplay/line-display.h | 57 ++++- drivers/auxdisplay/max6959.c | 200 ++++++++++++++++++ 8 files changed, 530 insertions(+), 146 deletions(-) create mode 100644 Documentation/devicetree/bindings/auxdisplay/maxim,max6959.yaml create mode 100644 drivers/auxdisplay/max6959.c
Comments
On Thu, Feb 08, 2024 at 05:50:51PM +0000, Conor Dooley wrote: > On Thu, Feb 08, 2024 at 06:58:57PM +0200, Andy Shevchenko wrote: > > Add initial device tree documentation for Maxim MAX6958/6959. > > Why "initial"? Are there elements this display that you've not > documented yet? s/documented/implemented/ There are features of the hardware that may need additional properties. > > +title: MAX6958/6959 7-segment LED display controller with keyscan > > > +properties: > > + compatible: > > + const: maxim,max6959 > > Where's the max6958's compatible? I don't see it in your driver either. For now, see above, there is no need. Moreover, there is no need at all as we have autodetection mechanism. I don't see why we should have two compatible strings just for the sake of having them. > It seems that the max6959 has some interrupt capabilities that are not > available on the max6958, so a dedicated compatible seems suitable to > me. So, please clarify the DT's p.o.v. on the hardware that can be autodetected. Do we need to still have different compatible strings? What for? I don't see the need, sorry for my (silly) questions.
On Thu, Feb 08, 2024 at 07:10:40PM +0100, Geert Uytterhoeven wrote: > On Thu, Feb 8, 2024 at 6:52 PM Conor Dooley <conor@kernel.org> wrote: > > On Thu, Feb 08, 2024 at 06:58:43PM +0200, Andy Shevchenko wrote: > > > Add a new initial driver for Maxim MAX6958/6959 chips. > > > While developing that driver I realised that there is a lot > > > of duplication between ht16k33 and a new one. Hence set of > > > cleanups and refactorings. > > > > > > Note, the new driver has minimum support of the hardware and > > > I have plans to cover more features in the future. > > > > > > Andy Shevchenko (15): > > > auxdisplay: img-ascii-lcd: Make container_of() no-op for struct > > > linedisp > > > auxdisplay: linedisp: Free allocated resources in ->release() > > > auxdisplay: linedisp: Use unique number for id > > > auxdisplay: linedisp: Unshadow error codes in ->store() > > > auxdisplay: linedisp: Add missing header(s) > > > auxdisplay: linedisp: Move exported symbols to a namespace > > > auxdisplay: linedisp: Group line display drivers together > > > auxdisplay: linedisp: Provide struct linedisp_ops for future extension > > > auxdisplay: linedisp: Add support for overriding character mapping > > > auxdisplay: linedisp: Provide a small buffer in the struct linedisp > > > auxdisplay: ht16k33: Move ht16k33_linedisp_ops down > > > auxdisplay: ht16k33: Switch to use line display character mapping > > > auxdisplay: ht16k33: Use buffer from struct linedisp > > > dt-bindings: auxdisplay: Add Maxim MAX6958/6959 > > > auxdisplay: Add driver for MAX695x 7-segment LED controllers > > > > Not all of these patches have made their way to the lists FYI: > > 2024-02-08 16:58 Andy Shevchenko [this message] > > 2024-02-08 16:58 ` [PATCH v1 01/15] auxdisplay: img-ascii-lcd: Make container_of() no-op for struct linedisp Andy Shevchenko > > 2024-02-08 16:58 ` [PATCH v1 02/15] auxdisplay: linedisp: Free allocated resources in ->release() Andy Shevchenko > > 2024-02-08 16:58 ` [PATCH v1 03/15] auxdisplay: linedisp: Use unique number for id Andy Shevchenko > > 2024-02-08 16:58 ` [PATCH v1 06/15] auxdisplay: linedisp: Move exported symbols to a namespace Andy Shevchenko > > 2024-02-08 16:58 ` [PATCH v1 07/15] auxdisplay: linedisp: Group line display drivers together Andy Shevchenko > > 2024-02-08 16:58 ` [PATCH v1 08/15] auxdisplay: linedisp: Provide struct linedisp_ops for future extension Andy Shevchenko > > 2024-02-08 16:58 ` [PATCH v1 09/15] auxdisplay: linedisp: Add support for overriding character mapping Andy Shevchenko > > 2024-02-08 16:58 ` [PATCH v1 10/15] auxdisplay: linedisp: Provide a small buffer in the struct linedisp Andy Shevchenko > > 2024-02-08 16:58 ` [PATCH v1 14/15] dt-bindings: auxdisplay: Add Maxim MAX6958/6959 Andy Shevchenko > > 2024-02-08 16:58 ` [PATCH v1 15/15] auxdisplay: Add driver for MAX695x 7-segment LED controllers Andy Shevchenko > > https://lore.kernel.org/all/20240208165937.2221193-1-andriy.shevchenko@linux.intel.com/ > > Same for my mailbox. I just resent it, hopefully without missing parts now.