On Wed, Nov 13, 2013 at 02:28:58PM +0530, Vinod Koul wrote:
On Tue, Nov 12, 2013 at 07:28:10PM +0900, Kukjin Kim wrote:
Vinod Koul wrote:
On Thu, Oct 31, 2013 at 10:48:09AM +0530, Sachin Kamat wrote:
Use the recently introduced DMA_COMPLETE instead of DMA_SUCCESS.
Without this
Hi Mark,
On Wed, Nov 27, 2013 at 8:35 PM, Mark Brown broo...@kernel.org wrote:
On Wed, Nov 27, 2013 at 06:08:47PM +0530, Padma Venkat wrote:
On Tue, Nov 26, 2013 at 5:50 PM, Mark Brown broo...@kernel.org wrote:
So this is 16 bit stereo or something, and did it work beforehand? Like
I say
This patch initializes the dma_data for the secondary dai.
Without this patch there is crash due to NULL pointer
dereference during boot time on systems where secondary dai
is initialized.
Below is the crash log:
[1.63] smdk-audio-wm8894 sound.7: wm8994-aif1 - 383.i2s mapping
ok
[
Arndale Octa board is based on Exynos5420 SoC. This patch
adds the basic support required for booting it through DT.
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
---
arch/arm/boot/dts/Makefile|1 +
arch/arm/boot/dts/exynos5420-arndale-octa.dts | 66
On 11/20/2013 08:54 AM, Tarek Dakhran wrote:
On 20.11.2013 03:23, Tomasz Figa wrote:
I've applied the patches on top of today's linux-next and tried to boot
my ODROID-XU using exynos5410-smdk5410.dts and exynos_defconfig, but all
I can get is an imprecise external abort, when the kernel tries
On Thu, Nov 28, 2013 at 03:32:12PM +0530, Padmavathi Venna wrote:
This is made based on Mark Brown for-next branch of sound.git
This patch is based on Mark Brown below patches for
generic dma engine support for samsung audio IPs.
ASoC: samsung: Use ASoC dmaengine code where possible
ASoC:
On Thu, Nov 28, 2013 at 03:29:31PM +0530, Padma Venkat wrote:
On Wed, Nov 27, 2013 at 8:35 PM, Mark Brown broo...@kernel.org wrote:
But if it's initialised at probe time then when is it getting
overwritten? This must be something triggered by DT which unfortunately
I can't test. It's a
On Wed, Oct 30, 2013 at 10:21:44AM +0530, Sachin Kamat wrote:
From: Andrew Bresticker abres...@chromium.org
When possible, avoid setting the manual update bit and starting/stopping
the PWM when adjusting the PWM as it causes noticable flickering when
setting the backlight brightness.
On Thursday 28 of November 2013 14:26:41 Thierry Reding wrote:
On Wed, Oct 30, 2013 at 10:21:44AM +0530, Sachin Kamat wrote:
From: Andrew Bresticker abres...@chromium.org
When possible, avoid setting the manual update bit and starting/stopping
the PWM when adjusting the PWM as it causes
I have development board whose SoC is exynos4412, I try to enable the
usb in it but I failed. I saw the document
Documentation/devicetree/bindings/usb/samsung-usbphy.txt, does it mean
that the usb driver is not done?
And about that document, in samsung datasheet(32.8.2), the address reg
Hi Sachin, Andrew,
On Wednesday 30 of October 2013 10:21:44 Sachin Kamat wrote:
From: Andrew Bresticker abres...@chromium.org
When possible, avoid setting the manual update bit and starting/stopping
the PWM when adjusting the PWM as it causes noticable flickering when
setting the backlight
On Wednesday, November 27, 2013 09:09:42 AM Viresh Kumar wrote:
This patch adds cpufreq callbacks to dpm_{suspend|resume}_noirq() for handling
suspend/resume of cpufreq governors.
There are multiple problems that are fixed by this patch:
- Nishanth Menon (TI) found an interesting problem on
On 28 November 2013 19:53, Rafael J. Wysocki r...@rjwysocki.net wrote:
I don't think that the Nishanth's issue is fixed by this particular version of
the patch, so I modified the changelog and removed a the comment above
cpufreq_suspend()
No, it does fix his issue as we are just stopping the
Hi Randy,
On Thursday 28 of November 2013 22:00:41 randy wrote:
I have development board whose SoC is exynos4412, I try to enable the
usb in it but I failed. I saw the document
Documentation/devicetree/bindings/usb/samsung-usbphy.txt, does it mean
that the usb driver is not done?
And about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Tomasz Figa
于 2013年11月28日 22:37, Tomasz Figa 写道:
Hi Randy,
On Thursday 28 of November 2013 22:00:41 randy wrote:
I have development board whose SoC is exynos4412, I try to enable
the usb in it but I failed. I saw the document
On Thursday, November 28, 2013 07:49:29 PM Viresh Kumar wrote:
On 28 November 2013 19:53, Rafael J. Wysocki r...@rjwysocki.net wrote:
I don't think that the Nishanth's issue is fixed by this particular version
of
the patch, so I modified the changelog and removed a the comment above
On Wed, Nov 27, 2013 at 11:25 PM, Vinod Koul vinod.k...@intel.com wrote:
On Wed, Nov 13, 2013 at 02:28:58PM +0530, Vinod Koul wrote:
On Tue, Nov 12, 2013 at 07:28:10PM +0900, Kukjin Kim wrote:
Vinod Koul wrote:
On Thu, Oct 31, 2013 at 10:48:09AM +0530, Sachin Kamat wrote:
Use the
On 29 November 2013 01:59, Rafael J. Wysocki r...@rjwysocki.net wrote:
So I'm reading this as the version of the patch in bleeding-edge is OK.
I hope that really is the case. :-)
Yeah, that's correct.
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of
On Thu, Nov 28, 2013 at 02:33:22PM -0800, Dan Williams wrote:
On Wed, Nov 27, 2013 at 11:25 PM, Vinod Koul vinod.k...@intel.com wrote:
On Wed, Nov 13, 2013 at 02:28:58PM +0530, Vinod Koul wrote:
On Tue, Nov 12, 2013 at 07:28:10PM +0900, Kukjin Kim wrote:
Vinod Koul wrote:
On Thu,
Hi Sachin,
Use common clock framework (CCF) APIs to set the clock rates
instead of direct register manipulation. This now updates the
sysfs entry (cpuinfo_cur_freq) correctly which did not reflect
the correct value until now. While at it clean up the PLL s-div
parameter setting as it is
20 matches
Mail list logo
