On Tue, Mar 12, 2013 at 12:11:54PM -0700, Andrew Chew wrote:
> > From: Thierry Reding [mailto:thierry.red...@avionic-design.de]
> > Sent: Tuesday, March 12, 2013 12:01 AM
> > To: Andrew Chew
> > Cc: peter.ujfal...@ti.com; Alex Courbot; linux-omap@vger.kernel.org
> > Subject: Re: [PATCH 1/1] ARM: OM
On 2013-03-12 17:01, Archit Taneja wrote:
> So, what I'm saying is that we should stick to output->dispc_channel. We
> iterate through all the panels, and by using output->dispc_channel, we
> get the manager for an output, and map that manager to a crtc, and make
> sure the number of unique manage
On 03/12/13 18:40, Paul Walmsley wrote:
>
> Here are some basic OMAP test results for Linux v3.9-rc1.
> Logs and other details at:
>
> http://www.pwsan.com/omap/testlogs/test_v3.9-rc1/20130312100243/
[...]
> Failing tests: needing investigation
>
[...]
On 03/12/2013 05:33 PM, Levi Pearson wrote:
> I spent some more time looking at clk-twl6030.c, and it seems it just turns
> the
> twl6030 chip on when you ask it to enable the clock, and as far as I
> can tell that
> happens based on module dependencies? There aren't any explicit references to
>
From: Mugunthan V N
Date: Tue, 12 Mar 2013 14:46:33 +0530
> This patch serires implements the following features in CPSW driver
> * get/set phy link settings
> * interrupt pacing
> * get phy id via ioctl cmd SIOCGMIIPHY
>
> Changes from initial version
> * Made active-slave common for cpts, etht
Op 12 mrt. 2013, om 16:35 heeft Mark Jackson het
volgende geschreven:
> I'm just fighting an issue with ethernet on our custom AM335x board:-
>
> # uname -a
> Linux nanobone 3.9.0-rc2-00113-gd60f039 #139 Tue Mar 12 15:14:01 GMT 2013
> armv7l GNU/Linux
>
> Every now and then, the whole unit s
In the case where omap glue is loaded and musb core is not, glue->status
wont have a valid status if the phy drivers call omap_musb_mailbox. So
fixed the conditions here.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/usb/musb/omap2430.c | 11 +--
1 file changed, 5 insertions(+), 6
Having twl4030_usb_phy_init() (detects if a cable is connected before
twl4030 is probed) in twl4030 probe makes cable connect events to be
missed by musb glue, since it gets loaded after twl4030. Having
twl4030_usb_phy_init as a usb_phy ops lets twl4030_usb_phy_init to be
called when glue is ready.
No functional change. otg_set_vbus is already protected so removed the
check before calling otg_set_vbus.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/usb/musb/omap2430.c |9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/drivers/usb/musb/omap2430.c b/drivers/us
Some PHYs load too early (twl4030) making omap glue to miss cable connect events
if the board is booted with cable connected. So adding usb_phy_init in
omap2430_musb_init lets PHYs to report events once glue is ready.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/usb/musb/omap2430.c |2 +
Used devres APIs devm_request_threaded_irq and devm_regulator_get for
requesting irq and for getting regulator respectively.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/usb/otg/twl4030-usb.c | 28
1 file changed, 8 insertions(+), 20 deletions(-)
diff --git a
This series has some misc cleanup and fixes. The fix solves the cold
plug issue in omap3 which some have reported. Developed these patches on
Linux 3.9-rc2 after applying
http://www.spinics.net/lists/linux-usb/msg81563.html
(Grazvydas Ignotas patch series)
Tested for g_zero enumeration in pandabo
On 03/12/2013 11:22 PM, Andrew Chew wrote:
> The pwm-backlight driver now takes a mandatory regulator that is gotten
> during driver probe. Initialize a dummy regulator to satisfy this
> requirement.
I can test this tomorrow, but I have one comment:
>
> Signed-off-by: Andrew Chew
> ---
> arch
On 03/12/2013 11:22 PM, Andrew Chew wrote:
> Many backlights need to be explicitly enabled. Typically, this is done
> with a GPIO. For flexibility, we generalize the enable mechanism to a
> regulator.
>
> If an enable regulator is not needed, then a dummy regulator can be given
> to the backligh
With recent arm broadcast time clean-up from Mark Rutland, the dummy
broadcast device is always registered with timer subsystem. And since
the rating of the dummy clock event is very high, it is preferred
over a real broad-cast clock event.
This is a change in behavior from past and not an intende
Benoit,
Will you be queuing this patch series?
Thanks
Kishon
On Thursday 07 March 2013 07:05 PM, Kishon Vijay Abraham I wrote:
Hi Benoit,
Here are the dt data patches to get usb device functional in OMAP platforms.
All the patches deal with modifying arch/arm/boot except one which modifies
D
Hi Balbi,
On Sat, Mar 2, 2013 at 6:55 PM, Vivek Gautam wrote:
> Now that machines may select the mode of working of DWC3 (HOST only,
> GADGET only or DUAL_ROLE), lets set DWC3 mode based on that
> rather than fixing it to whatever DWC3 hardware says.
> This way we can skip initializing Gadget/Ho
On Wed, Mar 13, 2013 at 02:42:22PM +0530, Vivek Gautam wrote:
> Hi Balbi,
>
>
> On Sat, Mar 2, 2013 at 6:55 PM, Vivek Gautam wrote:
> > Now that machines may select the mode of working of DWC3 (HOST only,
> > GADGET only or DUAL_ROLE), lets set DWC3 mode based on that
> > rather than fixing it t
On Wed, Mar 13, 2013 at 2:44 PM, Felipe Balbi wrote:
> On Wed, Mar 13, 2013 at 02:42:22PM +0530, Vivek Gautam wrote:
>> Hi Balbi,
>>
>>
>> On Sat, Mar 2, 2013 at 6:55 PM, Vivek Gautam
>> wrote:
>> > Now that machines may select the mode of working of DWC3 (HOST only,
>> > GADGET only or DUAL_ROL
(Forgot to CC Thomas)
On Wednesday 13 March 2013 02:36 PM, Santosh Shilimkar wrote:
> With recent arm broadcast time clean-up from Mark Rutland, the dummy
> broadcast device is always registered with timer subsystem. And since
> the rating of the dummy clock event is very high, it is preferred
> o
On 18/02/13 08:19, Mugunthan V N wrote:
> CPDMA interrupts are not properly acknowledged which leads to interrupt
> storm, only cpdma interrupt 0 is acknowledged in Davinci CPDMA driver.
> Changed cpdma_ctlr_eoi api to acknowledge 1 and 2 interrupts which are
> used for rx and tx respectively.
>
>
On 13/03/13 08:44, Koen Kooi wrote:
>
> Op 12 mrt. 2013, om 16:35 heeft Mark Jackson het
> volgende geschreven:
>
>> I'm just fighting an issue with ethernet on our custom AM335x board:-
>>
>> # uname -a
>> Linux nanobone 3.9.0-rc2-00113-gd60f039 #139 Tue Mar 12 15:14:01 GMT 2013
>> armv7l GNU
On Wed, Mar 13, 2013 at 09:56:57AM +0100, Peter Ujfalusi wrote:
> On 03/12/2013 11:22 PM, Andrew Chew wrote:
[...]
> > +static void pwm_backlight_disable(struct backlight_device *bl)
> > +{
> > + struct pwm_bl_data *pb = dev_get_drvdata(&bl->dev);
> > +
> > + /* Bail if we are already disabled.
Hello GraÅžvydas,
On Mon, 11 Mar 2013, Grazvydas Ignotas wrote:
> For some unknown reason, allowing hwmod to control MIDLEMODE causes
> core_pwrdm to not hit idle states for musb in DM3730 at least.
> I've verified that setting any MIDLEMODE value other than "force
> standby" before enabling the d
Hi Santosh,
On Wed, Mar 13, 2013 at 09:28:22AM +, Santosh Shilimkar wrote:
> (Forgot to CC Thomas)
>
> On Wednesday 13 March 2013 02:36 PM, Santosh Shilimkar wrote:
> > With recent arm broadcast time clean-up from Mark Rutland, the dummy
> > broadcast device is always registered with timer su
Hi Aaro,
On Tue, 12 Mar 2013, Aaro Koskinen wrote:
> On Tue, Mar 12, 2013 at 04:40:19PM +, Paul Walmsley wrote:
> > * 2420N800: powers down 30 seconds after boot
> > - Presumably due to missing CBUS patches for watchdog control
> > - http://lkml.org/lkml/2012/9/3/265
> > - http://marc.i
Hi Igor,
On Wed, 13 Mar 2013, Igor Grinberg wrote:
> This should have been fixed by:
> ff95793 (ARM: OMAP3: cm-t3517: add MMC support)
>
> I also can't find the MMC rootfs boot log on your website.
Hmm, I thought I had switched the CM-T3517 over to use MMC booting, but
looks like it's still tr
On Tue, Mar 12, 2013 at 4:35 PM, Mark Jackson wrote:
> I'm just fighting an issue with ethernet on our custom AM335x board:-
>
> # uname -a
> Linux nanobone 3.9.0-rc2-00113-gd60f039 #139 Tue Mar 12 15:14:01 GMT 2013
> armv7l GNU/Linux
>
> Every now and then, the whole unit slows to a crawl. The
On Mon, Mar 11, 2013 at 08:50:22AM +0100, Sebastien Guiriec wrote:
> Update OMAP2+ driver in order to use OMAP DMA DT binding for OMAP2+.
> In case of DT boot snd_dmaengine_generic_pcm_open function is used.
>
> Signed-off-by: Sebastien Guiriec
Discarded since it breaks the build as a result of
On 13/03/13 10:32, Daniel Mack wrote:
> On Tue, Mar 12, 2013 at 4:35 PM, Mark Jackson wrote:
>> I'm just fighting an issue with ethernet on our custom AM335x board:-
>>
>> # uname -a
>> Linux nanobone 3.9.0-rc2-00113-gd60f039 #139 Tue Mar 12 15:14:01 GMT 2013
>> armv7l GNU/Linux
>>
>> Every now a
On 12/03/13 11:25, Artem Bityutskiy wrote:
> On Mon, 2013-03-04 at 16:42 +, Mark Jackson wrote:
>> I'm encountering an oops when remounting my ubifs volume as read/write.
>>
>> # mount -o remount,rw /
>> [ 89.434974] UBIFS assert failed in ubifs_write_node at 869 (pid 628)
>> [ 89.442122] [
On Wed, 2013-03-13 at 11:12 +, Mark Jackson wrote:
> > - if (c->space_fixup) {
> > - err = ubifs_fixup_free_space(c);
> > - if (err)
> > - goto out;
> > - }
> > -
> > mutex_unlock(&c->umount_mutex);
> > return err;
> >
>
> Sorry ... this just
On 13/03/13 11:20, Artem Bityutskiy wrote:
> On Wed, 2013-03-13 at 11:12 +, Mark Jackson wrote:
>>> - if (c->space_fixup) {
>>> - err = ubifs_fixup_free_space(c);
>>> - if (err)
>>> - goto out;
>>> - }
>>> -
>>> mutex_unlock(&c->umount_mutex);
>>>
On Wednesday 13 March 2013 03:46 PM, Mark Rutland wrote:
> Hi Santosh,
>
> On Wed, Mar 13, 2013 at 09:28:22AM +, Santosh Shilimkar wrote:
>> (Forgot to CC Thomas)
>>
>> On Wednesday 13 March 2013 02:36 PM, Santosh Shilimkar wrote:
>>> With recent arm broadcast time clean-up from Mark Rutland,
On 03/12/2013 06:07 PM, Alan Stern wrote:
> On Tue, 12 Mar 2013, Roger Quadros wrote:
>
>> The HSIC devices need to be kept in reset while the EHCI controller
>> is being initialized and only brought out of reset after the
>> initialization is complete, else HSIC devices will not be detected.
>
>
On 13/03/13 06:52, Lokesh Vutla wrote:
Commit {9a6eb31 ARM: hw_breakpoint: Debug powerdown support for self-hosted
debug} introduces debug powerdown support for self-hosted debug.
While merging the patch 'has_ossr' check was removed which
was needed for hardwares which doesn't support self-hosted
On Tue, Mar 12, 2013 at 2:52 PM, Cliff Brake wrote:
> On Tue, Mar 12, 2013 at 11:33 AM, Cliff Brake wrote:
>> On Tue, Mar 12, 2013 at 10:57 AM, Paul Walmsley wrote:
>>
>>> Are you in a position to test whether the patch works for you?
>>>
>>> I'd still like to find someone whose USB problem is f
On Wed, Mar 13, 2013 at 11:24:01AM +, Santosh Shilimkar wrote:
> On Wednesday 13 March 2013 03:46 PM, Mark Rutland wrote:
> > Hi Santosh,
> >
> > On Wed, Mar 13, 2013 at 09:28:22AM +, Santosh Shilimkar wrote:
> >> (Forgot to CC Thomas)
> >>
> >> On Wednesday 13 March 2013 02:36 PM, Santosh
Hi Dietmar,
On Wednesday 13 March 2013 05:35 PM, Dietmar Eggemann wrote:
On 13/03/13 06:52, Lokesh Vutla wrote:
Commit {9a6eb31 ARM: hw_breakpoint: Debug powerdown support for
self-hosted
debug} introduces debug powerdown support for self-hosted debug.
While merging the patch 'has_ossr' check wa
Move PHY initialization until after EHCI initialization is
complete, instead of initializing the PHYs first, shutting
them down again, and then initializing them a second time.
This fixes HSIC device detection.
Signed-off-by: Roger Quadros
CC: Alan Stern
---
drivers/usb/host/ehci-omap.c | 32
As it does almost nothing, get rid of omap_ehci_init()
and move the ehci->caps initialization part into probe().
Also remove the outdated TODO list from header.
Signed-off-by: Roger Quadros
CC: Alan Stern
---
drivers/usb/host/ehci-omap.c | 21 +
1 files changed, 1 inserti
On 03/12/2013 06:40 PM, Tony Lindgren wrote:
> * Roger Quadros [130312 04:47]:
>> Hi Tony,
>>
>> These patches provide the SoC side code required to support
>> the changes in the OMAP USB Host drivers done in [1], [2] & [3].
> ...
>
>> arch/arm/mach-omap2/board-3430sdp.c| 97 +
On Wed, 13 Mar 2013, Santosh Shilimkar wrote:
> On Wednesday 13 March 2013 02:36 PM, Santosh Shilimkar wrote:
> > With recent arm broadcast time clean-up from Mark Rutland, the dummy
> > broadcast device is always registered with timer subsystem. And since
> > the rating of the dummy clock event is
On Wed, 13 Mar 2013, Roger Quadros wrote:
> Move PHY initialization until after EHCI initialization is
> complete, instead of initializing the PHYs first, shutting
> them down again, and then initializing them a second time.
>
> This fixes HSIC device detection.
>
> Signed-off-by: Roger Quadros
On Wed, 13 Mar 2013, Roger Quadros wrote:
> As it does almost nothing, get rid of omap_ehci_init()
> and move the ehci->caps initialization part into probe().
>
> Also remove the outdated TODO list from header.
>
> Signed-off-by: Roger Quadros
> CC: Alan Stern
Acked-by: Alan Stern
--
To uns
On 03/12/2013 04:20 PM, Roger Quadros wrote:
> Adding Peter to the loop. I faintly remember him mentioning this issue before
> for beagle. We really need the deferred probe mechanism or we need to resort
> to device registering order.
Yes, BeagleBoard is a good example. Long story short: we have e
On Wednesday 13 March 2013 07:49 PM, Thomas Gleixner wrote:
> On Wed, 13 Mar 2013, Santosh Shilimkar wrote:
>> On Wednesday 13 March 2013 02:36 PM, Santosh Shilimkar wrote:
>>> With recent arm broadcast time clean-up from Mark Rutland, the dummy
>>> broadcast device is always registered with timer
Salut Jon,
On 03/12/2013 10:43 PM, Jon Hunter wrote:
> Salut Benoit!
>
> On 03/12/2013 06:00 AM, Benoit Cousson wrote:
>> + Seb G.
>>
>> Hi Jon,
>>
>> How to you plan to merge that series?
>
> Good question ... my thinking was that you or Tony would take 1/2 and
> once that is queued then I woul
On Wednesday 13 March 2013 05:55 PM, Mark Rutland wrote:
> On Wed, Mar 13, 2013 at 11:24:01AM +, Santosh Shilimkar wrote:
>> On Wednesday 13 March 2013 03:46 PM, Mark Rutland wrote:
>>> Hi Santosh,
[..]
>>>
>>> Is the problem that the dummy timer is being registered as the broadcast
>>> sourc
On 03/13/2013 05:17 PM, Peter Ujfalusi wrote:
> On 03/12/2013 04:20 PM, Roger Quadros wrote:
>> Adding Peter to the loop. I faintly remember him mentioning this issue before
>> for beagle. We really need the deferred probe mechanism or we need to resort
>> to device registering order.
>
> Yes, Bea
On 03/13/2013 10:35 AM, Benoit Cousson wrote:
> Salut Jon,
>
> On 03/12/2013 10:43 PM, Jon Hunter wrote:
>> Salut Benoit!
>>
>> On 03/12/2013 06:00 AM, Benoit Cousson wrote:
>>> + Seb G.
>>>
>>> Hi Jon,
>>>
>>> How to you plan to merge that series?
>>
>> Good question ... my thinking was that you
On 03/13/2013 04:17 PM, Peter Ujfalusi wrote:
> On 03/12/2013 04:20 PM, Roger Quadros wrote:
>> Adding Peter to the loop. I faintly remember him mentioning this issue before
>> for beagle. We really need the deferred probe mechanism or we need to resort
>> to device registering order.
>
> Yes, Bea
On 03/13/2013 04:50 PM, Jon Hunter wrote:
>
> On 03/13/2013 10:35 AM, Benoit Cousson wrote:
>> Salut Jon,
>>
>> On 03/12/2013 10:43 PM, Jon Hunter wrote:
>>> Salut Benoit!
>>>
>>> On 03/12/2013 06:00 AM, Benoit Cousson wrote:
+ Seb G.
Hi Jon,
How to you plan to merge that
On Wed, Mar 13, 2013 at 2:29 AM, Peter Ujfalusi wrote:
> On 03/12/2013 05:33 PM, Levi Pearson wrote:
>> I spent some more time looking at clk-twl6030.c, and it seems it just turns
>> the
>> twl6030 chip on when you ask it to enable the clock, and as far as I
>> can tell that
>> happens based on m
On Wed, Mar 13, 2013 at 03:44:03PM +, Santosh Shilimkar wrote:
> On Wednesday 13 March 2013 05:55 PM, Mark Rutland wrote:
> > On Wed, Mar 13, 2013 at 11:24:01AM +, Santosh Shilimkar wrote:
> >> On Wednesday 13 March 2013 03:46 PM, Mark Rutland wrote:
> >>> Hi Santosh,
>
> [..]
>
> >>>
> >
* Roger Quadros [130313 06:46]:
> On 03/12/2013 06:40 PM, Tony Lindgren wrote:
> > * Roger Quadros [130312 04:47]:
> >> Hi Tony,
> >>
> >> These patches provide the SoC side code required to support
> >> the changes in the OMAP USB Host drivers done in [1], [2] & [3].
> > ...
> >
> >> arch/arm
On 03/13/2013 06:24 PM, Tony Lindgren wrote:
> * Roger Quadros [130313 06:46]:
>> On 03/12/2013 06:40 PM, Tony Lindgren wrote:
>>> * Roger Quadros [130312 04:47]:
Hi Tony,
These patches provide the SoC side code required to support
the changes in the OMAP USB Host drivers done
Hi Javier,
On 03/02/2013 02:52 AM, Javier Martinez Canillas wrote:
> On Fri, Feb 15, 2013 at 11:03 AM, Cousson, Benoit wrote:
>> Hi Matthias,
>>
>>
>> On 2/15/2013 10:35 AM, Matthias Brugger wrote:
>>>
>>> 2013/1/26 Javier Martinez Canillas :
On Sat, Jan 26, 2013 at 4:16 PM, Matthias Br
Hi Sourav,
I've just applied your branch after a minor subject cleanup for consistency.
git://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git
for_3.10/dts
Regards,
Benoit
On 03/11/2013 04:42 PM, Sourav Poddar wrote:
> On Monday 11 March 2013 08:02 PM, Benoit Cousson wrote:
* Roger Quadros [130313 09:40]:
> On 03/13/2013 06:24 PM, Tony Lindgren wrote:
> > * Roger Quadros [130313 06:46]:
> >> On 03/12/2013 06:40 PM, Tony Lindgren wrote:
> >>> * Roger Quadros [130312 04:47]:
> Hi Tony,
>
> These patches provide the SoC side code required to support
> >
Santosh Shilimkar writes:
> Kevin,
>
> On Wednesday 13 February 2013 02:25 PM, Santosh Shilimkar wrote:
>> Current CPU PM code code make use of common cpu_suspend() path for all the
>> CPU power states which is not optimal. In fact cpu_suspend() path is needed
>> only when we put CPU power domain
On Wed, Mar 13, 2013 at 5:41 PM, Benoit Cousson wrote:
> Hi Javier,
>
> On 03/02/2013 02:52 AM, Javier Martinez Canillas wrote:
>> On Fri, Feb 15, 2013 at 11:03 AM, Cousson, Benoit wrote:
>>> Hi Matthias,
>>>
>>>
>>> On 2/15/2013 10:35 AM, Matthias Brugger wrote:
2013/1/26 Javier Martin
On Wed, Mar 13, 2013 at 4:24 AM, Suman Anna wrote:
> From: Omar Ramirez Luna
(...)
>
> Signed-off-by: Omar Ramirez Luna
> [s-a...@ti.com: Kconfig fixes for build errors]
> Signed-off-by: Suman Anna
> Acked-by: Tony Lindgren
> Signed-off-by: Linus Walleij
It's not like I care super-much, but
On Wednesday 13 March 2013 10:16 PM, Benoit Cousson wrote:
Hi Sourav,
I've just applied your branch after a minor subject cleanup for consistency.
git://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git
for_3.10/dts
Thanks Benoit!
Regards,
Benoit
On 03/11/2013 04:42 PM,
On Wed, 13 Mar 2013, Santosh Shilimkar wrote:
> On Wednesday 13 March 2013 07:49 PM, Thomas Gleixner wrote:
> > Though making the rating of the dummy lower is definitely a good
> > thing, so a real hardware device which is detected later can replace
> > the dummy device. So yes, the rating should b
I don't know is this good or bad idea, thus RFC.
I got this idea after noticing that McBSP DMA channel definitions are no
longer used for OMAP2 and EAC DMA channel were never used in upstream.
Scripts here are used to remove all of those unused ones.
Build tested with omap1_defconfig and omap2plu
Many of these channel definitions have became unused or were never used
so remove unused definitions from arch/arm/mach-omap1/dma.h using a script
below. See also notes in commit 8c4cc00
("ARM: OMAP1: DMA: Moving OMAP1 DMA channel definitions to mach-omap1")
for removing remaining ones.
egrep '#de
Many of these channel definitions have became unused or were never used
so remove unused definitions from arch/arm/mach-omap2/dma.h using a script
below. See also notes in commit d5e7c86
("ARM: OMAP2+: DMA: Moving OMAP2+ DMA channel definitions to mach-omap2")
for removing remaining ones.
egrep '#
> > +/* Dummy regulator for pwm-backlight driver */ static struct
> > +regulator_consumer_supply backlight_supply =
> > + REGULATOR_SUPPLY("enable", NULL);
>
> 'enable' is just too generic, the device name should be also provided:
> REGULATOR_SUPPLY("enable", "pwm-backlight");
You're righ
On Wed, Mar 13, 2013 at 01:38:31PM -0700, Andrew Chew wrote:
> > > +/* Dummy regulator for pwm-backlight driver */ static struct
> > > +regulator_consumer_supply backlight_supply =
> > > + REGULATOR_SUPPLY("enable", NULL);
> >
> > 'enable' is just too generic, the device name should be also provid
> > +static void pwm_backlight_enable(struct backlight_device *bl) {
> > + struct pwm_bl_data *pb = dev_get_drvdata(&bl->dev);
> > +
> > + /* Bail if we are already enabled. */
> > + if (pb->enabled)
> > + return;
> > +
> > + pwm_enable(pb->pwm);
> > +
> > + if (regulator_enable
> From: Thierry Reding [mailto:thierry.red...@avionic-design.de]
> Sent: Wednesday, March 13, 2013 1:59 PM
> To: Andrew Chew
> Cc: Peter Ujfalusi; Alex Courbot; linux-omap@vger.kernel.org
> Subject: Re: [PATCH 1/2 v2] ARM: OMAP: board-4430sdp: Provide regulator
> to pwm-backlight
>
> * PGP Signed
> On Wed, Mar 13, 2013 at 4:24 AM, Suman Anna wrote:
>
> > From: Omar Ramirez Luna
> (...)
> >
> > Signed-off-by: Omar Ramirez Luna
> > [s-a...@ti.com: Kconfig fixes for build errors]
> > Signed-off-by: Suman Anna
> > Acked-by: Tony Lindgren
> > Signed-off-by: Linus Walleij
>
> It's not lik
On Wed, Mar 13, 2013 at 02:10:16PM -0700, Andrew Chew wrote:
> > > +static void pwm_backlight_enable(struct backlight_device *bl) {
> > > + struct pwm_bl_data *pb = dev_get_drvdata(&bl->dev);
> > > +
> > > + /* Bail if we are already enabled. */
> > > + if (pb->enabled)
> > > + return;
> >
> On Wed, Mar 13, 2013 at 02:10:16PM -0700, Andrew Chew wrote:
> > > > +static void pwm_backlight_enable(struct backlight_device *bl) {
> > > > + struct pwm_bl_data *pb = dev_get_drvdata(&bl->dev);
> > > > +
> > > > + /* Bail if we are already enabled. */
> > > > + if (pb->enabled
On Wed, Mar 13, 2013 at 10:47 AM, Kishon Vijay Abraham I wrote:
> In the case where omap glue is loaded and musb core is not, glue->status
> wont have a valid status if the phy drivers call omap_musb_mailbox. So
> fixed the conditions here.
There already seems to be another patch named "usb: musb
On Wed, Mar 13, 2013 at 10:47 AM, Kishon Vijay Abraham I wrote:
> This series has some misc cleanup and fixes. The fix solves the cold
> plug issue in omap3 which some have reported. Developed these patches on
> Linux 3.9-rc2 after applying
> http://www.spinics.net/lists/linux-usb/msg81563.html
>
Many backlights are enabled via GPIO. We can generalize the GPIO to a
fixed regulator.
The enable regulator needs to be mandatory because there was no good way
to determine the difference between opting out of the regulator, and probe
deferral.
This series of patches is intended to add a dummy r
The pwm-backlight driver now takes a mandatory regulator that is gotten
during driver probe. Initialize a dummy regulator to satisfy this
requirement.
Signed-off-by: Andrew Chew
---
Changed the device name of the backlight regulator supply to "pwm-backlight",
per Peter's comment.
Changed the na
Many backlights need to be explicitly enabled. Typically, this is done
with a GPIO. For flexibility, we generalize the enable mechanism to a
regulator.
If an enable regulator is not needed, then a dummy regulator can be given
to the backlight driver. If a GPIO is used to enable the backlight,
t
Hello guys,
This is a resend of my quite old patch
( https://patchwork.kernel.org/patch/1130991/ ) that
was submitted 9 months ago but I suddenly found that
it is still not picked up in the mainline.
It will be needed for OMAP USB Host HW errata (i687)
implementation that will be sent in a separat
This patch adds missing CONTROL_SMART2IO_PADCONF_2 register
definition
Signed-off-by: Ruslan Bilovol
---
arch/arm/mach-omap2/ctrl_module_pad_core_44xx.h | 45 +++
1 file changed, 45 insertions(+)
diff --git a/arch/arm/mach-omap2/ctrl_module_pad_core_44xx.h
b/arch/arm/mach
binMk5ShfA205.bin
Description: iso-8859-1
if pwrdm_read_pwrst returns negative number, curr_pwrst can not notice it.
since really need check curr_pwrst whether is negative,
need let the check valid in _pwrdm_save_clkdm_state_and_activate.
and also better to check the return value of pwrdm_read_pwrst, firstly.
Signed-off-by: C
On Thursday 14 March 2013 03:29 AM, Grazvydas Ignotas wrote:
On Wed, Mar 13, 2013 at 10:47 AM, Kishon Vijay Abraham I wrote:
In the case where omap glue is loaded and musb core is not, glue->status
wont have a valid status if the phy drivers call omap_musb_mailbox. So
fixed the conditions here.
On Wednesday 13 March 2013 11:12 PM, Kevin Hilman wrote:
> Santosh Shilimkar writes:
>
>> Kevin,
>>
>> On Wednesday 13 February 2013 02:25 PM, Santosh Shilimkar wrote:
>>> Current CPU PM code code make use of common cpu_suspend() path for all the
>>> CPU power states which is not optimal. In fact
On Thursday 14 March 2013 12:01 AM, Thomas Gleixner wrote:
> On Wed, 13 Mar 2013, Santosh Shilimkar wrote:
>> On Wednesday 13 March 2013 07:49 PM, Thomas Gleixner wrote:
>>> Though making the rating of the dummy lower is definitely a good
>>> thing, so a real hardware device which is detected later
On Wednesday 13 March 2013 10:16 PM, Benoit Cousson wrote:
> Hi Sourav,
>
> I've just applied your branch after a minor subject cleanup for consistency.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git
> for_3.10/dts
>
Thanks for the tree Benoit. I shall update my v2
Used devres APIs devm_request_threaded_irq and devm_regulator_get for
requesting irq and for getting regulator respectively.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/usb/otg/twl4030-usb.c | 28
1 file changed, 8 insertions(+), 20 deletions(-)
diff --git a
Some PHYs load too early (twl4030) making omap glue to miss cable connect events
if the board is booted with cable connected. So adding usb_phy_init in
omap2430_musb_init lets PHYs to report events once glue is ready.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/usb/musb/omap2430.c |2 +
Having twl4030_usb_phy_init() (detects if a cable is connected before
twl4030 is probed) in twl4030 probe makes cable connect events to be
missed by musb glue, since it gets loaded after twl4030. Having
twl4030_usb_phy_init as a usb_phy ops lets twl4030_usb_phy_init to be
called when glue is ready.
This series has some misc cleanup and fixes. The fix solves the cold
plug issue in omap3 which some have reported. Developed these patches on
fixes-for-v3.9-rc3 after applying
http://www.spinics.net/lists/linux-usb/msg81563.html
(Grazvydas Ignotas patch series)
Tested for g_zero enumeration in pa
No functional change. otg_set_vbus is already protected so removed the
check before calling otg_set_vbus.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/usb/musb/omap2430.c |9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/drivers/usb/musb/omap2430.c b/drivers/us
93 matches
Mail list logo