Hi Kishon,
On Wed, Oct 16, 2013 at 9:28 AM, Kishon Vijay Abraham I kis...@ti.com wrote:
diff --git a/drivers/video/exynos/exynos_mipi_dsi.c
b/drivers/video/exynos/exynos_mipi_dsi.c
index 32e5406..00b3a52 100644
--- a/drivers/video/exynos/exynos_mipi_dsi.c
+++
Hi Kishon,
Recently, I posted 'simple-phy' driver.
It is a part of patchset for HDMI enabling on Exynos4 using Device Tree.
http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg23655.html
The simple-phy was dedicated for single register PHYs like HDMI or DP.
Using such a generic phy
Fixed the following compilation warning:
../../drivers/video/exynos/exynos_mipi_dsi.c: In function
'exynos_mipi_dsi_blank_mode':
../../drivers/video/exynos/exynos_mipi_dsi.c:144:26: warning: unused
variable 'pdev' [-Wunused-variable]
struct platform_device *pdev = to_platform_device(dsim-dev);
On Thu, Oct 24, 2013 at 08:57:34PM +0530, Kishon Vijay Abraham I wrote:
Fixed the following compilation warning:
../../drivers/video/exynos/exynos_mipi_dsi.c: In function
'exynos_mipi_dsi_blank_mode':
../../drivers/video/exynos/exynos_mipi_dsi.c:144:26: warning: unused
variable 'pdev'
Hi,
On Monday 21 October 2013 07:48 PM, Tomasz Stanislawski wrote:
Use default handler of_phy_simple_xlate() when NULL is passed as argument to
of_phy_provider_register().
Signed-off-by: Tomasz Stanislawski t.stanisl...@samsung.com
---
drivers/phy/phy-core.c |2 +-
1 file changed, 1
Hi Olof,
On 24 October 2013 20:00, Olof Johansson o...@lixom.net wrote:
Hi Kishon,
On Wed, Oct 16, 2013 at 9:28 AM, Kishon Vijay Abraham I kis...@ti.com wrote:
diff --git a/drivers/video/exynos/exynos_mipi_dsi.c
b/drivers/video/exynos/exynos_mipi_dsi.c
index 32e5406..00b3a52 100644
---
Hi,
On Monday 21 October 2013 07:48 PM, Tomasz Stanislawski wrote:
Add simple-phy driver to support a single register
PHY interfaces present on Exynos4 SoC.
How are these PHY interfaces modelled in the SoC? Where does the register
actually reside?
Signed-off-by: Tomasz Stanislawski
Hi,
On Thursday 24 October 2013 09:12 PM, Sachin Kamat wrote:
Hi Olof,
On 24 October 2013 20:00, Olof Johansson o...@lixom.net wrote:
Hi Kishon,
On Wed, Oct 16, 2013 at 9:28 AM, Kishon Vijay Abraham I kis...@ti.com
wrote:
diff --git a/drivers/video/exynos/exynos_mipi_dsi.c
On Thu, Oct 24, 2013 at 8:42 AM, Sachin Kamat sachin.ka...@linaro.org wrote:
Hi Olof,
On 24 October 2013 20:00, Olof Johansson o...@lixom.net wrote:
Hi Kishon,
On Wed, Oct 16, 2013 at 9:28 AM, Kishon Vijay Abraham I kis...@ti.com
wrote:
diff --git a/drivers/video/exynos/exynos_mipi_dsi.c
Hello Joe,
On Wed, Oct 23, 2013 at 12:14:50PM -0700, Joe Perches wrote:
Emitting an OOM message isn't necessary after input_allocate_device
as there's a generic OOM and a dump_stack already done.
[...]
Signed-off-by: Joe Perches j...@perches.com
diff --git a/drivers/input/joystick/as5011.c
Hi Joe,
On Wed, Oct 23, 2013 at 12:14:50PM -0700, Joe Perches wrote:
Emitting an OOM message isn't necessary after input_allocate_device
as there's a generic OOM and a dump_stack already done.
No, please don't. The kzalloc may get changed in the future to not dump
stack (that was added
On Thu, 2013-10-24 at 20:26 +0200, Uwe Kleine-König wrote:
Hello Joe,
On Wed, Oct 23, 2013 at 12:14:50PM -0700, Joe Perches wrote:
Emitting an OOM message isn't necessary after input_allocate_device
as there's a generic OOM and a dump_stack already done.
[...]
Signed-off-by: Joe
On Thu, 2013-10-24 at 11:37 -0700, Dmitry Torokhov wrote:
Hi Joe,
On Wed, Oct 23, 2013 at 12:14:50PM -0700, Joe Perches wrote:
Emitting an OOM message isn't necessary after input_allocate_device
as there's a generic OOM and a dump_stack already done.
No, please don't. The kzalloc may
On Thu, Oct 24, 2013 at 11:43:38AM -0700, Joe Perches wrote:
On Thu, 2013-10-24 at 20:26 +0200, Uwe Kleine-König wrote:
Hello Joe,
On Wed, Oct 23, 2013 at 12:14:50PM -0700, Joe Perches wrote:
Emitting an OOM message isn't necessary after input_allocate_device
as there's a generic OOM
On Thu, 2013-10-24 at 20:46 +0200, Uwe Kleine-König wrote:
On Thu, Oct 24, 2013 at 11:43:38AM -0700, Joe Perches wrote:
[]
Any k.alloc without __GFP_NOWARN does a generic OOM message
and a dump_stack() so there could already be 2 messages anyway.
Then mention that in the commit log if you
On Thu, Oct 24, 2013 at 11:45:39AM -0700, Joe Perches wrote:
On Thu, 2013-10-24 at 11:37 -0700, Dmitry Torokhov wrote:
Hi Joe,
On Wed, Oct 23, 2013 at 12:14:50PM -0700, Joe Perches wrote:
Emitting an OOM message isn't necessary after input_allocate_device
as there's a generic OOM and
On Thu, Oct 24, 2013 at 11:48:48AM -0700, Joe Perches wrote:
On Thu, 2013-10-24 at 20:46 +0200, Uwe Kleine-König wrote:
On Thu, Oct 24, 2013 at 11:43:38AM -0700, Joe Perches wrote:
[]
Any k.alloc without __GFP_NOWARN does a generic OOM message
and a dump_stack() so there could already be
On Thu, 2013-10-24 at 12:10 -0700, Dmitry Torokhov wrote:
On Thu, Oct 24, 2013 at 11:45:39AM -0700, Joe Perches wrote:
On Thu, 2013-10-24 at 11:37 -0700, Dmitry Torokhov wrote:
Hi Joe,
On Wed, Oct 23, 2013 at 12:14:50PM -0700, Joe Perches wrote:
Emitting an OOM message isn't
On 10/24/2013 05:57 PM, Kishon Vijay Abraham I wrote:
On Thursday 24 October 2013 09:12 PM, Sachin Kamat wrote:
On 24 October 2013 20:00, Olof Johanssono...@lixom.net wrote:
On Wed, Oct 16, 2013 at 9:28 AM, Kishon Vijay Abraham Ikis...@ti.com wrote:
diff --git
19 matches
Mail list logo