linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: yong.shen@linaro.org (Yong Shen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] support PMIC mc13892
Date: Tue, 7 Dec 2010 10:50:30 +0800	[thread overview]
Message-ID: <AANLkTimvRVZOzRSxHWCmPKh66oap2CSBen2LW3gucqUN@mail.gmail.com> (raw)
In-Reply-To: <20101206114022.249671bc@archvile>

Hi David,

On Mon, Dec 6, 2010 at 6:40 PM, David Jander <david.jander@protonic.nl> wrote:
>
> Hi Yong,
>
> On Mon, 6 Dec 2010 14:25:35 +0800 <yong.shen@freescale.com> wrote:
>>[...]
>> --- /dev/null
>> +++ b/include/linux/mfd/mc13892.h
>> @@ -0,0 +1,38 @@
>> +/*
>> + * Copyright 2010 Yong Shen <yong.shen@linaro.org>
>> + *
>> + * This program is free software; you can redistribute it and/or modify it
>> under
>> + * the terms of the GNU General Public License version 2 as published by the
>> + * Free Software Foundation.
>> + */
>> +
>> +#ifndef __LINUX_MFD_MC13892_H
>> +#define __LINUX_MFD_MC13892_H
>> +#include <linux/mfd/mc13xxx.h>
>> +
>> +#define MC13892_SW1 ? ? ? ? ?0
>> +#define MC13892_SW2 ? ? ? ? ?1
>> +#define MC13892_SW3 ? ? ? ? ?2
>> +#define MC13892_SW4 ? ? ? ? ?3
>> +#define MC13892_SWBST ? ? ? ?4
>> +#define MC13892_VIOHI ? ? ? ?5
>> +#define MC13892_VPLL 6
>> +#define MC13892_VDIG 7
>> +#define MC13892_VSD ?8
>> +#define MC13892_VUSB2 ? ? ? ?9
>> +#define MC13892_VVIDEO ? ? ? 10
>> +#define MC13892_VAUDIO ? ? ? 11
>> +#define MC13892_VCAM 12
>> +#define MC13892_VGEN1 ? ? ? ?13
>> +#define MC13892_VGEN2 ? ? ? ?14
>> +#define MC13892_VGEN3 ? ? ? ?15
>> +#define MC13892_VUSB 16
>> +#define MC13892_GPO1 17
>> +#define MC13892_GPO2 18
>> +#define MC13892_GPO3 19
>> +#define MC13892_GPO4 20
>> +#define MC13892_PWGT1SPI ? ? 21
>> +#define MC13892_PWGT2SPI ? ? 22
>> +#define MC13892_VCOINCELL ? ?23
>> +
>> +#endif
>
> I suppose these are needed outside the driver .c file? If so, can't these go in
> linux/mfd/mc13xxx.h?

This head is only for regulator usage, however linux/mfd/mc13xxx.h is
for multiple functions.
> The platform-data struct is in there too, so why not put the corresponding
> defines there also?
> For other subsystems, those defines that are common are prefixed MC13XXX_ and
> those that are individual, get MC13892_ or MC13783_. This makes it also easier
> and less intrusive to add support for future chips in this series....
>
This is debatable. Previously, I put it under
include/linux/regulator/, but after reviewing comments from other guys
(see previous email for mc13783), I also realized that this is private
for mc13xxx regulator drivers, basically no other users, so it is
better to stay in drivers/regulator/.

Thanks
Yong

> Best regards,
>
> --
> David Jander
> Protonic Holland.
>

  reply	other threads:[~2010-12-07  2:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-06  6:25 [PATCH] support PMIC mc13892 yong.shen at freescale.com
2010-12-06  7:22 ` Uwe Kleine-König
2010-12-07  2:41   ` Yong Shen
2010-12-07  7:57   ` Yong Shen
2010-12-07  8:02     ` Uwe Kleine-König
2010-12-06 10:40 ` David Jander
2010-12-07  2:50   ` Yong Shen [this message]
2010-12-06 10:55 ` Arnaud Patard (Rtp)
2010-12-06 11:42   ` Alberto Panizzo
2010-12-06 11:55     ` Arnaud Patard (Rtp)
2010-12-06 13:12       ` Alberto Panizzo
2010-12-07  2:52   ` Yong Shen
2010-12-06 21:54 ` Marc Reilly
2010-12-07  7:14   ` [PATCH] Added i2c support for mc13xxx-core Marc Reilly
2010-12-07  8:32     ` Yong Shen
2010-12-07 10:09       ` Marc Reilly
2010-12-08  6:24     ` Yong Shen
2010-12-08  8:07       ` Marc Reilly
2010-12-08 10:42         ` Uwe Kleine-König
2010-12-07  7:23   ` Marc Reilly
2010-12-07  7:23   ` Marc Reilly

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=AANLkTimvRVZOzRSxHWCmPKh66oap2CSBen2LW3gucqUN@mail.gmail.com \
    --to=yong.shen@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).