Hi,
On Wed, Jun 4, 2014 at 12:41 AM, Paul Zimmerman
wrote:
>> From: linux-usb-ow...@vger.kernel.org
>> [mailto:linux-usb-ow...@vger.kernel.org] On Behalf Of Vivek Gautam
>> Sent: Tuesday, June 03, 2014 3:40 AM
>>
>> Putting together the code related to getting the 'IORESOURCE_MEM'
>> and assign
Hi Ben,
On Wed, Jun 4, 2014 at 4:56 AM, Ben Hutchings wrote:
> On Tue, 2014-06-03 at 20:34 +0100, Ben Hutchings wrote:
>> On Wed, 2014-05-21 at 18:11 +0530, Arun Kumar K wrote:
>> > Adding the following firmware files for MFC
>> > s5p-mfc-v7.fw: Used in exynos 5420
>> > s5p-mfc-v8.fw: Used in exy
Doug Anderson wrote:
>
> Chirantan,
>
> On Tue, Jun 3, 2014 at 11:48 AM, Chirantan Ekbote
> wrote:
> > Unfortunately on some exynos systems, resetting the mct counter also
> > resets the architected timer counter. This can cause problems if the
> > architected timer driver has already been init
Chirantan Ekbote wrote:
>
> Hi Kukjin,
>
Hi,
> On Wed, May 21, 2014 at 5:47 AM, Kukjin Kim wrote:
> > Yeah, actually we don't need to reset the count value after suspend/resume.
> > So, how about following? I think, it should be fine to you.
> >
> > diff --git a/drivers/clocksource/exynos_mct.c
Chirantan,
On Tue, Jun 3, 2014 at 11:48 AM, Chirantan Ekbote
wrote:
> Unfortunately on some exynos systems, resetting the mct counter also
> resets the architected timer counter. This can cause problems if the
> architected timer driver has already been initialized because the kernel
> will thin
On Tue, 2014-06-03 at 20:34 +0100, Ben Hutchings wrote:
> On Wed, 2014-05-21 at 18:11 +0530, Arun Kumar K wrote:
> > Adding the following firmware files for MFC
> > s5p-mfc-v7.fw: Used in exynos 5420
> > s5p-mfc-v8.fw: Used in exynos 5800
> >
> > Signed-off-by: Arun Kumar K
> > ---
> > Changes fr
On Wed, 2014-05-21 at 18:11 +0530, Arun Kumar K wrote:
> Adding the following firmware files for MFC
> s5p-mfc-v7.fw: Used in exynos 5420
> s5p-mfc-v8.fw: Used in exynos 5800
>
> Signed-off-by: Arun Kumar K
> ---
> Changes from v1
> - None
> ---
> WHENCE|2 ++
> s5p-mfc/s5p-m
On Wed, 2014-05-21 at 18:11 +0530, Arun Kumar K wrote:
> This is the newer version of mfc-v6 firmware which can
> be used in exynos5250 based boards. This has many bug fixes
> and enhancements. To maintain backward compatibility, the older
> firmware file is still retained and the new file is added
> From: linux-usb-ow...@vger.kernel.org
> [mailto:linux-usb-ow...@vger.kernel.org] On Behalf Of Vivek Gautam
> Sent: Tuesday, June 03, 2014 3:40 AM
>
> Putting together the code related to getting the 'IORESOURCE_MEM'
> and assigning the same to dwc->xhci_resources, for increasing
> the readabili
Unfortunately on some exynos systems, resetting the mct counter also
resets the architected timer counter. This can cause problems if the
architected timer driver has already been initialized because the kernel
will think that the counter has wrapped around, causing a big jump in
printk timestamps
Hi Kukjin,
On Wed, May 21, 2014 at 5:47 AM, Kukjin Kim wrote:
> Yeah, actually we don't need to reset the count value after suspend/resume.
> So, how about following? I think, it should be fine to you.
>
> diff --git a/drivers/clocksource/exynos_mct.c
> b/drivers/clocksource/exynos_mct.c
> index
On Tue, Jun 3, 2014 at 7:22 AM, Lucas Stach wrote:
> Hello Bjorn,
>
> Am Freitag, den 30.05.2014, 11:30 -0600 schrieb Bjorn Helgaas:
>> On Mon, May 12, 2014 at 10:59:43AM +0200, Lucas Stach wrote:
>> > Hi Bjorn,
>> >
>> > just a friendly reminder. It would be nice if you could pull those in.
>> >
On Fri, May 30, 2014 at 09:01:16AM +0100, Ulf Hansson wrote:
> On 28 May 2014 07:35, Jaehoon Chung wrote:
> > Removed the parser for "supports-highspeed".
> > It can be parsed with "cap-mmc-highsped" or "cap-sd-highspeed" at
> > mmc_of_parse().
> >
> > Signed-off-by: Jaehoon Chung
> > ---
> > dr
Hello Bjorn,
Am Freitag, den 30.05.2014, 11:30 -0600 schrieb Bjorn Helgaas:
> On Mon, May 12, 2014 at 10:59:43AM +0200, Lucas Stach wrote:
> > Hi Bjorn,
> >
> > just a friendly reminder. It would be nice if you could pull those in.
> >
> > Shawn already pulled the DT change and as it is a bindin
On 06/03/2014 11:58 AM, Ajay kumar wrote:
> On Tue, May 20, 2014 at 1:40 AM, Thierry Reding
> wrote:
>> On Tue, May 20, 2014 at 12:37:38AM +0530, Ajay kumar wrote:
>>> On 5/19/14, Thierry Reding wrote:
On Sun, May 18, 2014 at 01:50:36PM +0530, Ajay kumar wrote:
> On Sun, May 18, 2014 at
On 03.06.2014 14:17, Wolfram Sang wrote:
>
>> Couldn't it be made configurable with a Kconfig entry? E.g. "Enable
>> deprecated class-based instantiation" under Drivers / I2C? Turning it
>> off could make the code ignore the class field completely.
>
> Technically, yes. But we could also wait ano
> Couldn't it be made configurable with a Kconfig entry? E.g. "Enable
> deprecated class-based instantiation" under Drivers / I2C? Turning it
> off could make the code ignore the class field completely.
Technically, yes. But we could also wait another cycle and just be done
with it :)
signatur
Hi Wolfram, Sachin,
On 03.06.2014 13:21, Sachin Kamat wrote:
> Hi Wolfram,
>
> On Tue, Jun 3, 2014 at 3:35 PM, Wolfram Sang wrote:
>> On Tue, Jun 03, 2014 at 02:30:22PM +0530, Sachin Kamat wrote:
>>> With multiplatform support enabled for Exynos, class based
>>> instantiation causes a boot time
> The reason for the removal is the boot delay it is causing on Exynos 5250
> based boards by throwing the following errors continuously.
>
> [ 55.005300] s3c-i2c 12ce.i2c: cannot get bus (error -110)
> [ 59.005300] s3c-i2c 12ce.i2c: cannot get bus (error -110)
> [ 63.005300] s3c-i2c
Hi Arnd,
On Tue, Jun 3, 2014 at 3:23 PM, Arnd Bergmann wrote:
> commit e4ac92df2791 ("serial: samsung: Neaten dbg uses") introduced
> a regression in the conversion from vsprintf to vsnprintf.
>
> This fixes the build error by passing the correct variable name.
I submitted a similar patch someti
Hi Wolfram,
On Tue, Jun 3, 2014 at 3:35 PM, Wolfram Sang wrote:
> On Tue, Jun 03, 2014 at 02:30:22PM +0530, Sachin Kamat wrote:
>> With multiplatform support enabled for Exynos, class based
>> instantiation causes a boot time delay due to I2C_CLASS_HWMON
>> triggered probe. Since class based inst
Putting together the code related to getting the 'IORESOURCE_MEM'
and assigning the same to dwc->xhci_resources, for increasing
the readability.
Signed-off-by: Vivek Gautam
---
Based on 'next' branch of Felipe's usb tree.
Also cleanly applies to 'usb-next' branch of Greg's usb tree.
drivers/us
On Tue, Jun 03, 2014 at 02:30:22PM +0530, Sachin Kamat wrote:
> With multiplatform support enabled for Exynos, class based
> instantiation causes a boot time delay due to I2C_CLASS_HWMON
> triggered probe. Since class based instantiation has been
> deprecated since some time now, remove it for Sams
commit e4ac92df2791 ("serial: samsung: Neaten dbg uses") introduced
a regression in the conversion from vsprintf to vsnprintf.
This fixes the build error by passing the correct variable name.
Signed-off-by: Arnd Bergmann
Cc: Joe Perches
Cc: Greg Kroah-Hartman
Cc: Doug Anderson
Cc: Kukjin Kim
On Fri, May 30, 2014 at 12:42:57PM -0600, Stephen Warren wrote:
> From: Stephen Warren
>
> This is the same change as commit fb6b8e71448a "ASoC: tegra: free jack
> GPIOs before the sound card is freed", but applied to all other ASoC
> machine drivers where code inspection indicates the same probl
With multiplatform support enabled for Exynos, class based
instantiation causes a boot time delay due to I2C_CLASS_HWMON
triggered probe. Since class based instantiation has been
deprecated since some time now, remove it for Samsung I2C driver.
Signed-off-by: Sachin Kamat
Cc: Olof Johansson
---
26 matches
Mail list logo
