From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] i2c: mxs: Add I2C multibus support
Date: Tue, 23 Sep 2014 16:30:41 +0200 [thread overview]
Message-ID: <201409231630.41856.marex@denx.de> (raw)
In-Reply-To: <CAP9ODKr4HtBgyquNo3fg42kBt+AJVCfJWdey294Ceik6qufHzA@mail.gmail.com>
On Tuesday, September 23, 2014 at 03:49:27 PM, Otavio Salvador wrote:
> On Tue, Sep 23, 2014 at 8:48 AM, Heiko Schocher <hs@denx.de> wrote:
> > Hello Marek,
> >
> > Am 23.09.2014 13:15, schrieb Marek Vasut:
> >> The i.MX28 has two I2C IP blocks, but the MXS I2C driver is hard-coded
> >> to use the I2C block 0 . Add multibus support so we can use both I2C
> >> busses as seen fit.
> >>
> >> Signed-off-by: Marek Vasut<marex@denx.de>
> >> Cc: Stefano Babic<sbabic@denx.de>
> >> ---
> >>
> >> drivers/i2c/mxs_i2c.c | 47
> >>
> >> +++++++++++++++++++++++++++++++++++++----------
> >>
> >> include/configs/mxs.h | 1 +
> >> 2 files changed, 38 insertions(+), 10 deletions(-)
> >
> > Sorry, I have to NACK this patch. Please convert the driver for using
> > the CONFIG_SYS_I2C framework, see for example the drivers/i2c/mxc_i2c.c
> > driver, thanks!
>
> I think the conversion could be a follow up patch, I see no good
> reason to block this patch as is.
I disagree with you. Accepting this patch as is would only hinder progress
toward the conversion and would set a bad example further down the line, leading
only to more crap patches. Moreover, this is 2015.01 matter, so there is plenty
of time for the rework to take place. Thus, I agree with Heiko.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-09-23 14:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 11:15 [U-Boot] [PATCH] i2c: mxs: Add I2C multibus support Marek Vasut
2014-09-23 11:48 ` Heiko Schocher
2014-09-23 13:49 ` Otavio Salvador
2014-09-23 14:30 ` Marek Vasut [this message]
2014-09-24 5:18 ` Heiko Schocher
2014-09-23 15:16 ` Fabio Estevam
2014-09-24 5:19 ` Heiko Schocher
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=201409231630.41856.marex@denx.de \
--to=marex@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox