On Fri, 10 Apr 2015 13:56:54 +0530 Keerthy wrote:
> >>> How do we know that all systems have this external clock and that it
> >>> works OK?
> >>>
> >>
> >> AM335 and AM43X have the external clock feature which we choose using
> >> RTC_OSC_REG. I verified it works OK by seeing the RTC seconds tic
On Tue, 07 Apr 2015 16:27:44 -0700 Kevin Hilman wrote:
> >> > It should all be there today?
> >>
> >> Nope.
> >
> > huh, I swear I did an mmotm yesterday.
>
> Well, based on the timestamp of the mmotm dir on ozlabs, it appears you
> did. That's why I was confused why the gcc-473 patches from
On Tue, 07 Apr 2015 15:41:32 -0700 Kevin Hilman wrote:
> Andrew Morton writes:
>
> > On Tue, 7 Apr 2015 10:57:52 -0700 Kevin Hilman wrote:
> >
> >> > The diff below[2] on top of yours compiles fine here and at least covers
> >> > the compilers I *kno
On Tue, 7 Apr 2015 10:57:52 -0700 Kevin Hilman wrote:
> > The diff below[2] on top of yours compiles fine here and at least covers
> > the compilers I *know* to trigger the ICE.
>
> I see my fix in your mmots since last Thurs (4/2), but it's not in
> mmotm (last updated today) so today's linux-n
On Wed, 18 Mar 2015 15:48:02 -0700 Tony Lindgren wrote:
> Looks like dm81xx can only do 32-bit fifo reads like am35x. Let's set
> up musb-dsps with a custom read_fifo function based on the compatible
> flag.
>
> Otherwise we can get the following errors when starting dhclient on a
> asix USB Eth
On Wed, 01 Apr 2015 10:47:49 +0100 Marc Zyngier wrote:
> > -static int unmap_and_move(new_page_t get_new_page, free_page_t
> > put_new_page,
> > - unsigned long private, struct page *page, int force,
> > - enum migrate_mode mode)
> > +static noinline int unmap
On Tue, 3 Mar 2015 15:12:02 +0530 Keerthy wrote:
> Add external 32k clock feature. The internal clock will be gated during
> suspend.
> Hence make use of the external 32k clock so that rtc is functional accross
> suspend/resume.
>
> ...
>
> @@ -446,6 +449,7 @@ static const struct omap_rtc_devic
On Wed, 29 Oct 2014 13:50:05 +0100 Johan Hovold wrote:
> On Tue, Oct 28, 2014 at 09:36:33AM +0100, Johan Hovold wrote:
> > On Mon, Oct 27, 2014 at 03:40:31PM -0700, Andrew Morton wrote:
> > > On Mon, 27 Oct 2014 09:09:28 +0100 Johan Hovold wrote:
>
> > But in general
On Tue, 28 Oct 2014 09:36:33 +0100 Johan Hovold wrote:
> > But it doesn't explain *why* we want the alarm to trigger before
> > returning.
>
> Should we really require every power-off handler to document arch
> behaviour (even if its inconsistent and currently undocumented); in
> this case that
On Fri, 24 Oct 2014 21:55:32 +0200 Johan Hovold wrote:
> On Fri, Oct 24, 2014 at 02:44:42PM -0500, Felipe Balbi wrote:
> > On Fri, Oct 24, 2014 at 09:36:55PM +0200, Johan Hovold wrote:
> > > On Fri, Oct 24, 2014 at 02:29:48PM -0500, Felipe Balbi wrote:
> > > > Hi,
> > > >
> > > > On Fri, Oct 24,
On Mon, 27 Oct 2014 09:09:28 +0100 Johan Hovold wrote:
> Add new property "ti,system-power-controller" to register the RTC as a
> power-off handler.
>
> Some RTC IP revisions can control an external PMIC via the pmic_power_en
> pin, which can be configured to transition to OFF on ALARM2 events a
On Fri, 31 May 2013 15:37:07 -0700 Kevin Hilman wrote:
> Currently, the RTC IRQ is never wakeup-enabled so is not capable of
> bringing the system out of suspend.
>
> On OMAP platforms, we have gotten by without this because the TWL RTC
> is on an I2C-connected chip which is capable of waking up
On Tue, 20 Nov 2012 15:18:43 +0530
AnilKumar Ch wrote:
> From: Colin Foe-Parker
>
> Add system power off control to rtc driver which is the in-charge
> of controlling the BeagleBone system power. The power_off routine
> can be hooked up to "pm_power_off" system call.
>
> System power off seque
On Wed, 26 Sep 2012 13:44:03 -0700
Greg KH wrote:
> On Wed, Sep 26, 2012 at 01:34:50PM -0700, Andrew Morton wrote:
> > On Wed, 26 Sep 2012 13:24:00 -0700
> > Greg KH wrote:
> >
> > > On Mon, Sep 17, 2012 at 12:53:18PM +0530, AnilKumar Ch wrote:
> > > >
On Wed, 26 Sep 2012 13:24:00 -0700
Greg KH wrote:
> On Mon, Sep 17, 2012 at 12:53:18PM +0530, AnilKumar Ch wrote:
> > Adds device tree support to lis3lv02d_i2c driver. Along with this
> > DT init is moved from core driver to individual drivers, with the
> > current implementation some pdata is mi
On Mon, 17 Sep 2012 12:53:22 +0530
AnilKumar Ch wrote:
> Add lis331dlh device tree data to am335x-evm.dts. In AM335x EVM
> lis331dlh accelerometer is connected to I2C2 bus. So this patch
> change the status of I2C2 node to "okay" to use I2C2 bus. Also
> added all the required platform data to am3
On Fri, 14 Sep 2012 15:31:36 +
Arnd Bergmann wrote:
> On Friday 14 September 2012, AnilKumar Ch wrote:
> > Adds device tree support to lis3lv02d_i2c driver. Along with this
> > DT init is moved from core driver to individual drivers, with the
> > current implementation some pdata is missing i
On Fri, 14 Sep 2012 08:33:42 -0700
Steve Sakoman wrote:
> Tested-by: Steve Sakoman
Thanks.
Given the tested-by's that are rolling in, I will assume that people
are hitting this problem in 3.5 and perhaps earlier kernels, so I
scheduled the fix for 3.6, with a -stable backport.
I might have be
On Fri, 6 Jul 2012 09:33:54 -0700
Kevin Hilman wrote:
> Requesting a threaded interrupt without a primary handler and without
> IRQF_ONESHOT is dangerous, and after commit 1c6c6952 (genirq: Reject
> bogus threaded irq requests), these requests are rejected. This
> causes ->probe() to fail, and
On Mon, 21 May 2012 09:24:35 +0200
Corentin Chary wrote:
> In all these files, the .power field was never correctly initialized.
>
> ...
>
> --- a/drivers/gpu/drm/i915/intel_panel.c
> +++ b/drivers/gpu/drm/i915/intel_panel.c
> @@ -342,6 +342,7 @@ int intel_panel_setup_backlight(struct drm_device
On Fri, 30 Mar 2012 19:58:16 +0800
Bryan Wu wrote:
> Attempting to consolidate the ARM LED code, this removes the
> custom RealView LED trigger code to turn LEDs on and off in
> response to CPU activity and replace it with a standard trigger.
>
> (bryan...@canonical.com:
> It moves arch/arm/kern
On Wed, 28 Mar 2012 16:34:01 -0500
Nishanth Menon wrote:
> From: Konstantin Shlyakhovoy
>
> RTC stores time and date in several registers. Due to the fact that
> these registers can't be read instantaneously, there is a chance
> that reading from counting registers gives an error of one minute,
On Tue, 17 Jan 2012 07:32:47 +
"AnilKumar, Chimata" wrote:
> Hi All,
>
> Recalling the patch, provide the comments if there are any if not please
> include
> this patch to v3.3 kernel.
The patch is all mangled by someone's email client. Wordwrapping, mime
crap which my MUA can't decrypt,
On Sat, 12 Mar 2011 23:23:06 +0300
Vasiliy Kulikov wrote:
> > Vasiliy Kulikov (20):
> > mach-ux500: mbox-db5500: world-writable sysfs fifo file
> > leds: lp5521: world-writable sysfs engine* files
> > leds: lp5523: world-writable engine* sysfs files
> > misc: ep93xx_pwm: world-writable sysfs
On Tue, 1 Feb 2011 09:36:22 +0200 Ohad Ben-Cohen wrote:
> On Tue, Feb 1, 2011 at 8:38 AM, Andrew Morton
> wrote:
> >> I'll do a quick respin of the patches with that and the
> >> hwspinlock_internal.h comment above.
> >
> > OK..
> >
> >
On Tue, 1 Feb 2011 08:20:13 +0200 Ohad Ben-Cohen wrote:
> On Tue, Feb 1, 2011 at 1:38 AM, Andrew Morton
> wrote:
> > It's a little irritating having two hwspinlock.h's.
> > hwspinlock_internal.h wold be a conventional approach. _
On Mon, 31 Jan 2011 12:33:41 +0200
Ohad Ben-Cohen wrote:
> Add a platform-independent hwspinlock framework.
>
> Hardware spinlock devices are needed, e.g., in order to access data
> that is shared between remote processors, that otherwise have no
> alternative mechanism to accomplish synchroniza
On Thu, 6 Jan 2011 13:08:56 -0800
Randy Dunlap wrote:
> On Thu, 6 Jan 2011 13:04:40 -0800 Andrew Morton wrote:
>
> > On Thu, 9 Dec 2010 14:41:50 +0100
> > Janusz Krzysztofik wrote:
> >
> > > +static DEVICE_ATTR(invert, 0644, bl_trig_invert_show,
> > >
On Thu, 9 Dec 2010 14:41:50 +0100
Janusz Krzysztofik wrote:
> This patch extends the LED backlight tirgger driver with an option that
> allows
> for inverting the trigger output polarity.
>
> With the invertion option provided, I (ab)use the backlight trigger for
> driving a LED that indicate
On Tue, 4 Jan 2011 14:23:20 +0200
Ohad Ben-Cohen wrote:
> Hi Andrew,
>
> On Sat, Dec 18, 2010 at 2:53 AM, Tony Lindgren wrote:
> > * Ohad Ben-Cohen [101216 13:34]:
> >> Tony, Andrew, can you please have a look ?
> >>
> >> Any comment or suggestion is appreciated.
> >
> > Looks sane to me from
On Sun, 5 Dec 2010 12:06:03 +0200
Ohad Ben-Cohen wrote:
> Introduce BUG_ON_MAPPABLE_NULL in order to eliminate redundant BUG_ON
> code, checking for NULL addresses, on architectures where the zero
> address can never be mapped.
>
> Originally proposed by Russell King
>
> Signed-off-by: Ohad B
On Tue, 5 Oct 2010 17:29:56 +0530
Arun Murthy wrote:
> The existing pwm based led and backlight driver makes use of the
> pwm(include/linux/pwm.h). So all the board specific pwm drivers will
> be exposing the same set of function name as in include/linux/pwm.h.
> Consder a platform with multi Soc
On Sat, 21 Aug 2010 18:00:29 +0530
hvaib...@ti.com wrote:
> +static int s35390a_update_irq_enable(struct i2c_client *client,
> + unsigned enabled)
> +{
> + struct s35390a *s35390a = i2c_get_clientdata(client);
> + char buf[1];
> +
> + if (s35
On Thu, 17 Jun 2010 20:57:19 +0530 (IST)
"kishore kadiyala" wrote:
> Adding card detect callback function which gives the status of
> the card .For MMC1 Controller, Card detect interrupt source is
> twl6030 and card present/absent status is provided by MMCCTRL
> register of twl6030.
>
>
> ...
>
On Thu, 17 Jun 2010 20:56:58 +0530 (IST)
"kishore kadiyala" wrote:
> --- a/arch/arm/plat-omap/include/plat/mmc.h
> +++ b/arch/arm/plat-omap/include/plat/mmc.h
> @@ -43,6 +43,9 @@
>
> #define OMAP_MMC_MAX_SLOTS 2
>
> +#define NON_GPIO 0
> +#define GPIO 1
I'm count
On Thu, 17 Jun 2010 20:57:19 +0530 (IST)
"kishore kadiyala" wrote:
> Adding card detect callback function which gives the status of
> the card .For MMC1 Controller, Card detect interrupt source is
> twl6030 and card present/absent status is provided by MMCCTRL
> register of twl6030.
>
> Signed-o
On Wed, 2 Jun 2010 15:26:52 -0700
Cory Maccarrone wrote:
> On Wed, Jun 2, 2010 at 2:05 PM, Andrew Morton
> wrote:
> > On Sat, 29 May 2010 19:27:23 -0700
> > Cory Maccarrone wrote:
> >
> >> This change removes a BUG_ON for when interrupts are disabled
> >
On Sat, 29 May 2010 19:27:23 -0700
Cory Maccarrone wrote:
> This change removes a BUG_ON for when interrupts are disabled
> during an MMC request. During boot, interrupts can be disabled
> when a request is made, causing this bug to be triggered. In reality,
> there's no reason this should halt
On Tue, 01 Jun 2010 21:39:10 +0100
Jonathan Cameron wrote:
> >
> > It would be most useful if the changelog were to fully describe the
> > proposed kernel<->userspace interface. That's the most important part
> > of the driver, because it's the only part we can never change.
> >
> > There is a
On Tue, 1 Jun 2010 22:27:15 +0200
Daniel Mack wrote:
> On Tue, Jun 01, 2010 at 01:12:44PM -0700, Andrew Morton wrote:
> > On Mon, 24 May 2010 16:34:25 +0530 (IST)
> > "Hemanth V" wrote:
> >
> > > This patch adds support for ROHM BH1780GLI Ambient light
I re-added your reviewers to the cc...
On Mon, 24 May 2010 16:34:25 +0530 (IST)
"Hemanth V" wrote:
> This patch adds support for ROHM BH1780GLI Ambient light sensor.
>
> BH1780 supports I2C interface. Driver supports read/update of power state and
> read of lux value (through SYSFS). Writing v
On Thu, 20 May 2010 20:04:17 +0100
Alan Cox wrote:
>
> > > +EXPORT_SYMBOL_GPL(gpio_set_debounce);
> >
> > nitlet: I suspect this function is taking gpio_lock sooner than it
> > strictly needs to. Find-tuning that would decrease contention by an
> > insignificant amount ;)
>
> We need this for
On Mon, 17 May 2010 13:02:29 +0300
felipe.ba...@nokia.com wrote:
> From: Felipe Balbi
>
> Hi all,
>
> I'm resending this series since no-one has had any further
> comments for quite some time.
>
> Adding Andrew Morton to the loop also since David Brownell
&g
On Mon, 17 May 2010 13:02:30 +0300
felipe.ba...@nokia.com wrote:
> From: Felipe Balbi
>
> Few architectures, like OMAP, allow you to set
> a debouncing time for the gpio before generating
> the IRQ. Teach gpiolib about that.
>
> ...
>
> --- a/drivers/gpio/gpiolib.c
> +++ b/drivers/gpio/gpiolib.
On Thu, 13 May 2010 12:29:35 -0700
Tony Lindgren wrote:
> * Cory Maccarrone [100307 09:44]:
> > From: Marek Belisko
> >
> > The omap850 and omap730 use 16-bit registers instead of 32-bit, requiring
> > a modification of the register addresses in the mmc-omap driver. To resolve
> > this, a bit
On Tue, 11 May 2010 17:15:28 +0300
Eduardo Valentin wrote:
> Here is the version 5 of the change to export OMAP data to userspace
> (name, revision, id code, production id and die id).
>
> Basically, this version is still attempting to create a new file under /proc.
> It is the /proc/socinfo, wh
On Wed, 12 May 2010 10:50:45 +0300
Adrian Hunter wrote:
> >From ad2e1cd024ccf9144b6620cfe808893719db738f Mon Sep 17 00:00:00 2001
> From: Adrian Hunter
> Date: Wed, 14 Apr 2010 16:26:45 +0300
> Subject: [PATCH] omap_hsmmc: improve interrupt synchronisation
>
> The following changes were needed:
On Thu, 31 Dec 2009 22:15:08 +0100
Helge Deller wrote:
> On 12/30/2009 04:49 PM, James Bottomley wrote:
> > A better, and more comprehensive patch would be to try not to count the
> > empty text sections when we're building the notes section (and actually
> > anywhere else in the file). This pat
On Fri, 16 Oct 2009 17:25:04 +0100
Martin Michlmayr wrote:
> * Andrew Morton [2009-10-06 13:34]:
> > Rigor mortis is setting in on this one.
>
> > The patch seems correct to me.
>
> Can someone put this patch in now? The problem has also been reported
> on Marve
On Fri, 9 Oct 2009 23:42:27 +0200 (CEST)
Jiri Kosina wrote:
> On Fri, 9 Oct 2009, Greg KH wrote:
>
> > > >> There's a tree for trivial fixes:
> > > >> git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial
>
> Well, as this is quite a high-priority functional fix, I'd suggest using
> othe
On Fri, 9 Oct 2009 12:26:42 -0700
Greg KH wrote:
> > >
> > > What kind of issues? __Why would I be interested, where is the problem?
> >
> > The obvious-brain-dead-duh kind of issues, like this one.
> >
> > The problem is that OMAP devices (like beagleboard) are not booting
> > correctly right
On Wed, 30 Sep 2009 23:21:33 +0200
"Rafael J. Wysocki" wrote:
> On Wednesday 30 September 2009, Kevin Hilman wrote:
> > In the case where cpuidle_idle_call() returns before changing state
> > due to a need_resched(), it was returning with IRQs disabled.
> >
> > This patch ensures IRQs are (re)en
On Wed, 23 Sep 2009 10:04:09 +0300 Tomi Valkeinen
wrote:
> Hi,
>
> How can we proceed with the OMAP DSS2 merging? I can take the old omapfb
> patches you have to my tree, and give that tree to you as one set, or I
> can base the DSS2 on top of your tree. If that's ok, where can I find
> the pat
On Tue, 22 Sep 2009 15:29:48 +0300
Tomi Valkeinen wrote:
> Linus,
>
> Here's the new display subsystem and framebuffer driver for OMAP2/3.
>
> The driver has been reviewed on linux-omap and linux-fbdev-devel, and is in
> use, for example, on N900, Beagle Board and Overo boards. We have an ACK f
On Wed, 09 Sep 2009 15:00:03 +0300
Adrian Hunter wrote:
> >From baf6574a1b5e7c4fdc4a66d9e038efeee75ea1a0 Mon Sep 17 00:00:00 2001
> From: Adrian Hunter
> Date: Sun, 31 May 2009 19:27:36 +0300
> Subject: [PATCH] omap_hsmmc: ensure all clock enables and disables are paired
>
This patch hasn't be
On Wed, 2 Sep 2009 18:54:36 +0530 (IST)
"kishore kadiyala" wrote:
> This Patch adds basic support for all 5 MMC controllers on OMAP4.
>
> -Kishore
>
> Signed-off-by: Kishore Kadiyala
> ---
> This patch doesn't include mmc-regulator support
>
> arch/arm/mach-omap2/devices.c | 42
>
On Tue, 01 Sep 2009 10:10:19 +0300
Artem Bityutskiy wrote:
> Andrew,
>
> could you please help with merging this piece of (well written) code?
> Could you give your blessing to include it into linux-next now, and
> merge this during the next merge window?
I'll merge them (after I've looked thro
On Thu, 13 Aug 2009 10:27:15 -0500 "Madhusudhan" wrote:
> I am curious to know is this series lined up for upstream?
yup. http://userweb.kernel.org/~akpm/mmotm/ is the place to check for that.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to m
On Mon, 27 Jul 2009 14:02:47 +0300 Adrian Hunter
wrote:
> Matt Fleming wrote:
> > On Mon, Jul 27, 2009 at 10:15:11AM +0100, Matt Fleming wrote:
> >> On Mon, Jul 27, 2009 at 11:58:22AM +0300, Adrian Hunter wrote:
> >>> Yes much nicer. Will you add it to your patch?
> >> Sure, I'll reply with an
On Fri, 10 Jul 2009 15:43:09 +0300
Adrian Hunter wrote:
> >From 242fae6293adec671b14354f215217354f5076a0 Mon Sep 17 00:00:00 2001
> From: Adrian Hunter
> Date: Sat, 16 May 2009 10:32:34 +0300
> Subject: [PATCH] omap_hsmmc: prevent races with irq handler
>
> If an unexpected interrupt occurs whi
On Fri, 10 Jul 2009 15:42:27 +0300
Adrian Hunter wrote:
> +static int omap_mmc_regsleep_to_enabled(struct mmc_omap_host *host)
> +{
> + unsigned long timeout;
> +
> + dev_dbg(mmc_dev(host->mmc), "REGSLEEP -> ENABLED\n");
> +
> + clk_enable(host->fclk);
> + clk_enable(host->iclk);
On Wed, 11 Mar 2009 22:47:41 +0530
Trilok Soni wrote:
> Hi Felipe,
>
> On Fri, Dec 5, 2008 at 4:15 AM, Felipe Contreras
I bet he thought we'd forgotten.
> wrote:
> > From: Felipe Contreras
> >
> > The blank operation should receive FB_BLANK_POWERDOWN, not
> > VESA_POWERDOWN.
> >
>
> Thanks.
On Tue, 3 Feb 2009 15:05:58 +0100
Jean Pihet wrote:
> + while (OMAP_HSMMC_READ(host->base,
> + SYSCTL) & SRD)
> + ;
Is a __raw_readl() sufficient to prevent the cpu from burning up here,
or should we add cpu_relax()?
An infinite loop which assumes the hardwar
> On Tue, 14 Oct 2008 17:42:49 +0400 Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
> Hi.
>
> On Tue, Oct 14, 2008 at 05:50:02AM -0700, Andrew Morton ([EMAIL PROTECTED])
> wrote:
> > I think it's reasonable to permit the driver's operations to be interrupted
&g
> On Tue, 14 Oct 2008 14:21:50 +0530 "Madhusudhan Chikkature" <[EMAIL
> PROTECTED]> wrote:
>
> - Original Message -
> From: "Andrew Morton" <[EMAIL PROTECTED]>
> To: "Madhusudhan Chikkature" <[EMAIL PROTECTED]>
> On Mon, 13 Oct 2008 18:55:43 +0530 "Madhusudhan Chikkature" <[EMAIL
> PROTECTED]> wrote:
>
> - Original Message -
> From: "Andrew Morton" <[EMAIL PROTECTED]>
> To: "Gadiyar, Anand" <[EMAIL PROTECTED]>
> Cc: <
On Wed, 8 Oct 2008 12:46:25 +0530
"Gadiyar, Anand" <[EMAIL PROTECTED]> wrote:
> From: Madhusudhan Chikkature <[EMAIL PROTECTED]>
>
> The HDQ/1-Wire module of TI OMAP2430/3430 platforms implement the hardware
> protocol of the master functions of the Benchmark HDQ and the Dallas
> Semiconductor 1-
On Wed, 8 Oct 2008 12:53:57 +0530
"Gadiyar, Anand" <[EMAIL PROTECTED]> wrote:
> From: Madhusudhan Chikkature <[EMAIL PROTECTED]>
>
> Device registeration for the TI OMAP2430/3430 HDQ driver.
>
> Signed-off-by: Madhusudhan Chikkature <[EMAIL PROTECTED]>
> Acked-by: Felipe Balbi <[EMAIL PROTECTED]
On Wed, 8 Oct 2008 12:49:19 +0530
"Gadiyar, Anand" <[EMAIL PROTECTED]> wrote:
> From: Madhusudhan Chikkature <[EMAIL PROTECTED]>
>
> This patch provides the BQ27000 slave interface driver.
>
> ...
>
> --- /dev/null 1970-01-01 00:00:00.0 +
> +++ linux-2.6/drivers/w1/slaves/w1_bq27000.
69 matches
Mail list logo