mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Antonio Ospite <ospite@studenti.unina.it>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.arm.linux.org.uk,
	Daniel Ribeiro <drwyrm@gmail.com>
Subject: Re: [RFC] Freescale MC13783 PMIC support
Date: Tue, 11 Aug 2009 15:57:48 +0200	[thread overview]
Message-ID: <20090811135748.GR6108@pengutronix.de> (raw)
In-Reply-To: <20090811140500.2678b289.ospite@studenti.unina.it>

Hi Antonio,

On Tue, Aug 11, 2009 at 02:05:00PM +0200, Antonio Ospite wrote:
> On Tue, 11 Aug 2009 11:07:42 +0200
> Sascha Hauer <s.hauer@pengutronix.de> wrote:
> 
> > Hi all,
> > 
> > This series adds support for the Freescale MC13783 PMIC. The MC13783
> > is connected via SPI, the first patch adds basic support for it in
> > drivers/mfd. The rest of the patches can be applied independently.
> > Individual Maintainers are on Cc, the whole series can be found on
> > lkml and the Arm Linux Kernel mailing list.
> > Please ignore the previous mail which lacked the intrductory mail.
> > 
> > Sascha
> >
> 
> Hi Sascha,
> 
> the MC13783 is also named Atlas, isn't it?
> Maybe you can add this name somewhere in comments or in Kconfig entry
> to help greppers and web crawlers.
> 
> BTW, I only took a very brief look to some of your patches, and here's
> some humble thoughts, sorry if I don't comment patch by patch.
> 
> There is a driver queued for inclusion in 2.6.31 for the PCAP2
> PMIC, which is quite similar to MC13783. This driver uses the irq_chip
> mechanism to expose the PMIC IRQs to be used as general IRQs in
> sub-devices drivers (which you call client-devices AFAICS).

I can change the driver if there's consensus to do so.

> Also, it
> passed all the reviews so maybe you can give it a look to take some
> other solution already accepted by reviewers, like passing sub-devices
> via platform data (some of the phones which use PCAP2 don't have
> touchscreen, for instance),

This is indeed a useful feature. What I don't like about the pcap
approach is that the generation of the correct struct pcap_subdev
devices with the correct names is left to the board code.
Maybe we can also use the flags approach I already started with
MC13783_USE_TOUCHSCREEN which can be passed to the platform_data?

> generalize the driver so to handle multiple
> PMICs in one system (quite unlikely scenario?),

All functions take a struct mc13783 * so I think it should work with
multiple PMICs already.

> read actual pressure
> in TS driver.

This is left as an exercise for people who have the hardware which
supports this feature ;)

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

      parent reply	other threads:[~2009-08-11 13:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11  9:07 Sascha Hauer
2009-08-11  9:07 ` [PATCH 1/5] drivers/mfd: Add Freescale MC13783 driver Sascha Hauer
2009-08-11  9:07   ` [PATCH 2/5] [input] add mc13783 touchscreen driver Sascha Hauer
2009-08-11  9:07     ` [PATCH 3/5] [hwmon] add Freescale MC13783 adc driver Sascha Hauer
2009-08-11  9:07       ` [PATCH 4/5] [RTC] Add Freescale MC13783 RTC driver Sascha Hauer
2009-08-11  9:07         ` [PATCH 5/5] [regulator] Add a Freescale MC13783 regulator driver Sascha Hauer
2009-08-11 10:19           ` Mark Brown
2009-08-12  2:15     ` [PATCH 2/5] [input] add mc13783 touchscreen driver Dmitry Torokhov
2009-08-12 11:10       ` Sascha Hauer
2009-08-12 11:16         ` Mark Brown
2009-08-12 11:34           ` Sascha Hauer
2009-08-12 16:01         ` Dmitry Torokhov
2009-08-11 10:12   ` [PATCH 1/5] drivers/mfd: Add Freescale MC13783 driver Mark Brown
2009-08-11 11:38     ` Sascha Hauer
2009-08-11 10:15   ` Mark Brown
2009-08-11 12:05 ` [RFC] Freescale MC13783 PMIC support Antonio Ospite
2009-08-11 12:28   ` Mark Brown
2009-08-15  1:17     ` Daniel Ribeiro
2009-08-11 13:57   ` Sascha Hauer [this message]

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=20090811135748.GR6108@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=drwyrm@gmail.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ospite@studenti.unina.it \
    /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

all inboxes | Powered by JetHome®