All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Sebastian Reichel <sre@kernel.org>,
	Richard Purdie <rpurdie@rpsys.net>,
	Jacek Anaszewski <jacek.anaszewski@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] leds: cpcap: new driver
Date: Mon, 6 Mar 2017 15:38:59 -0800	[thread overview]
Message-ID: <20170306233859.GQ20572@atomide.com> (raw)
In-Reply-To: <20170306221147.GA24272@amd>

Hi,

* Pavel Machek <pavel@ucw.cz> [170306 14:13]:
> > Motorola CPCAP is a PMIC found in multiple smartphones.
> > This driver adds support for the chip's LED controllers.
> > It has explicit support for all controllers used by the
> > Droid 4. Since no datasheets are available the other
> > available controllers are not supported until somebody
> > verified, that the register layout matches.
> 
> This of course leads me to two questions:
> 
> 1) Where can I get Droid 4?

There's plenty of them available used for a few tens of $/€
on ebay as it was a popular phone on Verizon network in the
US. It works fine on 3G networks outside the U.S, 4G probably
only works in the US.

> 2) How well is it supported?

Basic things like UART, MMC, eMMC, WLAN, I2C, SPI, HDMI,
clocks, PMIC and regulators work with lots of other dts
configured devices heading into tomorrow's Linux next in my
dts branch omap-for-v4.12/dt-droid4. LCD related patches have
been posted but are not yet in next.

Things that currently don't work are ADC, USB, charging,
audio and modems. The modems are on OHCI/EHCI, audio is on the
PMIC similar to the twl4030. I'm slowly working on a driver for
ADC/USB/charging with few more issues to sort out. I do have
ADC/USB/charging working with my current hacks though.

I've posted some notes at:

http://muru.com/linux/d4/

And Sebastian has information in his blog including a device
status matrix at:

http://elektranox.org/droid4/

Cheers,

Tony

  reply	other threads:[~2017-03-06 23:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-05 17:22 [PATCH 1/2] leds: cpcap: new driver Sebastian Reichel
     [not found] ` <20170305172234.24120-1-sre-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-03-05 17:22   ` [PATCH 2/2] ARM: dts: motorola-cpcap-mapphone: add LEDs Sebastian Reichel
2017-03-05 17:22     ` Sebastian Reichel
2017-03-06 16:11     ` Tony Lindgren
2017-03-06 21:41   ` [PATCH 1/2] leds: cpcap: new driver Jacek Anaszewski
2017-03-06 21:41     ` Jacek Anaszewski
2017-03-06 22:11 ` Pavel Machek
2017-03-06 23:38   ` Tony Lindgren [this message]
     [not found]     ` <20170306233859.GQ20572-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2017-03-07 11:55       ` Pavel Machek
2017-03-07 11:55         ` Pavel Machek
2017-03-07 16:26         ` Tony Lindgren
2017-03-07 16:26           ` Tony Lindgren
2017-04-11 20:20           ` Pavel Machek
2017-03-07 17:19   ` Sebastian Reichel
2017-03-07 17:19     ` Sebastian Reichel
2017-04-11 20:19     ` Pavel Machek
2017-04-11 20:19       ` Pavel Machek

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=20170306233859.GQ20572@atomide.com \
    --to=tony@atomide.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jacek.anaszewski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pavel@ucw.cz \
    --cc=robh+dt@kernel.org \
    --cc=rpurdie@rpsys.net \
    --cc=sre@kernel.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 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.