Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 22 May 2019 21:06:33 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 189914] i2c(8) utility does not work on Raspberry Pi
Message-ID:  <bug-189914-227-aCgsThzjAY@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-189914-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-189914-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D189914

--- Comment #13 from commit-hook@freebsd.org ---
A commit references this bug:

Author: ian
Date: Wed May 22 21:06:10 UTC 2019
New revision: 348120
URL: https://svnweb.freebsd.org/changeset/base/348120

Log:
  Add a new 'tr' (transfer) mode to i2c(8) to support more i2c controllers.

  Some i2c controller hardware does not provide a way to do individual STAR=
T,
  REPEAT-START and STOP actions on the i2c bus.  Instead, they can only do
  a complete transfer as a single operation.  Typically they can do either
  START-data-STOP or START-data-REPEATSTART-data-STOP.  In the i2c driver
  framework, this corresponds to the iicbus_transfer method.  In the userla=
nd
  interface they are initiated with the I2CRDWR ioctl command.

  These changes add a new 'tr' mode which can be specified with the '-m'
  command line option.  This mode should work on all hardware; when an i2c
  controller driver doesn't directly support the iicbus_transfer method,
  code in the i2c driver framework uses the lower-level START/REPEAT/STOP
  methods to implement the transfer.  After this new mode has gotten some
  testing on various hardware, the 'tr' mode should probably become the
  new default mode.

  PR:           189914

Changes:
  head/usr.sbin/i2c/i2c.8
  head/usr.sbin/i2c/i2c.c

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-189914-227-aCgsThzjAY>