<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/sys/dev/pcf, branch release/12.3.0</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=release%2F12.3.0</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=release%2F12.3.0'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2019-02-01T03:26:10Z</updated>
<entry>
<title>MFC r343496:</title>
<updated>2019-02-01T03:26:10Z</updated>
<author>
<name>Andriy Voskoboinyk</name>
<email>avos@FreeBSD.org</email>
</author>
<published>2019-02-01T03:26:10Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=a97507532b6b03f8e0cc2b8f73d09000275b1535'/>
<id>urn:sha1:a97507532b6b03f8e0cc2b8f73d09000275b1535</id>
<content type='text'>
pcf(4): fix parentheses in if condition

PR:		210709
Submitted by:	David Binderman &lt;dcb314@hotmail.com&gt;
</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/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>sys/dev: minor spelling fixes.</title>
<updated>2016-05-03T03:41:25Z</updated>
<author>
<name>Pedro F. Giffuni</name>
<email>pfg@FreeBSD.org</email>
</author>
<published>2016-05-03T03:41:25Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=453130d9bfc1c6d68b366dfcb041689d69f81295'/>
<id>urn:sha1:453130d9bfc1c6d68b366dfcb041689d69f81295</id>
<content type='text'>
Most affect comments, very few have user-visible effects.
</content>
</entry>
<entry>
<title>Cleanup unnecessary semicolons from the kernel.</title>
<updated>2016-04-10T23:07:00Z</updated>
<author>
<name>Pedro F. Giffuni</name>
<email>pfg@FreeBSD.org</email>
</author>
<published>2016-04-10T23:07:00Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=74b8d63dcc17c07d8cb21e13f6db517698efd49f'/>
<id>urn:sha1:74b8d63dcc17c07d8cb21e13f6db517698efd49f</id>
<content type='text'>
Found with devel/coccinelle.
</content>
</entry>
<entry>
<title>Convert rman to use rman_res_t instead of u_long</title>
<updated>2016-01-27T02:23:54Z</updated>
<author>
<name>Justin Hibbits</name>
<email>jhibbits@FreeBSD.org</email>
</author>
<published>2016-01-27T02:23:54Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=2dd1bdf1834c53d048d3d9a7079b45afea5cecd7'/>
<id>urn:sha1:2dd1bdf1834c53d048d3d9a7079b45afea5cecd7</id>
<content type='text'>
Summary:
Migrate to using the semi-opaque type rman_res_t to specify rman resources.  For
now, this is still compatible with u_long.

This is step one in migrating rman to use uintmax_t for resources instead of
u_long.

Going forward, this could feasibly be used to specify architecture-specific
definitions of resource ranges, rather than baking a specific integer type into
the API.

This change has been broken out to facilitate MFC'ing drivers back to 10 without
breaking ABI.

Reviewed By: jhb
Sponsored by:	Alex Perez/Inertial Computing
Differential Revision: https://reviews.freebsd.org/D5075
</content>
</entry>
<entry>
<title>Use IIC_EBUSBSY and IIC_BUSERR status values consistantly across all drivers.</title>
<updated>2015-10-09T22:49:50Z</updated>
<author>
<name>Ian Lepore</name>
<email>ian@FreeBSD.org</email>
</author>
<published>2015-10-09T22:49:50Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=d1e99670ae56b733bfffe627047eb0a552b5ac7e'/>
<id>urn:sha1:d1e99670ae56b733bfffe627047eb0a552b5ac7e</id>
<content type='text'>
Make it clearer what each one means in the comments that define them.

IIC_BUSBSY was used in many places to mean two different things, either
"someone else has reserved the bus so you have to wait until they're done"
or "the signal level on the bus was not in the state I expected before/after
issuing some command".

Now IIC_BUSERR is used consistantly to refer to protocol/signaling errors,
and IIC_BUSBSY refers to ownership/reservation of the bus.
</content>
</entry>
<entry>
<title>Make ofw_bus_get_node() consistently return -1 when there is no associated</title>
<updated>2012-03-15T22:53:39Z</updated>
<author>
<name>Nathan Whitehorn</name>
<email>nwhitehorn@FreeBSD.org</email>
</author>
<published>2012-03-15T22:53:39Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=0d8d9edaaaca133545e9c50bbc51a19ea2bd6006'/>
<id>urn:sha1:0d8d9edaaaca133545e9c50bbc51a19ea2bd6006</id>
<content type='text'>
OF node, instead of a random mixture of 0 and -1. Update all checks for 0
to check for -1 instead.

MFC after:	4 weeks
</content>
</entry>
<entry>
<title>strict kobj signatures: fix iicbus_write impl in dev/pcf</title>
<updated>2009-06-11T17:15:44Z</updated>
<author>
<name>Andriy Gapon</name>
<email>avg@FreeBSD.org</email>
</author>
<published>2009-06-11T17:15:44Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=1c44eb75f7785130e2b860518d3bd538d9ab5804'/>
<id>urn:sha1:1c44eb75f7785130e2b860518d3bd538d9ab5804</id>
<content type='text'>
input buf is const

Reviewed by:	imp, current@
Approved by:	jhb (mentor)
</content>
</entry>
<entry>
<title>- Consolidate module version for the pcf module into just pcf.c instead</title>
<updated>2008-08-05T17:39:37Z</updated>
<author>
<name>John Baldwin</name>
<email>jhb@FreeBSD.org</email>
</author>
<published>2008-08-05T17:39:37Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=9e58d59f4166a9fad46bb4587bf4807c8a7f2e93'/>
<id>urn:sha1:9e58d59f4166a9fad46bb4587bf4807c8a7f2e93</id>
<content type='text'>
  of having duplicate versions in each bus attachment.
- Add a DRIVER_MODULE() instance so that the iicbus(4) driver will
  actually attach to pcf(4) driver instances.
- Fix compile of envctrl.c.

Pointy hat:	jhb (3)
</content>
</entry>
<entry>
<title>Add locking to the various iicbus(4) bridge drivers:</title>
<updated>2008-08-04T20:46:15Z</updated>
<author>
<name>John Baldwin</name>
<email>jhb@FreeBSD.org</email>
</author>
<published>2008-08-04T20:46:15Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=13e3657b7b30a7605e51c19d8341b2fbbf1bdfee'/>
<id>urn:sha1:13e3657b7b30a7605e51c19d8341b2fbbf1bdfee</id>
<content type='text'>
- Just grab Giant in the ixp425_iic(4) driver since this driver uses
  a shared address/data register window pair to access the actual
  I2C registers.  None of the other ixp425 drivers lock access to these
  shared address/data registers yet and that would need to be done before
  this could use any meaningful locking.
- Add locking to the interrupt handler and 'iicbus_reset' methods of the
  at91_twi(4) driver.
- Add locking to the pcf(4) driver.  Other pcf(4) fixes include:
  - Don't needlessly zero the softc.
  - Use bus_foo rather than bus_space_foo and remove bus space tag and
    handle from softc.
- The lpbb(4) driver just grabs Giant for now.  This will be refined later
  when ppbus(4) is locked.
- As was done with smbus earlier, move the DRIVER_MODULE() lines to match
  the bus driver (either iicbus or iicbb) to the bridge driver into the
  bridge drivers.

Tested by:	sam (arm/ixp425)
</content>
</entry>
</feed>
