linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Andersson <jan-FkzTOoA/JUlBDgjK7y7TUQ@public.gmane.org>
To: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	jacmet-OfajU3CKLf1/SzgSGea1oA@public.gmane.org
Subject: Re: [PATCH] i2c/busses: Add support for Aeroflex Gaisler I2CMST controller
Date: Wed, 16 Feb 2011 15:51:11 +0100	[thread overview]
Message-ID: <4D5BE45F.5020908@gaisler.com> (raw)
In-Reply-To: <20110216142708.GA6365-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>

On 02/16/2011 03:27 PM, Wolfram Sang wrote:
> Hi Jan,
>
> On Wed, Feb 16, 2011 at 01:30:48PM +0100, Jan Andersson wrote:
>> This patch adds support for the I2CMST core found on LEON/GRLIB SoCs.
>>
>> Signed-off-by: Jan Andersson<jan-FkzTOoA/JUlBDgjK7y7TUQ@public.gmane.org>
>> ---
>> The I2CMST core is basically the OpenCores I2C master with an AMBA APB
>> interface. This driver re-uses much of i2c-ocores.c. It is submitted as
>> a separate driver since the register interfaces differ sligthly. Also the
>> two IP cores are maintained separately so they may diverge further in
>> the future.
>>
>> The driver is identical in terms of transfer handling and HW control.
>> The original module author string has been kept.
>
> Just judging from this message, it seems that algo could be extracted and used
> by both drivers? Or would this make no sense?
>

Hi Wolfram,

The control parts of the *_process, *_isr and *_xfer functions could be 
shared by ripping it out and changing the calls used to read/set registers.

I considered that change more complex and did not think it to be worth 
the trouble for saving ~50 LOC (probably less with added glue). Of 
course, it could be beneficial to have the algo part shared if there are 
future updates to it. At the same time I suppose that it could be bad to 
have the algo part shared if the updates are only valid for one of the 
cores.

Best regards,
   Jan

  parent reply	other threads:[~2011-02-16 14:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-16 12:30 [PATCH] i2c/busses: Add support for Aeroflex Gaisler I2CMST controller Jan Andersson
     [not found] ` <1297859448-6621-1-git-send-email-jan-FkzTOoA/JUlBDgjK7y7TUQ@public.gmane.org>
2011-02-16 14:27   ` Wolfram Sang
     [not found]     ` <20110216142708.GA6365-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-02-16 14:51       ` Jan Andersson [this message]
     [not found]         ` <4D5BE45F.5020908-FkzTOoA/JUlBDgjK7y7TUQ@public.gmane.org>
2011-02-16 15:15           ` Wolfram Sang
2011-02-23  1:07           ` Ben Dooks
     [not found]             ` <20110223010703.GA15795-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
2011-02-23  9:38               ` Jan Andersson
     [not found]                 ` <4D64D5AC.3060301-FkzTOoA/JUlBDgjK7y7TUQ@public.gmane.org>
2011-02-23  9:46                   ` Peter Korsgaard
2011-02-23  1:06   ` Ben Dooks
     [not found]     ` <20110223010627.GZ15795-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
2011-02-23  9:26       ` Jan Andersson

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=4D5BE45F.5020908@gaisler.com \
    --to=jan-fkztooa/julbdgjk7y7tuq@public.gmane.org \
    --cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
    --cc=jacmet-OfajU3CKLf1/SzgSGea1oA@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@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).