All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] [PATCH] DaVinci/i2c: allow multiple buses
Date: Wed, 11 Jan 2012 07:52:41 +0100	[thread overview]
Message-ID: <4F0D31B9.6040305@denx.de> (raw)
In-Reply-To: <CA+M6bX=P8X-O261yTwnsjrEDxDr7wQ4S9RU10PzbnyyDQgnwjA@mail.gmail.com>

Hello Tom, J?r?me,

Sorry for the late reply, but I just starting to look through my
backlog, after my vacation ...

Tom Rini wrote:
> On Wed, Dec 21, 2011 at 10:36 PM, J?r?me Carretero <cJ-uboot@zougloub.eu> wrote:
>> Hi Tom,
>>
>> I'm requesting comments on the following (untested) patch.
>> It adds support for multiple i2c buses on davinci_i2c, without altering one line of code.
>> What I don't like is that I'm doing a bit of macro black magic to transform constants into variables.
>> But I don't know whether refactoring the code would be accepted, so this is a first shot.
> 
> So, this follows the example of other i2c drivers, but as Wolfgang
> likes to point out, following another bad example isn't a valid reason
> to do something.  So, is this the right way or a bad example to
> follow, Wolfgang or Heiko?  Thanks!

Yes, that is the actual (not really nice) state to implement the
"multibus" feature for i2c. The better way would be to go this way:

http://git.denx.de/?p=u-boot/u-boot-i2c.git;a=shortlog;h=refs/heads/multibus_v2_20111112

but this branch is not up to date, some test on at last powerpc
and arm architectures should be done, and there are a lof of
checkpatch errors in this branch (any help is welcome ;-) ... so there
is some work to do, before this can go to mainline ...

bye,
Heiko
-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  reply	other threads:[~2012-01-11  6:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-22  5:36 [U-Boot] [RFC] [PATCH] DaVinci/i2c: allow multiple buses Jérôme Carretero
2012-01-05 19:46 ` Tom Rini
2012-01-11  6:52   ` Heiko Schocher [this message]
2012-01-11 13:30     ` Jérôme Carretero

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=4F0D31B9.6040305@denx.de \
    --to=hs@denx.de \
    --cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.