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=-8.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham 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 22638C352AA for ; Wed, 2 Oct 2019 15:27:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E310721A4C for ; Wed, 2 Oct 2019 15:27:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1570030045; bh=N6nCtFyy4PN0zLmYzEpPNNT1Qk905Tislp/fIPFBW6c=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=f9za5PCQaVDeAfijVmGQ2y9gsXnahThFUYOEpA1eVggygW8YuV+MBlY0j28duKy3g l+axB8upKQe6qoS5RjECMXHoOk2EfwO6dNyA90Xq/A/h0yD9poPwg8D8WY5L8B6iw/ +hhAxLzcIL2A0aewZGV4RJjrt2kyMWES54q+kf4M= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727854AbfJBP1Y (ORCPT ); Wed, 2 Oct 2019 11:27:24 -0400 Received: from mail.kernel.org ([198.145.29.99]:37540 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727756AbfJBP1Y (ORCPT ); Wed, 2 Oct 2019 11:27:24 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 85DC821920; Wed, 2 Oct 2019 15:27:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1570030043; bh=N6nCtFyy4PN0zLmYzEpPNNT1Qk905Tislp/fIPFBW6c=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=LvckY60fpe1emInbuIWvc5DVgeT+jL3mgKoV0W1Pf3rwj8AsI/9Vwg/ZY/ImdWY3N u7U/dUAnTKFeaxkscPilExUZDukBvYJnkoxWJJyD6ojNtDUCwQN/aoJPkd8ohLqR1H vvulgk4GJJ/A2akUDQQkRpoQEf4j1Lf8bIDcnB2A= Date: Wed, 2 Oct 2019 17:27:20 +0200 From: Greg Kroah-Hartman To: Akinobu Mita Cc: linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org, "Rafael J. Wysocki" , Jacek Anaszewski , Pavel Machek , Dan Murphy Subject: Re: [PATCH -next 1/2] leds: add /sys/devices/virtual/led-trigger/ Message-ID: <20191002152720.GB1748000@kroah.com> References: <1570029181-11102-1-git-send-email-akinobu.mita@gmail.com> <1570029181-11102-2-git-send-email-akinobu.mita@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1570029181-11102-2-git-send-email-akinobu.mita@gmail.com> User-Agent: Mutt/1.12.2 (2019-09-21) Sender: linux-leds-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-leds@vger.kernel.org On Thu, Oct 03, 2019 at 12:13:00AM +0900, Akinobu Mita wrote: > Reading /sys/class/leds//trigger returns all available LED triggers. > However, this violates the "one value per file" rule of sysfs. > > This makes led_triggers "real" devices and provides an > /sys/devices/virtual/led-trigger/ directory that contains a sub-directoriy > for each LED trigger device. The name of the sub-directory matches the LED > trigger name. > > We can find all available LED triggers by listing this directory contents. > > Cc: Greg Kroah-Hartman > Cc: "Rafael J. Wysocki" > Cc: Jacek Anaszewski > Cc: Pavel Machek > Cc: Dan Murphy > Signed-off-by: Akinobu Mita > --- > .../ABI/testing/sysfs-devices-virtual-led-trigger | 8 +++ > drivers/leds/led-triggers.c | 57 ++++++++++++++++++++++ > include/linux/leds.h | 3 ++ > 3 files changed, 68 insertions(+) > create mode 100644 Documentation/ABI/testing/sysfs-devices-virtual-led-trigger > > diff --git a/Documentation/ABI/testing/sysfs-devices-virtual-led-trigger b/Documentation/ABI/testing/sysfs-devices-virtual-led-trigger > new file mode 100644 > index 0000000..b8eb8f3 > --- /dev/null > +++ b/Documentation/ABI/testing/sysfs-devices-virtual-led-trigger > @@ -0,0 +1,8 @@ > +What: /sys/devices/virtual/leds-trigger/ > +Date: September 2019 > +KernelVersion: 5.5 > +Contact: linux-leds@vger.kernel.org > +Description: > + This directory contains a sub-directoriy for each LED trigger > + device. The name of the sub-directory matches the LED trigger > + name. > diff --git a/drivers/leds/led-triggers.c b/drivers/leds/led-triggers.c > index 79e30d2..0b810cf 100644 > --- a/drivers/leds/led-triggers.c > +++ b/drivers/leds/led-triggers.c > @@ -267,21 +267,76 @@ void led_trigger_rename_static(const char *name, struct led_trigger *trig) > } > EXPORT_SYMBOL_GPL(led_trigger_rename_static); > > +struct ledtrig_device { > + struct device dev; > +}; > + > +static void ledtrig_device_release(struct device *dev) > +{ > + struct ledtrig_device *trig_dev = > + container_of(dev, struct ledtrig_device, dev); > + > + kfree(trig_dev); > +} > + > +static struct bus_type led_trigger_subsys = { > + .name = "led-trigger", > +}; > + > +static int led_trigger_subsys_init(void) > +{ > + static DEFINE_MUTEX(init_mutex); > + static bool init_done; > + int ret = 0; > + > + mutex_lock(&init_mutex); > + if (!init_done) { a test and set of an atomic would solve the issue of having both a mutex and a boolean, right? thanks, greg k-h