From: Ian Abbott <abbotti@mev.co.uk>
To: Ian Abbott <ian.abbott@mev.co.uk>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Peter Huewe <peterhuewe@gmx.de>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Mori Hess <fmhess@users.sourceforge.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging/comedi: Fix undefined array subscript
Date: Wed, 13 Feb 2013 13:47:10 +0000 [thread overview]
Message-ID: <511B995E.3030905@mev.co.uk> (raw)
In-Reply-To: <511B7F58.4000909@mev.co.uk>
On 2013-02-13 11:56, Ian Abbott wrote:
> For a digital output subdevice, you could either read back the current
> values directly from the hardware or just use the value previously
> written. The Velleman K8055 doesn't have a command to read back the
> digital outputs from the hardware, so the last written value has to be
> used. But what if the digital outputs have never been written (or the
> analog outputs have never been written, since the same command updates
> all analog and digital channels)? A "reset" command is sent to the
> hardware on initialization by vmk80xx_reset_device() (only called for
> the K8055), but I don't know what effect this has on the actual digital
> (and analog) outputs (though I could find out easily enough as we appear
> to have one of these kits (assembled) lying around in the office). If
> necessary, we may have to also send a "write" command on initialization
> to make the hardware outputs match the initial software state.
I've had a quick play with a K8055 and it seems the "reset" command
issued during hardware initialization has no effect on the digital
outputs. (I tested this by setting some digital outputs with comedi
instructions - there are some handy LEDs on the board that light up or
not according to the state of the digital outputs - then rmmod'ing and
modprobe'ing the vmk80xx module - the LEDs remained in the same state.)
Since we can't read back the outputs on this board we should initialize
them to a known state. I'll submit some patches later.
Nothing to do with the patch in this thread, which has my Ack.
Acked-by: Ian Abbott <abbotti@mev.co.uk>
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
next prev parent reply other threads:[~2013-02-13 13:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 3:30 [PATCH] staging/comedi: Fix undefined array subscript Peter Huewe
2013-02-13 7:32 ` Dan Carpenter
2013-02-13 11:56 ` Ian Abbott
2013-02-13 13:47 ` Ian Abbott [this message]
2013-02-13 14:01 ` Dan Carpenter
2013-02-13 14:28 ` [PATCH v2] " Peter Huewe
2013-02-13 14:58 ` Dan Carpenter
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=511B995E.3030905@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=fmhess@users.sourceforge.net \
--cc=gregkh@linuxfoundation.org \
--cc=ian.abbott@mev.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
/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