From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6A595C49ED7 for ; Fri, 20 Sep 2019 11:58:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 36DD32086A for ; Fri, 20 Sep 2019 11:58:16 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b="iemKs8ut" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2408818AbfITL6P (ORCPT ); Fri, 20 Sep 2019 07:58:15 -0400 Received: from fllv0016.ext.ti.com ([198.47.19.142]:46664 "EHLO fllv0016.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2404368AbfITL6O (ORCPT ); Fri, 20 Sep 2019 07:58:14 -0400 Received: from fllv0034.itg.ti.com ([10.64.40.246]) by fllv0016.ext.ti.com (8.15.2/8.15.2) with ESMTP id x8KBwA4L065674; Fri, 20 Sep 2019 06:58:10 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1568980690; bh=ey0viNTdU+GzdBNr4SUzMtQl3KW8nudMOoaA604+7+c=; h=From:To:CC:Subject:Date; b=iemKs8utd2aXKzYUao7FtZRIt5BpxxYouOflH1fVpdtG1gVit9CBNUu35AFfC0sfr no4ngcqEW9dYhOil8BkoKUV0yjYYZkgaBCA5jj/rfrEwM3WFzoNd7ErQvEWyMHNSK8 fQ8rxpKb5cSoQxrEicQF1SLh2E1IY5mnbf/Gr3To= Received: from DFLE104.ent.ti.com (dfle104.ent.ti.com [10.64.6.25]) by fllv0034.itg.ti.com (8.15.2/8.15.2) with ESMTPS id x8KBwAQk098944 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 20 Sep 2019 06:58:10 -0500 Received: from DFLE106.ent.ti.com (10.64.6.27) by DFLE104.ent.ti.com (10.64.6.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Fri, 20 Sep 2019 06:58:09 -0500 Received: from lelv0326.itg.ti.com (10.180.67.84) by DFLE106.ent.ti.com (10.64.6.27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5 via Frontend Transport; Fri, 20 Sep 2019 06:58:10 -0500 Received: from localhost (ileax41-snat.itg.ti.com [10.172.224.153]) by lelv0326.itg.ti.com (8.15.2/8.15.2) with ESMTP id x8KBw9ZA115013; Fri, 20 Sep 2019 06:58:09 -0500 From: Jean-Jacques Hiblot To: , , CC: , , , Jean-Jacques Hiblot Subject: [PATCH v4 0/2] leds: tlc591xx: switch to managed LED registration Date: Fri, 20 Sep 2019 13:58:04 +0200 Message-ID: <20190920115806.14475-1-jjhiblot@ti.com> X-Mailer: git-send-email 2.17.1 MIME-Version: 1.0 Content-Type: text/plain X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This subject of this series used to be "leds: tlc591xx: switch to OF and managed API" This mini-series updates the tlc591xx driver to use the managed API. The driver is also modified to pass the initialization data to the LED core layer. The goal is to be able to the generic led-backlight [0] driver on top of it. changes in v4: - rebased on top of linux-leds/for-5.5 changes in v3: - rebased on top of linux-leds/for-next - use devm_led_classdev_register_ext() instead of the late devm_of_led_classdev_register() - let the LED core assign the names of the LEDs changes in v2: - fixed LED indexing. Previous version did not allow for holes: if n LEDs were used, they had to be led(0) to led(n-1) Jean-Jacques Hiblot (2): leds: tlc591xx: simplify driver by using the managed led API leds: tlc591xx: use devm_led_classdev_register_ext() drivers/leds/leds-tlc591xx.c | 88 ++++++++++-------------------------- 1 file changed, 25 insertions(+), 63 deletions(-) -- 2.17.1