linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>, Lee Jones <lee@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Vladimir Oltean <olteanv@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	linux-leds@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [net-next PATCH v3 05/13] leds: trigger: netdev: introduce check for possible hw control
Date: Mon, 29 May 2023 17:32:21 +0200	[thread overview]
Message-ID: <6ce434f5-dfa7-4ef5-800f-7bb328ec5070@lunn.ch> (raw)
In-Reply-To: <20230527112854.2366-6-ansuelsmth@gmail.com>

On Sat, May 27, 2023 at 01:28:46PM +0200, Christian Marangi wrote:
> Introduce function to check if the requested mode can use hw control in
> preparation for hw control support. Currently everything is handled in
> software so can_hw_control will always return false.
> 
> Add knob with the new value hw_control in trigger_data struct to
> set hw control possible. Useful for future implementation to implement
> in set_baseline_state() the required function to set the requested mode
> using LEDs hw control ops and in other function to reject set if hw
> control is currently active.
> 
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>

Reviewed-by: Andrew Lunn <andrew@lunn.ch>

    Andrew

  reply	other threads:[~2023-05-29 15:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-27 11:28 [net-next PATCH v3 00/13] leds: introduce new LED hw control APIs Christian Marangi
2023-05-27 11:28 ` [net-next PATCH v3 01/13] leds: add APIs for LEDs hw control Christian Marangi
2023-05-29 15:31   ` Andrew Lunn
2023-05-27 11:28 ` [net-next PATCH v3 02/13] leds: add API to get attached device for LED " Christian Marangi
2023-05-27 11:28 ` [net-next PATCH v3 03/13] Documentation: leds: leds-class: Document new Hardware driven LEDs APIs Christian Marangi
2023-05-29  8:10   ` Bagas Sanjaya
2023-05-29 14:12     ` Jonathan Corbet
2023-05-29 14:09       ` Christian Marangi
2023-05-30  3:09         ` Bagas Sanjaya
2023-05-30 12:24           ` Andrew Lunn
2023-05-29 14:52     ` Andrew Lunn
2023-05-27 11:28 ` [net-next PATCH v3 04/13] leds: trigger: netdev: refactor code setting device name Christian Marangi
2023-05-27 11:28 ` [net-next PATCH v3 05/13] leds: trigger: netdev: introduce check for possible hw control Christian Marangi
2023-05-29 15:32   ` Andrew Lunn [this message]
2023-05-27 11:28 ` [net-next PATCH v3 06/13] leds: trigger: netdev: add basic check for hw control support Christian Marangi
2023-05-29 15:33   ` Andrew Lunn
2023-05-27 11:28 ` [net-next PATCH v3 07/13] leds: trigger: netdev: reject interval store for hw_control Christian Marangi
2023-05-29 15:33   ` Andrew Lunn
2023-05-27 11:28 ` [net-next PATCH v3 08/13] leds: trigger: netdev: add support for LED hw control Christian Marangi
2023-05-29 15:45   ` Andrew Lunn
2023-05-29 15:52     ` Christian Marangi
2023-05-27 11:28 ` [net-next PATCH v3 09/13] leds: trigger: netdev: validate configured netdev Christian Marangi
2023-05-27 11:28 ` [net-next PATCH v3 10/13] leds: trigger: netdev: init mode if hw control already active Christian Marangi
2023-05-27 11:28 ` [net-next PATCH v3 11/13] leds: trigger: netdev: expose netdev trigger modes in linux include Christian Marangi
2023-05-29 15:47   ` Andrew Lunn
2023-05-27 11:28 ` [net-next PATCH v3 12/13] net: dsa: qca8k: implement hw_control ops Christian Marangi
2023-05-29 15:52   ` Andrew Lunn
2023-05-27 11:28 ` [net-next PATCH v3 13/13] net: dsa: qca8k: add op to get ports netdev Christian Marangi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6ce434f5-dfa7-4ef5-800f-7bb328ec5070@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ansuelsmth@gmail.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=pavel@ucw.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).