public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Abbott <abbotti@mev.co.uk>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	Ian Abbott <ian.abbott@mev.co.uk>,
	"fmhess@users.sourceforge.net" <fmhess@users.sourceforge.net>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 36/36] staging: comedi: cb_pcidas: cleanup dac08_write()
Date: Wed, 27 Jun 2012 10:44:38 +0100	[thread overview]
Message-ID: <4FEAD606.9030605@mev.co.uk> (raw)
In-Reply-To: <201206261812.16108.hartleys@visionengravers.com>

On 2012-06-27 02:12, H Hartley Sweeten wrote:
> Reverse the logic of the test against the cached value so that
> the function only has one exit point.
>
> Make the logic of the dac write a bit clearer by create a local
> variable for the address used in the outw() calls and masking the
> value to write and setting the enable bits before doing the outw()
> calls. Add a comment just to make sure it's clear.
>
> Also, add a comment about the 'return 1;'.  This should be
> insn->n which is the number of data parameters used to do the
> dac08_write_insn() but the insn is not a parameter to this
> function.

It's probably better to make dac08_write() return void and return 1 in 
dac08_write_insn().

Actually, I think dac08_write_insn() ought to call dac08_write() in a 
loop, iterating over data[] and return insn->n.  That's what the 
INSN_WRITE instruction is meant to do although it's not implemented all 
that consistently by the drivers.

-- 
-=( Ian Abbott @ MEV Ltd.    E-mail: <abbotti@mev.co.uk>        )=-
-=( Tel: +44 (0)161 477 1898   FAX: +44 (0)161 718 3587         )=-



      reply	other threads:[~2012-06-27  9:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27  1:12 [PATCH 36/36] staging: comedi: cb_pcidas: cleanup dac08_write() H Hartley Sweeten
2012-06-27  9:44 ` Ian Abbott [this message]

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=4FEAD606.9030605@mev.co.uk \
    --to=abbotti@mev.co.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=fmhess@users.sourceforge.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=hartleys@visionengravers.com \
    --cc=ian.abbott@mev.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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