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 DBD1BC6FD1E for ; Fri, 10 Mar 2023 09:40:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230076AbjCJJka (ORCPT ); Fri, 10 Mar 2023 04:40:30 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52430 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230221AbjCJJjg (ORCPT ); Fri, 10 Mar 2023 04:39:36 -0500 Received: from mail-yb1-xb29.google.com (mail-yb1-xb29.google.com [IPv6:2607:f8b0:4864:20::b29]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 11F77497C0 for ; Fri, 10 Mar 2023 01:37:38 -0800 (PST) Received: by mail-yb1-xb29.google.com with SMTP id k199so4664242ybf.4 for ; Fri, 10 Mar 2023 01:37:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1678441057; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=dkaa33xZucHUmrkT5EKmd+RR2GnIarbPW3jBS/IXiH4=; b=ILgy/F6/c0pxMeQ/+6TFJeeOwNTnmur/K+JvQ701v0qAA0vS7Fs3hSM2WV0r7T71AR 7iyHIC6BKS6Txkgct7txGB9X1f9a5XW4YC4NUMtvVFayyucjCMRJWfK7Ml/3TEFIjoFV V041ltbDeIdKFbE82x/frnGpKAk2ItooSDnmIwrBF0QnLTPC89Yo9wveO6wvD3WF0KtY 8WaWDVmLxFEWWA4uCYz5a/N6jiSA17yEwUyo9tEcTCEAWwyVVBd3K1utC5G7tXhiTF0j 71o7KVhFV0JvVVATu5MVkEh9usoL3P5lcfP10ng4cRA1ZwckPPEYmC1gjgqURqCJ/G+a JyfA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678441057; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=dkaa33xZucHUmrkT5EKmd+RR2GnIarbPW3jBS/IXiH4=; b=cIGU/5MJwskFWgrcZwRALDRohNKLJ/6EI9GjFIVz6TEmKXU3XXbaQgcIw+AYVfgPgD L++TSWBAl9TtHEbe5yH6l5g3bgMlryu2WMSnhnFTds7EFwQRw0g1gJU+9185pRlxSQR3 9TuEnGuekUw9/jl60AaWxu/QxUzfbI12Grk0/S6NMo0rrf4WYmx50+5JNu20Kyrc6qT9 empxdVSaEUze3cyb/H1cnVlsTQUGJNi7d0+OO3vJWM5HNAUhvQwJWQT0qaJRE45rOmkT SXz6A5iIE5FUVIZmVxRG7Uon813geZG7ac7woPi8exh9CTelPxhAMOjkFPZs2LSSM+Gv 0cNg== X-Gm-Message-State: AO0yUKXhkl6SQiEZ4RTC1RkG7Fedvp7uSYWoMRLvuvjf/Ai8lLui0FLV PqXNS/hG3jqnpGfxnZZxh0RmOKnAiFtydcvy91Jxow== X-Google-Smtp-Source: AK7set+5e6x1wi7MIweB5TOI7S3BjN5EW/S43FwJZUJkRYmGqWqeeshxKBdvJTlMBkQWSrF6TT50wquIIlxgcDtOgIE= X-Received: by 2002:a25:e201:0:b0:b2e:f387:b428 with SMTP id h1-20020a25e201000000b00b2ef387b428mr1178326ybe.5.1678441057179; Fri, 10 Mar 2023 01:37:37 -0800 (PST) MIME-Version: 1.0 References: <20230216013230.22978-1-ansuelsmth@gmail.com> <8226f000-dd9c-4774-b972-a7f1113f0986@lunn.ch> In-Reply-To: <8226f000-dd9c-4774-b972-a7f1113f0986@lunn.ch> From: Linus Walleij Date: Fri, 10 Mar 2023 10:37:25 +0100 Message-ID: Subject: Re: [PATCH v8 00/13] Adds support for PHY LEDs with offload triggers To: Andrew Lunn Cc: Christian Marangi , Hans de Goede , Pavel Machek , Lee Jones , Rob Herring , Krzysztof Kozlowski , Florian Fainelli , Vladimir Oltean , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Heiner Kallweit , Russell King , Jonathan Corbet , "Russell King (Oracle)" , Jacek Anaszewski , John Crispin , linux-leds@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, linux-doc@vger.kernel.org, Tim Harvey , Alexander Stein , Rasmus Villemoes , Bagas Sanjaya , Arun.Ramadoss@microchip.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 9, 2023 at 4:22 PM Andrew Lunn wrote: > As to 'how a certain trigger on a certain LED is going to associate > itself with, say, a certain port' is clearly a property of the > hardware, when offloading is supported. I've not seen a switch you can > arbitrarily assign LEDs to ports. The Marvell switches have the LED > registers within the port registers, for example, two LEDs per port. Aha so there is an implicit HW dependency between the port and the LED, that we just cannot see in the device tree. Okay, it makes sense. I think there will be a day when a switch without LED controller appears, but the system has a few LEDs for the ports connected to an arbitrary GPIO controller, and then we will need this. But we have not seen that yet :) Yours, Linus Walleij