<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src-test/sys/dev/led, branch main</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src-test/atom?h=main</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src-test/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/'/>
<updated>2019-05-20T00:38:23Z</updated>
<entry>
<title>Extract eventfilter declarations to sys/_eventfilter.h</title>
<updated>2019-05-20T00:38:23Z</updated>
<author>
<name>Conrad Meyer</name>
<email>cem@FreeBSD.org</email>
</author>
<published>2019-05-20T00:38:23Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=e2e050c8ef733138fc6a9e514e4b856fefbc3ff1'/>
<id>urn:sha1:e2e050c8ef733138fc6a9e514e4b856fefbc3ff1</id>
<content type='text'>
This allows replacing "sys/eventfilter.h" includes with "sys/_eventfilter.h"
in other header files (e.g., sys/{bus,conf,cpu}.h) and reduces header
pollution substantially.

EVENTHANDLER_DECLARE and EVENTHANDLER_LIST_DECLAREs were moved out of .c
files into appropriate headers (e.g., sys/proc.h, powernv/opal.h).

As a side effect of reduced header pollution, many .c files and headers no
longer contain needed definitions.  The remainder of the patch addresses
adding appropriate includes to fix those files.

LOCK_DEBUG and LOCK_FILE_LINE_ARG are moved to sys/_lock.h, as required by
sys/mutex.h since r326106 (but silently protected by header pollution prior
to this change).

No functional change (intended).  Of course, any out of tree modules that
relied on header pollution for sys/eventhandler.h, sys/lock.h, or
sys/mutex.h inclusion need to be fixed.  __FreeBSD_version has been bumped.
</content>
</entry>
<entry>
<title>[led] propagate error from set_led() to the caller</title>
<updated>2019-01-15T00:52:41Z</updated>
<author>
<name>Oleksandr Tymoshenko</name>
<email>gonzo@FreeBSD.org</email>
</author>
<published>2019-01-15T00:52:41Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=7c895edb6673b6cfe6ddcc024a5d2ab234bda7cc'/>
<id>urn:sha1:7c895edb6673b6cfe6ddcc024a5d2ab234bda7cc</id>
<content type='text'>
Do not lose error condition by always returning 0 from set_led.
None of the calls to set_led checks for return value at the moment so
none of API consumers in base is affected.

PR:		231567
Submitted by:	Bertrand Petit &lt;bsdpr@phoe.frmug.org&gt;
MFC after:	1 week
</content>
</entry>
<entry>
<title>SPDX: use the Beerware identifier.</title>
<updated>2017-11-30T20:33:45Z</updated>
<author>
<name>Pedro F. Giffuni</name>
<email>pfg@FreeBSD.org</email>
</author>
<published>2017-11-30T20:33:45Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=64de3fdd5893e55c8aa20df2dcf1d9e86d851b34'/>
<id>urn:sha1:64de3fdd5893e55c8aa20df2dcf1d9e86d851b34</id>
<content type='text'>
</content>
</entry>
<entry>
<title>This implements default-state support as described in:</title>
<updated>2015-05-24T07:45:42Z</updated>
<author>
<name>Ganbold Tsagaankhuu</name>
<email>ganbold@FreeBSD.org</email>
</author>
<published>2015-05-24T07:45:42Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=3a9ac40382469a3ce163a2d4379bd8c41cdf6b47'/>
<id>urn:sha1:3a9ac40382469a3ce163a2d4379bd8c41cdf6b47</id>
<content type='text'>
https://www.kernel.org/doc/Documentation/devicetree/bindings/leds/leds-gpio.txt

Without this booting the VSATV102 causes the blue "working" led to turn
off when the kernel starts up. With this the led (which is turned on by
the firmware) stays on since that's the default state specified in the FDT.

Expanded the meaning of the led_create_state state parameter in order
to implement support for "keep". The original values were:

== 0             Off
!= 0             On

The new values are:

== -1            don't change / keep current setting
== 0             Off
!= -1 &amp;&amp; != 0    On

This should have no effect on acpi_asus_attach which only calls
led_create_state with state set to 1. Updated acpi_ibm_attach
in order to avoid surprises.

