From: Arnd Bergmann <arnd@arndb.de>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Donggeun Kim <dg77.kim@samsung.com>,
linux-kernel@vger.kernel.org,
broonie@opensource.wolfsonmicro.com, gregkh@suse.de,
akpm@linux-foundation.org, kyungmin.park@samsung.com,
myungjoo.ham@samsung.com
Subject: Re: [PATCH 2/2] misc: add driver support for MAX8997 MUIC
Date: Wed, 14 Dec 2011 16:35:54 +0000 [thread overview]
Message-ID: <201112141635.55071.arnd@arndb.de> (raw)
In-Reply-To: <20111212170846.GO13952@sortiz-mobl>
On Monday 12 December 2011, Samuel Ortiz wrote:
> On Thu, Nov 24, 2011 at 06:12:18PM +0900, Donggeun Kim wrote:
> > The MUIC function in MAX8997 device can be used as
> > a USB port detector and switch.
> > This patch supports the MUIC feature of MAX8997.
>
> I'm queueing this one to my for-next branch as it depends on your previous MFD
> patch.
> I'm also cc'ing Arnd in case he has some objections.
Thanks for the notification!
First of all, every new user space interface including new sysfs files
and uevent messages needs documentation in the Documentation/ABI
directory.
The part that is not clear to me is how this new driver fits in
with the first fsa9480 driver and the currently discussed extcon
subsystem, apparently all written by the same team at Samsung.
Is this misc driver still useful when the extcon framework gets
merged?
I very much believe that we should avoid introducing user interfaces
in a driver specific way when we have multiple pieces of hardware
that try to do the same thing. The extcon subsystem seems to handle
this correctly on the high-level (I have not done a detailed
review yet but I trust that it will be ok), so I don't understand
why we want another driver for the MAX8997 MUIC.
Arnd
next prev parent reply other threads:[~2011-12-14 16:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 9:12 [PATCH 1/2] MFD: MAX8997: add platform data for MAX8997 MUIC driver Donggeun Kim
2011-11-24 9:12 ` [PATCH 2/2] misc: add driver support for MAX8997 MUIC Donggeun Kim
2011-11-28 23:48 ` Andrew Morton
2011-11-29 0:02 ` Kyungmin Park
2011-11-29 9:59 ` Samuel Ortiz
2011-12-12 17:08 ` Samuel Ortiz
2011-12-14 16:35 ` Arnd Bergmann [this message]
2011-12-12 17:06 ` [PATCH 1/2] MFD: MAX8997: add platform data for MAX8997 MUIC driver Samuel Ortiz
-- strict thread matches above, loose matches on Subject: below --
2011-12-15 0:32 Re: [PATCH 2/2] misc: add driver support for MAX8997 MUIC MyungJoo Ham
2011-12-15 15:34 ` Arnd Bergmann
2011-12-15 17:25 ` Samuel Ortiz
2011-12-16 5:13 함명주
2011-12-16 13:58 ` Arnd Bergmann
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=201112141635.55071.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dg77.kim@samsung.com \
--cc=gregkh@suse.de \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=sameo@linux.intel.com \
/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