Received: by 2002:a05:7412:251c:b0:e2:908c:2ebd with SMTP id w28csp1196646rda; Mon, 23 Oct 2023 05:46:26 -0700 (PDT) X-Google-Smtp-Source: AGHT+IHCYvl+MiHRKSs0k+aoTURZvaHpl0OcoYYafTkCI6uNPrBYzYEN1WYdIl9MHDMarFGnxV2I X-Received: by 2002:a17:902:f687:b0:1c9:cc88:5008 with SMTP id l7-20020a170902f68700b001c9cc885008mr7927661plg.43.1698065185968; Mon, 23 Oct 2023 05:46:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1698065185; cv=none; d=google.com; s=arc-20160816; b=aiE3aevnjCuf1IKf0xWcqOd/xGLoVQEIcqPGuHcNwb44IuaCljTnmHU9sztRdlUVxz Fmvqw3gaFQAkVcguG7I6x1NnCqziYBxyOfEVzT4EwpM0qF4uT7wr7FpronnPjxtOUunz xV4/ekxiAUxzRbaCZVWuBTxG6bPm1rusXT3Dfxw2+hun3G045pv2x14szXXupVTJRjGO eADx6VvIcWU6AQZRCdV0+lR18bQGSMycw8xQlRoF2gm0J3mKxL1m2Y+3NHwrlxCxU4la XUOq/cdV/DL7rpSY2MUkwc/ZSOF2r+Dua8MURJ6b0M7M4TG8McUKxyPWQjwAb9pTWhKd 8rrQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:message-id:references:in-reply-to :subject:cc:to:from:date:content-transfer-encoding:mime-version; bh=OGeiCTgHzVWTojmH1YZT+GF2ObTLSESSPCgFq4oHk4s=; fh=mP5kyvj1RuZKzZOjR6pnX/1muXKtxpjKqd1FRxlYo8Q=; b=je6A+Of724nQYXU1/wN2xvWRgEdurte1hzaXJ31rts7HUxxDJUtmXJ1+1mjCSK8el7 kHp4gWkfCam1gL0jjXl0xm8LS8bvJ6npVPDrZRWScNC6Eo5uSobALufChlUZKHI86ID8 2KFJVQrc8Jx8Q4qb2qPP/4I6MaUcOdRGAWE/OaNjTDEch/0dFIMt4xg32++0fdcUvHug gRPO42gmYALundpMYdNFEc9SWmZ0LTs/S6ATcsRd8/j/PjgpHvm2/uSviTSMe86v6MMJ WgQGWwjOQnbhG9VkLUW4H8sRSk5ANheXazouBWj9hVvJVjgBI8bDnwLMexe5BOi4Jq5W 9t+A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:6 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from pete.vger.email (pete.vger.email. [2620:137:e000::3:6]) by mx.google.com with ESMTPS id ij25-20020a170902ab5900b001c9b5d2c3fasi6015619plb.523.2023.10.23.05.46.25 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 23 Oct 2023 05:46:25 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:6 as permitted sender) client-ip=2620:137:e000::3:6; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:6 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by pete.vger.email (Postfix) with ESMTP id 56465807CECB; Mon, 23 Oct 2023 05:46:23 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at pete.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230071AbjJWMqO (ORCPT + 99 others); Mon, 23 Oct 2023 08:46:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37322 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229613AbjJWMqN (ORCPT ); Mon, 23 Oct 2023 08:46:13 -0400 Received: from mxout70.expurgate.net (mxout70.expurgate.net [194.37.255.70]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2B6B4A4; Mon, 23 Oct 2023 05:46:11 -0700 (PDT) Received: from [127.0.0.1] (helo=localhost) by relay.expurgate.net with smtp (Exim 4.92) (envelope-from ) id 1quuJh-0036p8-FW; Mon, 23 Oct 2023 14:45:57 +0200 Received: from [195.243.126.94] (helo=securemail.tdt.de) by relay.expurgate.net with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1quuJg-001WBy-Hj; Mon, 23 Oct 2023 14:45:56 +0200 Received: from securemail.tdt.de (localhost [127.0.0.1]) by securemail.tdt.de (Postfix) with ESMTP id 30EF5240049; Mon, 23 Oct 2023 14:45:56 +0200 (CEST) Received: from mail.dev.tdt.de (unknown [10.2.4.42]) by securemail.tdt.de (Postfix) with ESMTP id 822CD240040; Mon, 23 Oct 2023 14:45:55 +0200 (CEST) Received: from mail.dev.tdt.de (localhost [IPv6:::1]) by mail.dev.tdt.de (Postfix) with ESMTP id 19EB221272; Mon, 23 Oct 2023 14:45:55 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 23 Oct 2023 14:45:55 +0200 From: Florian Eckert To: Greg KH Cc: Eckert.Florian@googlemail.com, jirislaby@kernel.org, pavel@ucw.cz, lee@kernel.org, kabel@kernel.org, u.kleine-koenig@pengutronix.de, m.brock@vanmierlo.com, linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org, linux-leds@vger.kernel.org Subject: Re: [PATCH v5 2/2] leds: ledtrig-tty: add new line mode evaluation In-Reply-To: <2023102320-princess-issuing-be13@gregkh> References: <20231023094205.2706812-1-fe@dev.tdt.de> <20231023094205.2706812-3-fe@dev.tdt.de> <2023102341-jogger-matching-dded@gregkh> <7e8860574413505c314bdfd0f3e10188@dev.tdt.de> <2023102320-princess-issuing-be13@gregkh> Message-ID: X-Sender: fe@dev.tdt.de User-Agent: Roundcube Webmail/1.3.17 X-Spam-Status: No, score=-0.8 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on pete.vger.email X-purgate-type: clean X-purgate: clean X-purgate-ID: 151534::1698065157-066056AA-3CCDE06D/0/0 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (pete.vger.email [0.0.0.0]); Mon, 23 Oct 2023 05:46:23 -0700 (PDT) On 2023-10-23 14:27, Greg KH wrote: > On Mon, Oct 23, 2023 at 02:15:55PM +0200, Florian Eckert wrote: >> > Again, I thought we had rx/tx already? If not, how was that controlled >> > today? >> >> It could not be controlled! The LED flashed when data where >> transferred. >> This was the only function that the trigger supported. > > Ok, then maybe this needs to be a bit longer of a series. One that > does > the "tx/rx" feature, as that is needed today, and will be the more > complex one, and then one-per-line-setting that you want to apply. > > That should make it much easier to review overall, right? Sorry for asking, but why should I split the change. What is the added value? But if it is necessary, then I will do it. Before my change, the trigger could not be configured. The LED always flashed when data was transferred. Now I can configure for which tty event the LED should flash or be on/off. So that the trigger behaves the same as before (flash on rx/tx transmission), I set the rx/tx bits in the function ledtrig_tty_activate() with the following code. Nothing changes for the user of the trigger. /* Enable default rx/tx LED blink */ set_bit(TRIGGER_TTY_TX, &trigger_data->ttytrigger); set_bit(TRIGGER_TTY_RX, &trigger_data->ttytrigger); --- Florian