Differential Revision:	https://reviews.freebsd.org/D2615
Submitted by:	John Wehle
Reviewed by:	gonzo, loos
</content>
</entry>
<entry>
<title>MFcalloutng:</title>
<updated>2013-02-19T19:25:50Z</updated>
<author>
<name>Alexander Motin</name>
<email>mav@FreeBSD.org</email>
</author>
<published>2013-02-19T19:25:50Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=69c2a7707dfbb0fec7d1eb9b7f2856e94a83b423'/>
<id>urn:sha1:69c2a7707dfbb0fec7d1eb9b7f2856e94a83b423</id>
<content type='text'>
Make led(4) fire callouts at 10Hz only when there is at least one LED that
is requested to blink.  Do not fire if all LEDs are static (usual case).
</content>
</entry>
<entry>
<title>MFgraid/head r218174:</title>
<updated>2011-03-24T08:56:12Z</updated>
<author>
<name>Alexander Motin</name>
<email>mav@FreeBSD.org</email>
</author>
<published>2011-03-24T08:56:12Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=92b7c16c7371466cb312aba0ce2607c394925829'/>
<id>urn:sha1:92b7c16c7371466cb312aba0ce2607c394925829</id>
<content type='text'>
Add simple in-kernel API for controlling leds.
</content>
</entry>
<entry>
<title>Fix an incorrect use of sbuf_overflowed() after a call to sbuf_finish().</title>
<updated>2010-09-09T18:35:08Z</updated>
<author>
<name>Matthew D Fleming</name>
<email>mdf@FreeBSD.org</email>
</author>
<published>2010-09-09T18:35:08Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=10e0075ddb96d18cc1dbb02ef068f00c452f2157'/>
<id>urn:sha1:10e0075ddb96d18cc1dbb02ef068f00c452f2157</id>
<content type='text'>
</content>
</entry>
<entry>
<title>(S)LIST_HEAD_INITIALIZER takes a (S)LIST_HEAD as an argument.</title>
<updated>2009-12-28T22:56:30Z</updated>
<author>
<name>Antoine Brodin</name>
<email>antoine@FreeBSD.org</email>
</author>
<published>2009-12-28T22:56:30Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=13e403fdeadd26f9748ba83ea50ee271fbfc862a'/>
<id>urn:sha1:13e403fdeadd26f9748ba83ea50ee271fbfc862a</id>
<content type='text'>
Fix some wrong usages.
Note: this does not affect generated binaries as this argument is not used.

PR:		137213
Submitted by:	Eygene Ryabinkin (initial version)
MFC after:	1 month
</content>
</entry>
<entry>
<title>Remove unit2minor() use from kernel code.</title>
<updated>2008-09-26T14:19:52Z</updated>
<author>
<name>Ed Schouten</name>
<email>ed@FreeBSD.org</email>
</author>
<published>2008-09-26T14:19:52Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=d3ce8327194c0bcf742f2e03b5b0dc8f8cfe7f6b'/>
<id>urn:sha1:d3ce8327194c0bcf742f2e03b5b0dc8f8cfe7f6b</id>
<content type='text'>
When I changed kern_conf.c three months ago I made device unit numbers
equal to (unneeded) device minor numbers. We used to require
bitshifting, because there were eight bits in the middle that were
reserved for a device major number. Not very long after I turned
dev2unit(), minor(), unit2minor() and minor2unit() into macro's.
The unit2minor() and minor2unit() macro's were no-ops.

We'd better not remove these four macro's from the kernel, because there
is a lot of (external) code that may still depend on them. For now it's
harmless to remove all invocations of unit2minor() and minor2unit().

Reviewed by:	kib
</content>
</entry>
<entry>
<title>Add sbuf_new_auto as a shortcut for the very common case of creating a</title>
<updated>2008-08-09T11:14:05Z</updated>
<author>
<name>Dag-Erling Smørgrav</name>
<email>des@FreeBSD.org</email>
</author>
<published>2008-08-09T11:14:05Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=2616144e4345e4cdab56fd7c673fbb69074a9ce2'/>
<id>urn:sha1:2616144e4345e4cdab56fd7c673fbb69074a9ce2</id>
<content type='text'>
completely dynamic sbuf.

Obtained from:	Varnish
MFC after:	2 weeks
</content>
</entry>
</feed>
