All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Johannes Thumshirn <johannes.thumshirn@men.de>
Cc: Andreas Werner <andreas.werner@men.de>,
	linux-kernel@vger.kernel.org, sameo@linux.intel.com,
	wim@iguana.be, linux-watchdog@vger.kernel.org,
	cooloney@gmail.com, rpurdie@rpsys.net,
	linux-leds@vger.kernel.org
Subject: Re: [PATCH v2 1/3] drivers/mfd/menf21bmc: introduce MEN 14F021P00 BMC MFD Core driver
Date: Wed, 28 May 2014 09:24:05 +0100	[thread overview]
Message-ID: <20140528082404.GA10803@lee--X1> (raw)
In-Reply-To: <20140528070222.GA24101@jtlinux>

> > > The MEN 14F021P00 Board Management Controller provides an
> > > I2C interface to the host to access the feature implemented in the BMC.
> > > The BMC is a PIC Microntroller assembled on CPCI Card from MEN Mikroelektronik
> > > and on a few Box/Display Computer.
> > >
> > > Added MFD Core driver, supporting the I2C communication to the device.
> > >
> > > The MFD driver currently supports the following features:
> > > 	- Watchdog
> > > 	- LEDs
> > >
> > > Signed-off-by: Andreas Werner <andreas.werner@men.de>
> > > ---
> > >  drivers/mfd/Kconfig           |  12 +++
> > >  drivers/mfd/Makefile          |   1 +
> > >  drivers/mfd/menf21bmc.c       | 220 ++++++++++++++++++++++++++++++++++++++++++
> > >  include/linux/mfd/menf21bmc.h |  31 ++++++
> > >  4 files changed, 264 insertions(+)
> > >  create mode 100644 drivers/mfd/menf21bmc.c
> > >  create mode 100644 include/linux/mfd/menf21bmc.h

[...]

> > > +static int menf21bmc_write_byte(struct i2c_client *client, u8 val)
> > > +{
> > > +	int ret;
> > > +	struct menf21bmc *data = i2c_get_clientdata(client);
> > > +
> > > +	mutex_lock(&data->lock);
> > > +	ret = i2c_smbus_write_byte(client, val);
> > > +	mutex_unlock(&data->lock);
> > > +
> > > +	return ret;
> > > +}
> >
> > Didn't we ask you to remove these?  Just make the i2c_smbus_* calls
> > from within the driver.  The I2C subsystem conducts its own locking.
> > I'm really starting to frown on aggregation for the sake of
> > aggregation.  It's just overhead.
> >
> 
> Correct me if I'm wrong but as far as I remember Guenther asked to retain the
> original API, not the remove the "abstraction layer". Once we build a board with
> one of these BMCs attached via e.g. SPI we would have to reintroduce it anyways,
> in order to re-use these drivers.

If there are two or more possible interfaces then I agree, these
aggregations would be the best approach.  However, as it stands, that's
not currently the case.

Genuine question; are Men on the verge of building such a board, or
are we talking about 'ifs' and 'maybes'?

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2014-05-28  8:24 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-27  9:05 [PATCH v2 0/3] Introduce MEN 14F02100 BMC driver series Andreas Werner
2014-05-27  9:05 ` Andreas Werner
2014-05-27  9:06 ` [PATCH v2 1/3] drivers/mfd/menf21bmc: introduce MEN 14F021P00 BMC MFD Core driver Andreas Werner
2014-05-27  9:06   ` Andreas Werner
2014-05-27 15:05   ` Lee Jones
2014-05-28  7:02     ` Johannes Thumshirn
2014-05-28  7:02       ` Johannes Thumshirn
2014-05-28  8:24       ` Lee Jones [this message]
2014-05-28 11:51         ` Andreas Werner
2014-05-28 11:51           ` Andreas Werner
2014-05-28 13:29           ` Guenter Roeck
2014-05-28 13:52             ` Guenter Roeck
2014-06-02  8:06               ` Andreas Werner
2014-06-02  8:06                 ` Andreas Werner
2014-05-28 13:27       ` Guenter Roeck
2014-06-04 13:50     ` Andreas Werner
2014-06-04 13:50       ` Andreas Werner
2014-06-04 13:50       ` Andreas Werner
2014-05-27  9:07 ` [PATCH v2 2/3] drivers/watchdog/menf21bmc_wd: introduce MEN 14F021P00 BMC Watchdog driver Andreas Werner
2014-05-27  9:07   ` Andreas Werner
2014-05-27  9:08 ` [PATCH v2 3/3] drivers/leds/leds-menf21bmc: introduce MEN 14F021P00 BMC LED driver Andreas Werner
2014-05-27  9:08   ` Andreas Werner
2014-06-25 23:10   ` Bryan Wu
2014-06-26  7:34     ` AW: " Thumshirn, Johannes Tobias
2014-06-26  7:34       ` Thumshirn, Johannes Tobias
2014-06-26  7:34       ` Thumshirn, Johannes Tobias
2014-07-18 10:48     ` Andreas Werner
2014-07-18 10:48       ` Andreas Werner

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=20140528082404.GA10803@lee--X1 \
    --to=lee.jones@linaro.org \
    --cc=andreas.werner@men.de \
    --cc=cooloney@gmail.com \
    --cc=johannes.thumshirn@men.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    --cc=sameo@linux.intel.com \
    --cc=wim@iguana.be \
    /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.