From: "Ira W. Snyder" <iws@ovro.caltech.edu>
To: linux-kernel@vger.kernel.org
Cc: linux-can@vger.kernel.org, sameo@linux.intel.com,
"Ira W. Snyder" <iws@ovro.caltech.edu>
Subject: [PATCH 0/2] janz: fix support for Janz CMOD-IO revision 1.0 hardware
Date: Tue, 11 Sep 2012 15:58:13 -0700 [thread overview]
Message-ID: <1347404295-7985-1-git-send-email-iws@ovro.caltech.edu> (raw)
From: "Ira W. Snyder" <iws@ovro.caltech.edu>
The Janz CMOD-IO Carrier Board hardware, revision 1.0 has several quirks
that do not effect newer revisions of the hardware. This series fixes both
quirks so that the old hardware works correctly.
The janz-cmodio MFD driver did not mask out the unused bits from the
modulbus_number sysfs file. On CMOD-IO revision 1.0, the upper bits have
random data. By masking out the bits, the correct number is presented to
userspace.
The janz-ican3 driver used the reset_assert and reset_deassert registers.
These registers do not exist on CMOD-IO revision 1.0. To work around the
problem, the hardware reset registers on the ican3 hardware itself are
used.
These are trivial fixes that fix support for some hardware which is currently
broken. It would be nice to get these into the current kernel release.
Ira W. Snyder (2):
mfd/janz-cmodio: fix MODULBus number sysfs entry
can: janz-ican3: fix support for older hardware revisions
drivers/mfd/janz-cmodio.c | 2 +-
drivers/net/can/janz-ican3.c | 4 +---
2 files changed, 2 insertions(+), 4 deletions(-)
--
1.7.8.6
next reply other threads:[~2012-09-11 22:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 22:58 Ira W. Snyder [this message]
2012-09-11 22:58 ` [PATCH 1/2] mfd/janz-cmodio: fix MODULBus number sysfs entry Ira W. Snyder
2012-09-13 11:56 ` Marc Kleine-Budde
2012-09-13 12:52 ` Samuel Ortiz
2012-09-13 12:57 ` Marc Kleine-Budde
2012-09-11 22:58 ` [PATCH 2/2] can: janz-ican3: fix support for older hardware revisions Ira W. Snyder
2012-09-13 11:57 ` Marc Kleine-Budde
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=1347404295-7985-1-git-send-email-iws@ovro.caltech.edu \
--to=iws@ovro.caltech.edu \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
/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
all inboxes | Powered by JetHome®