<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src-test/sys/dev/gpio/gpioled.c, 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-23T11:15:22Z</updated>
<entry>
<title>gpioled: add a new hint for initial state</title>
<updated>2019-05-23T11:15:22Z</updated>
<author>
<name>Andriy Gapon</name>
<email>avg@FreeBSD.org</email>
</author>
<published>2019-05-23T11:15:22Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=211bd53a182803370b7b3dd8212d4cf153eed861'/>
<id>urn:sha1:211bd53a182803370b7b3dd8212d4cf153eed861</id>
<content type='text'>
hint.gpioled.%d.state determines the initial state of the LED when the
driver takes control over it:
  0 - the LED is off
  1 - the LED is on
 -1 - the LED is kept as it was

While here, add a module version declaration.

MFC after:	2 weks
</content>
</entry>
<entry>
<title>sys/dev: further adoption of SPDX licensing ID tags.</title>
<updated>2017-11-27T14:52:40Z</updated>
<author>
<name>Pedro F. Giffuni</name>
<email>pfg@FreeBSD.org</email>
</author>
<published>2017-11-27T14:52:40Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=718cf2ccb9956613756ab15d7a0e28f2c8e91cab'/>
<id>urn:sha1:718cf2ccb9956613756ab15d7a0e28f2c8e91cab</id>
<content type='text'>
Mainly focus on files that use BSD 2-Clause license, however the tool I
was using misidentified many licenses so this was mostly a manual - error
prone - task.

The Software Package Data Exchange (SPDX) group provides a specification
to make it easier for automated tools to detect and summarize well known
opensource licenses. We are gradually adopting the specification, noting
that the tags are considered only advisory and do not, in any way,
superceed or replace the license texts.
</content>
</entry>
<entry>
<title>Refactor FDT part of gpioled driver</title>
<updated>2016-11-07T21:15:39Z</updated>
<author>
<name>Oleksandr Tymoshenko</name>
<email>gonzo@FreeBSD.org</email>
</author>
<published>2016-11-07T21:15:39Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=aabc5ce043340c18d7bc7f7ca956724c66583625'/>
<id>urn:sha1:aabc5ce043340c18d7bc7f7ca956724c66583625</id>
<content type='text'>
- Split driver in two parts: FDT and non-FDT
- Instead of reattach gpioled nodes to GPIO bus use
    gpio_pin_get_by_ofw_idx and add ofwbus and simplebus as parrent buses

Reviewed by:	loos
Differential Revision:	https://reviews.freebsd.org/D8233
</content>
</entry>
<entry>
<title>[gpioled] add support for inverting the LED polarity.</title>
<updated>2016-07-31T06:24:26Z</updated>
<author>
<name>Adrian Chadd</name>
<email>adrian@FreeBSD.org</email>
</author>
<published>2016-07-31T06:24:26Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=d75e8c5089a969f19e23164edf1029729f2544e3'/>
<id>urn:sha1:d75e8c5089a969f19e23164edf1029729f2544e3</id>
<content type='text'>
No, this isn't a star trek science joke - sometimes LEDs are wired
up to be active low, so this is needed.

Submitted by:	Dan Nelson &lt;dnelson_1901@yahoo.com&gt;
</content>
</entry>
<entry>
<title>Get rid of two consumers of gpiobus acquire/release.</title>
<updated>2016-05-22T03:55:57Z</updated>
<author>
<name>Luiz Otavio O Souza</name>
<email>loos@FreeBSD.org</email>
</author>
<published>2016-05-22T03:55:57Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=03302aa37f00a2cba5baebcb93b726befb671dc2'/>
<id>urn:sha1:03302aa37f00a2cba5baebcb93b726befb671dc2</id>
<content type='text'>
The GPIO hardware should not be owned by a single device, this defeats any
chance of use of the GPIO controller as an interrupt source.

ow(4) is now the only consumer of this 'feature' before we can remove it
for good.

Discussed with:	ian, bsdimp
</content>
</entry>
<entry>
<title>Fix probe routine to return BUS_PROBE_DEFAULT instead of BUS_PROBE_SPECIFIC.</title>
<updated>2016-05-22T03:12:49Z</updated>
<author>
<name>Luiz Otavio O Souza</name>
<email>loos@FreeBSD.org</email>
</author>
<published>2016-05-22T03:12:49Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=fc5f218adedb6cec78b2e79b9b0ed6d98583978e'/>
<id>urn:sha1:fc5f218adedb6cec78b2e79b9b0ed6d98583978e</id>
<content type='text'>
While here fix a few style(9) issues.
</content>
</entry>
<entry>
<title>Add OF_prop_free function as a counterpart for OF_*prop_alloc</title>
<updated>2016-05-11T18:20:02Z</updated>
<author>
<name>Oleksandr Tymoshenko</name>
<email>gonzo@FreeBSD.org</email>
</author>
<published>2016-05-11T18:20:02Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=bc90a48ccf2a906024256a42463b47dd99631796'/>
<id>urn:sha1:bc90a48ccf2a906024256a42463b47dd99631796</id>
<content type='text'>
- Introduce new OF API function OF_prop_free to free memory allocated by
  OF_getprop_alloc and OF_getencprop_alloc. Current code just calls free(9)
  with M_OFWPROP memory class which assumes knowledge about OF_*prop_alloc
  functions' internals and leads to unneccessary code coupling

- Convert some of the free(..., M_OFWPROP) instances to OF_prop_free

Files affected by this commit are the ones I was able to test on real
hardware. The rest of free(..., M_OFWPROP) instances will be handled with
idividual maintainers

Reviewed by:	andrew
Differential Revision:	https://reviews.freebsd.org/D6315
</content>
</entry>
<entry>
<title>Use DEVMETHOD_END instead of its value to indicate end of methods table</title>
<updated>2016-05-11T00:34:43Z</updated>
<author>
<name>Oleksandr Tymoshenko</name>
<email>gonzo@FreeBSD.org</email>
</author>
<published>2016-05-11T00:34:43Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=e2a1919df0110f0b783b87f3a85fa1ec7a116b1d'/>
<id>urn:sha1:e2a1919df0110f0b783b87f3a85fa1ec7a116b1d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>gpioled(4) depends on gpiobus.</title>
<updated>2015-08-17T17:09:57Z</updated>
<author>
<name>Luiz Otavio O Souza</name>
<email>loos@FreeBSD.org</email>
</author>
<published>2015-08-17T17:09:57Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=e9aebbb018fa7fc7692a4dee8635138a42c90f69'/>
<id>urn:sha1:e9aebbb018fa7fc7692a4dee8635138a42c90f69</id>
<content type='text'>
This fixes the loading of gpioled as a module.

Sponsored by:	Rubicon Communications (Netgate)
</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>
</feed>
