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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 97332C433FE for ; Fri, 18 Nov 2022 13:13:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=7JB8ctGYXNPZHcv5kmzY7KhDAXWd2+qd1RnsdCQLU8U=; b=xAa7A5lPn1BIrk kgJn0bjNgZ649/RF57RLMnDWYTZb8deMHBo2YT0EhS9QQc8hjVRN5ld+zOIl5hVxefzVdVsl1lb6q gQUhgW/YRlCfjxyX9Ctk7mF2VxUQloQLWYNeULfskuwRxu1qA3obc6yf65L0Rf4JNsQCJFA2NJBlB AEHIWCnHnrSZ5kH4VvMIcx5AxLSB9a1MFlMHMMqHPkH1+VG0xvVN+QYnDv3eQ0c+I5PeKmnlNrhHn 6iuFzpdNVylyzDHYKwxH3EbcrRm9Cnm4glWoWrt/8mSG0uzJREyHtaIzZNfS1sYpE4sRsl4Re16HF Oz+QZFlK/LlRMmmCEaRw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1ow1A3-004417-KN; Fri, 18 Nov 2022 13:12:03 +0000 Received: from vps0.lunn.ch ([156.67.10.101]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1ow1A0-0043yi-OG for linux-arm-kernel@lists.infradead.org; Fri, 18 Nov 2022 13:12:02 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=4Aeu8UwIWgXvC6uSW82BD1GlVbqZxuA9k7NKVXlvkIc=; b=fi6O3mFvI7PWujd16InhbX4q0g OqJCOxeSjTFaJdYdanioee16QbVe7lOlfsyEwIMZg7bqsHhyAuwcHyt0WK7T5I37CekR1LYmgit3E ZXWanr36/Z8VVHi9m2KvzZRLdytQabOIRqzu3bZEQZh4h9CyUkmy4oi/sfFBGsQt6KNo=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1ow19f-002nPj-PO; Fri, 18 Nov 2022 14:11:39 +0100 Date: Fri, 18 Nov 2022 14:11:39 +0100 From: Andrew Lunn To: Tim Harvey Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, netdev@vger.kernel.org, Heiner Kallweit , Russell King , Shawn Guo , Sascha Hauer , Pengutronix Kernel Team , Fabio Estevam , Rob Herring , Krzysztof Kozlowski Subject: Re: [PATCH 0/3] add dt configuration for dp83867 led modes Message-ID: References: <20221118001548.635752-1-tharvey@gateworks.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221118_051200_803631_BECA388F X-CRM114-Status: GOOD ( 11.47 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org > Andrew, > > I completely agree with you but I haven't seen how that can be done > yet. What support exists for a PHY driver to expose their LED > configuration to be used that way? Can you point me to an example? Nobody has actually worked on this long enough to get code merged. e.g. https://lore.kernel.org/netdev/20201004095852.GB1104@bug/T/ https://lists.archive.carbon60.com/linux/kernel/3396223 This is probably the last attempt, which was not too far away from getting merged: https://patches.linaro.org/project/linux-leds/cover/20220503151633.18760-1-ansuelsmth@gmail.com/ I seem to NACK a patch like yours every couple of months. If all that wasted time was actually spent on a common framework, this would of been solved years ago. How important is it to you to control these LEDs? Enough to finish this code and get it merged? Andrew _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel 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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2331FC433FE for ; Fri, 18 Nov 2022 13:12:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241750AbiKRNMR (ORCPT ); Fri, 18 Nov 2022 08:12:17 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37988 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241299AbiKRNMQ (ORCPT ); Fri, 18 Nov 2022 08:12:16 -0500 Received: from vps0.lunn.ch (vps0.lunn.ch [156.67.10.101]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 890338B13C; Fri, 18 Nov 2022 05:12:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=4Aeu8UwIWgXvC6uSW82BD1GlVbqZxuA9k7NKVXlvkIc=; b=fi6O3mFvI7PWujd16InhbX4q0g OqJCOxeSjTFaJdYdanioee16QbVe7lOlfsyEwIMZg7bqsHhyAuwcHyt0WK7T5I37CekR1LYmgit3E ZXWanr36/Z8VVHi9m2KvzZRLdytQabOIRqzu3bZEQZh4h9CyUkmy4oi/sfFBGsQt6KNo=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1ow19f-002nPj-PO; Fri, 18 Nov 2022 14:11:39 +0100 Date: Fri, 18 Nov 2022 14:11:39 +0100 From: Andrew Lunn To: Tim Harvey Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, netdev@vger.kernel.org, Heiner Kallweit , Russell King , Shawn Guo , Sascha Hauer , Pengutronix Kernel Team , Fabio Estevam , Rob Herring , Krzysztof Kozlowski Subject: Re: [PATCH 0/3] add dt configuration for dp83867 led modes Message-ID: References: <20221118001548.635752-1-tharvey@gateworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org > Andrew, > > I completely agree with you but I haven't seen how that can be done > yet. What support exists for a PHY driver to expose their LED > configuration to be used that way? Can you point me to an example? Nobody has actually worked on this long enough to get code merged. e.g. https://lore.kernel.org/netdev/20201004095852.GB1104@bug/T/ https://lists.archive.carbon60.com/linux/kernel/3396223 This is probably the last attempt, which was not too far away from getting merged: https://patches.linaro.org/project/linux-leds/cover/20220503151633.18760-1-ansuelsmth@gmail.com/ I seem to NACK a patch like yours every couple of months. If all that wasted time was actually spent on a common framework, this would of been solved years ago. How important is it to you to control these LEDs? Enough to finish this code and get it merged? Andrew