From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752442AbcGMIIU (ORCPT ); Wed, 13 Jul 2016 04:08:20 -0400 Received: from ipv4.connman.net ([82.165.8.211]:40239 "EHLO mail.holtmann.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750975AbcGMIIG convert rfc822-to-8bit (ORCPT ); Wed, 13 Jul 2016 04:08:06 -0400 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: [PATCH 1/2] Bluetooth: Add LED triggers for HCI frames tx and rx From: Marcel Holtmann In-Reply-To: <1466657923-5776-1-git-send-email-guodong.xu@linaro.org> Date: Wed, 13 Jul 2016 09:07:58 +0100 Cc: "Gustavo F. Padovan" , Johan Hedberg , "David S. Miller" , xuwei5@hisilicon.com, Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , catalin.marinas@arm.com, will.deacon@arm.com, haojian.zhuang@linaro.org, Linus Walleij , Tony Lindgren , "open list:BLUETOOTH DRIVERS" , Network Development , open list , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org Content-Transfer-Encoding: 8BIT Message-Id: References: <1466657923-5776-1-git-send-email-guodong.xu@linaro.org> To: Guodong Xu X-Mailer: Apple Mail (2.3124) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Guodong, > Two LED triggers are defined: tx_led and rx_led. Upon frames > available in HCI core layer, for tx or for rx, the combined LED > can blink. > > Verified on HiKey, 96boards. It uses hi6220 SoC and TI WL1835 combo > chip. > > Signed-off-by: Guodong Xu > --- > include/net/bluetooth/hci_core.h | 1 + > net/bluetooth/hci_core.c | 3 +++ > net/bluetooth/leds.c | 15 +++++++++++++++ > net/bluetooth/leds.h | 2 ++ > 4 files changed, 21 insertions(+) > > diff --git a/include/net/bluetooth/hci_core.h b/include/net/bluetooth/hci_core.h > index dc71473..37b8dd9 100644 > --- a/include/net/bluetooth/hci_core.h > +++ b/include/net/bluetooth/hci_core.h > @@ -398,6 +398,7 @@ struct hci_dev { > bdaddr_t rpa; > > struct led_trigger *power_led; > + struct led_trigger *tx_led, *rx_led; > > int (*open)(struct hci_dev *hdev); > int (*close)(struct hci_dev *hdev); > diff --git a/net/bluetooth/hci_core.c b/net/bluetooth/hci_core.c > index 45a9fc6..c6e1210 100644 > --- a/net/bluetooth/hci_core.c > +++ b/net/bluetooth/hci_core.c > @@ -3248,6 +3248,7 @@ int hci_recv_frame(struct hci_dev *hdev, struct sk_buff *skb) > skb_queue_tail(&hdev->rx_q, skb); > queue_work(hdev->workqueue, &hdev->rx_work); > > + hci_leds_blink_oneshot(hdev->rx_led); > return 0; > } > EXPORT_SYMBOL(hci_recv_frame); > @@ -3325,6 +3326,8 @@ static void hci_send_frame(struct hci_dev *hdev, struct sk_buff *skb) > BT_ERR("%s sending frame failed (%d)", hdev->name, err); > kfree_skb(skb); > } > + > + hci_leds_blink_oneshot(hdev->tx_led); > } so I am not convinced that this is the right way of doing TX/RX activity leds. This would have them purely based on HCI traffic and this would include control frames. I think that we want activity leds for actual radio activity. Meaning that when we have an active connection and ACL packets are exchanged or when we are scanning. Regards Marcel