This patch adds support for the tps65217 charger driver. This driver is
responsible for controlling the charger aspect of the tps65217 mfd.
Currently, this mainly consists of turning on and off the charger, but
some other features of the charger can be supported through this driver.
Hi all,
The following series add initial support for tps65217 battery charger. This
series is a first attempt and will have mistake so all comments and
suggestions are welcomed.
Best regards,
Enric Balletbo i Serra (3):
devicetree: Add TPS65217 charger binding.
power_supply: Add support for
The TPS65217 charger is a subnode of the TPS65217 MFD.
Signed-off-by: Enric Balletbo i Serra
---
.../devicetree/bindings/power_supply/tps65217_charger.txt| 12
1 file changed, 12 insertions(+)
create mode 100644
On Mon, Sep 07, 2015 at 01:23:01PM +0300, Roger Quadros wrote:
> On 07/09/15 04:23, Peter Chen wrote:
> > On Mon, Aug 24, 2015 at 04:21:18PM +0300, Roger Quadros wrote:
> >> + * This is used by the USB Host stack to register the Host controller
> >> + * to the OTG core. Host controller must not be
Add tps65217 battery charger subdevice.
Signed-off-by: Enric Balletbo i Serra
---
drivers/mfd/tps65217.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/mfd/tps65217.c b/drivers/mfd/tps65217.c
index 55add04..d32b5442 100644
---
Hello,
On Wednesday 05 August 2015 07:13 PM, Kishon Vijay Abraham I wrote:
> One of the lines from PCF857x is connected to the vdd line of MMC1
> in DRA74x and DRA72x EVMs and is modelled as a regulator. If PCF857x
> is not made as built-in, the regulator_get in omap_hsmmc fails making
> it
On Mon, Sep 07, 2015 at 12:57:21PM +0300, Roger Quadros wrote:
> On 07/09/15 04:24, Peter Chen wrote:
> > On Mon, Aug 24, 2015 at 04:21:15PM +0300, Roger Quadros wrote:
> >> This is to prevent missing symbol build error if OTG is
> >> enabled (built-in) and HCD core (CONFIG_USB) is module.
> >>
>
On 08/09/15 09:54, Peter Chen wrote:
> On Mon, Sep 07, 2015 at 12:57:21PM +0300, Roger Quadros wrote:
>> On 07/09/15 04:24, Peter Chen wrote:
>>> On Mon, Aug 24, 2015 at 04:21:15PM +0300, Roger Quadros wrote:
This is to prevent missing symbol build error if OTG is
enabled (built-in) and
Hi Peter,
Thank you for the patch.
While trying to port the omap_vout driver to the DMA engine API I noticed that
the driver makes use of double-indexed transfers, which are not supported by
the omap-dma driver. I haven't checked in details what would be required, but
the interleaved API
Hi,
this is a longstanding problem I'm seeing since the very beginning,
which was around 3.12 or so (when I've first got the hardware) and it
seems 4.2 is affected by it still. Basically what happens is Xorg
randomly segfaults at some "impossible" location. I don't have the
details at the moment
On 08/09/15 11:31, Peter Chen wrote:
> On Mon, Sep 07, 2015 at 01:23:01PM +0300, Roger Quadros wrote:
>> On 07/09/15 04:23, Peter Chen wrote:
>>> On Mon, Aug 24, 2015 at 04:21:18PM +0300, Roger Quadros wrote:
+ * This is used by the USB Host stack to register the Host controller
+ * to
Laurent,
On 09/08/2015 02:24 PM, Laurent Pinchart wrote:
> Hi Peter,
>
> Thank you for the patch.
>
> While trying to port the omap_vout driver to the DMA engine API I noticed
> that
> the driver makes use of double-indexed transfers, which are not supported by
> the omap-dma driver. I
* Mugunthan V N [150907 02:50]:
> In DRA72x EVM, by default slave 1 is connected to the onboard
> phy, but slave 2 pins are also muxed with video input module
> which is controlled by pcf857x gpio and currently to select slave
> 0 to connect to phy gpio hogging is used, but
* Kevin Hilman [150908 11:36]:
> On Wed, Sep 2, 2015 at 6:07 AM, Tony Lindgren wrote:
> > * Neil Brown [150901 23:23]:
> >> Kevin Hilman writes:
> >>
> >> > ping... this boot failure has now landed in mainline
> >>
> >>
* Grazvydas Ignotas [150908 13:44]:
> On Tue, Sep 8, 2015 at 4:38 PM, Tony Lindgren wrote:
> > * Grazvydas Ignotas [150908 05:50]:
> >> Hi,
> >>
> >> this is a longstanding problem I'm seeing since the very beginning,
> >> which was around
On Tue, Sep 8, 2015 at 4:38 PM, Tony Lindgren wrote:
> * Grazvydas Ignotas [150908 05:50]:
>> Hi,
>>
>> this is a longstanding problem I'm seeing since the very beginning,
>> which was around 3.12 or so (when I've first got the hardware) and it
>> seems 4.2
On Thu, Sep 3, 2015 at 7:31 PM, Tony Lindgren wrote:
> If gpio-omap probe fails with -EPROBE_DEFER, the GPIO numbering
> keeps increasing. Only increase the gpio count if gpiochip_add()
> was successful as otherwise the numbers will increase for each
> probe attempt.
>
> Cc:
On Thu, Sep 3, 2015 at 7:34 PM, Tony Lindgren wrote:
> If the gpio driver is confused about the numbers for gpio-ranges,
> pinctrl_ready_for_gpio_range() may get called with invalid GPIO
> causing a NULL pointer exception. Let's instead provide a warning
> that allows fixing
On Tue, 8 Sep 2015, Roger Quadros wrote:
> On 08/09/15 11:31, Peter Chen wrote:
> > On Mon, Sep 07, 2015 at 01:23:01PM +0300, Roger Quadros wrote:
> >> On 07/09/15 04:23, Peter Chen wrote:
> >>> On Mon, Aug 24, 2015 at 04:21:18PM +0300, Roger Quadros wrote:
> + * This is used by the USB Host
From: Vignesh R
TIPWMSS is present on TI's DRA7x and
AM437x SoCs. Enable its usage.
Instead of adding each SoC individually,
use the more generic ARCH_OMAP2PLUS
instead.
Signed-off-by: Vignesh R
Signed-off-by: Sekhar Nori
---
On Mon, Sep 07, 2015 at 12:32:10PM +0200, Yegor Yefremov wrote:
> On Mon, Aug 31, 2015 at 7:41 PM, Felipe Balbi wrote:
> > Hi,
> >
> > On Mon, Aug 31, 2015 at 11:41:59AM -0500, Felipe Balbi wrote:
> >> On Mon, Aug 31, 2015 at 03:11:58PM +0200, Yegor Yefremov wrote:
> >> > Hi Felipe,
On Tue, Sep 08, 2015 at 03:25:25PM +0300, Roger Quadros wrote:
>
>
> On 08/09/15 11:31, Peter Chen wrote:
> > On Mon, Sep 07, 2015 at 01:23:01PM +0300, Roger Quadros wrote:
> >> On 07/09/15 04:23, Peter Chen wrote:
> >>> On Mon, Aug 24, 2015 at 04:21:18PM +0300, Roger Quadros wrote:
> + *
On Mon, Aug 24, 2015 at 04:21:21PM +0300, Roger Quadros wrote:
> The existing usb_add/remove_hcd() functionality
> remains unchanged for non-OTG devices. For OTG
> devices they only register the HCD with the OTG core.
>
> Introduce usb_otg_add/remove_hcd() for use by OTG core.
> These functions
On Sun, Sep 06, 2015 at 04:41:10PM -0700, Guenter Roeck wrote:
> On Thu, Sep 03, 2015 at 03:25:11PM +0530, Kishon Vijay Abraham I wrote:
> > PBIAS regulator is required for MMC module in OMAP2, OMAP3, OMAP4,
> > OMAP5 and DRA7 SoCs. Enable it here.
> >
> > Signed-off-by: Kishon Vijay Abraham I
* Grazvydas Ignotas [150908 05:50]:
> Hi,
>
> this is a longstanding problem I'm seeing since the very beginning,
> which was around 3.12 or so (when I've first got the hardware) and it
> seems 4.2 is affected by it still. Basically what happens is Xorg
> randomly segfaults at
On Fri, Aug 28, 2015 at 8:44 PM, Tony Lindgren wrote:
> Currently we gpio-omap breaks if gpiochip_add() returns -EPROBE_DEFER:
>
> [0.57] gpiochip_add: GPIOs 0..31 (gpio) failed to register
> [0.57] omap_gpio 4831.gpio: Could not register gpio chip -517
>
Alan,
On 08/09/15 17:34, Alan Stern wrote:
> On Tue, 8 Sep 2015, Roger Quadros wrote:
>
>> On 08/09/15 11:31, Peter Chen wrote:
>>> On Mon, Sep 07, 2015 at 01:23:01PM +0300, Roger Quadros wrote:
On 07/09/15 04:23, Peter Chen wrote:
> On Mon, Aug 24, 2015 at 04:21:18PM +0300, Roger
On Wed, Sep 2, 2015 at 6:07 AM, Tony Lindgren wrote:
> * Neil Brown [150901 23:23]:
>> Kevin Hilman writes:
>>
>> > ping... this boot failure has now landed in mainline
>>
>> sorry, I'm on leave at the moment and travelling so I'm unlikely
28 matches
Mail list logo