linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
To: dmitry pervushin
	<dpervushin-L1vi/lXTdtvkgf6YlCu6wwC/G2K4zDHf@public.gmane.org>
Cc: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH, RFC] Freescale STMP: i2c driver
Date: Mon, 22 Jun 2009 11:51:48 +0100	[thread overview]
Message-ID: <20090622105148.GC9006@fluff.org.uk> (raw)
In-Reply-To: <1245169539.32549.12.camel-GL0tbJR47UuzLY3athcO2A@public.gmane.org>

On Tue, Jun 16, 2009 at 08:25:39PM +0400, dmitry pervushin wrote:
> Hello Ben,
> 
> I am sending the updated patch in next message, and this message is just
> to answer your questions/concerns.\
> 
> [...]
> > > +#include <mach/regs-apbx.h>
> > > +
> > > +static const u32 I2C_READ = 1,
> > > +		 I2C_WRITE = 0;
> > 
> > do you really want to be defining things with a prefix of I2C, thatB
> > might end up clashing with the i2c core?
> Fixed, changed to I2C_SMBUS_READ/WRITE as Jean Delvare proposed.
> > 
> > > +static const struct stmp3xxx_dma_command cmd_i2c_select = {
> > > +	.cmd =	BF(1, APBX_CHn_CMD_XFER_COUNT)	|
> > > +		BF(1, APBX_CHn_CMD_CMDWORDS)	|
> > > +		BM_APBX_CHn_CMD_WAIT4ENDCMD	|
> > > +		BM_APBX_CHn_CMD_CHAIN		|
> > > +		BF(BV_APBX_CHn_CMD_COMMAND__DMA_READ, APBX_CHn_CMD_COMMAND),
> > 
> > what is BF() ?
> it is the macro from arch/arm/plat-stmp3xxx/include/mach/platform.h,
> abbreviated "bitfield" :) For example, BF(1, APBX_CHn_CMD_CMDWORDS) is
> expanded like 
> ((1 << BP_APBX_CHn_CMD_CMDWORDS) & BM_APBX_CHn_CMD_CMDWORDS).
> BP_xxx stuff means bitfield position, BM_xxx - bitfield mask. 

yuck. I don't like people hiding thinks in macros for what is very
little gain, especially when an extant constant is being used!

-- 
Ben (ben-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org, http://www.fluff.org/)

  'a smiley only costs 4 bytes'

  parent reply	other threads:[~2009-06-22 10:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-03 19:59 [PATCH, RFC] Freescale STMP: i2c driver dmitry pervushin
     [not found] ` <1244059155.4074.19.camel-GL0tbJR47UuzLY3athcO2A@public.gmane.org>
2009-06-08 22:50   ` Ben Dooks
     [not found]     ` <20090608225034.GA20446-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2009-06-09  7:46       ` Jean Delvare
2009-06-16 16:25       ` dmitry pervushin
     [not found]         ` <1245169539.32549.12.camel-GL0tbJR47UuzLY3athcO2A@public.gmane.org>
2009-06-22 10:51           ` Ben Dooks [this message]
     [not found]             ` <20090622105148.GC9006-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2009-06-22 13:41               ` dmitry pervushin
2009-06-15  8:19   ` Ben Dooks
     [not found]     ` <20090615081938.GA19878-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2009-06-16 16:31       ` dmitry pervushin
     [not found]         ` <1245169913.32549.19.camel-GL0tbJR47UuzLY3athcO2A@public.gmane.org>
2009-06-22  0:47           ` Ben Dooks
     [not found]             ` <20090622004741.GB9006-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2009-06-22 13:39               ` dmitry pervushin
2009-06-22 13:42               ` [PATCH, RFC] Freescale STMP: i2c driver, updated with correct signed-off lines dmitry pervushin

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=20090622105148.GC9006@fluff.org.uk \
    --to=ben-linux-elnmno+kys3ytjvyw6ydsg@public.gmane.org \
    --cc=dpervushin-L1vi/lXTdtvkgf6YlCu6wwC/G2K4zDHf@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).