On 07/02/2014 07:33 AM, Laura Abbott wrote:
Currently, early_init_dt_scan validates the header, sets the
boot params, and scans for chosen/memory all in one function.
Split this up into two separate functions (validation/setting
boot params in one, scanning in another) to allow for
additional
Hi Marek,
On 07/01/2014 06:08 PM, Marek Szyprowski wrote:
Hello,
On 2014-07-01 10:52, Tobias Jakobi wrote:
Hello Marek,
I think you had a similar patch in the tizen tree, but according to
Tomasz Figa, it was considered a hack. I don't quite see how this is
different.
Also, if I have been
Kukjin,
Your commit 0aeaa68cf509 (ASoC: samsung: no more support for S5P6440
and S5P6450 SoCs) landed in next-20140702. It removed references to
MACH_SMDK6440 and MACH_SMDK6450 from sound/soc/samsung/.
It seems to have missed one reference to MACH_SMDK6450 in
sound/soc/samsung/Kconfig
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
---
drivers/phy/phy-samsung-usb2.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/phy/phy-samsung-usb2.c b/drivers/phy/phy-samsung-usb2.c
index 8a8c6bc..1e69a32 100644
--- a/drivers/phy/phy-samsung-usb2.c
+++
Hello,
On 2014-07-01 19:54, Tobias Jakobi wrote:
Marek Szyprowski wrote:
On 2014-07-01 10:52, Tobias Jakobi wrote:
I think you had a similar patch in the tizen tree, but according to
Tomasz Figa, it was considered a hack. I don't quite see how this is
different.
Also, if I have been
Kukjin,
Your commit 52ad6582ceb2 (ARM: S5PC100: no more support S5PC100 SoC
landed in next-20140702. It removed the Kconfig symbol MACH_SMDKC100
(and a lot of other stuff).
Is the trivial patch to also remove the last two references to
MACH_SMDKC100 from sound/soc/samsung/Kconfig/ queued
Hi,
On Wednesday 02 July 2014 01:18 PM, Sjoerd Simons wrote:
Please add a commit log here describing what your patch does and why you need
it.
Cheers
Kishon
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
---
drivers/phy/phy-samsung-usb2.c | 1 +
1 file changed, 1 insertion(+)
ARCH_EXYNOS doesn't select NEED_MACH_MEMORY_H, so asm/memory.h doesn't
include mach/memory.h and so this file is not used and can go away.
Signed-off-by: Uwe Kleine-König u.kleine-koe...@pengutronix.de
---
Cc: Kukjin Kim kgene@samsung.com
Cc: linux-samsung-soc@vger.kernel.org
---
Hello Mike,
On 07/01/2014 07:26 PM, Mike Turquette wrote:
Quoting Yadwinder Singh Brar (2014-06-29 21:01:36)
Hi Javier,
On Thu, Jun 26, 2014 at 11:45 PM, Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
Maxim Integrated Power Management ICs are very similar with
regard to
Hello Mike,
On 07/01/2014 07:29 PM, Mike Turquette wrote:
Quoting Javier Martinez Canillas (2014-06-26 11:15:36)
Like most clock drivers, the Maxim 77686 PMIC clock binding
follows the convention that the #clock-cells property is
used to specify the number of cells in a clock provider.
But
On śro, 2014-07-02 at 12:13 +0200, Javier Martinez Canillas wrote:
Hello Mike,
On 07/01/2014 07:26 PM, Mike Turquette wrote:
Quoting Yadwinder Singh Brar (2014-06-29 21:01:36)
Hi Javier,
On Thu, Jun 26, 2014 at 11:45 PM, Javier Martinez Canillas
javier.marti...@collabora.co.uk
Hi All,
While testing linux-next (next-20140625) on Exynos4412-based TRATS2
board, from time to time I hit a deadlock between clk_disable_unused()
of Common Clock Framework and parallel clk_prepare() from s3c24xx-i2c
driver.
I believe the following is happening (in processes 1 and 2):
1:
On Wed, Jul 02, 2014 at 12:59:04PM +0200, Tomasz Figa wrote:
Hi All,
While testing linux-next (next-20140625) on Exynos4412-based TRATS2
board, from time to time I hit a deadlock between clk_disable_unused()
of Common Clock Framework and parallel clk_prepare() from s3c24xx-i2c
driver.
This
On Wed, Jul 02, 2014 at 12:59:04PM +0200, Tomasz Figa wrote:
Hi All,
While testing linux-next (next-20140625) on Exynos4412-based TRATS2
board, from time to time I hit a deadlock between clk_disable_unused()
of Common Clock Framework and parallel clk_prepare() from s3c24xx-i2c
driver.
I
On 02/07/14 13:49, Peter De Schrijver wrote:
Or if you use notifiers which use i2c... See also
http://comments.gmane.org/gmane.linux.kernel/1553699. One workaround is to
always leave the clock of the i2c controller in a prepared state.
Keeping the clock always prepared might not be that bad,
On Tue, Jul 1, 2014 at 9:18 PM, Andreas Färber afaer...@suse.de wrote:
Am 23.06.2014 23:24, schrieb Andreas Färber:
Am 23.06.2014 22:11, schrieb Benson Leung:
On Mon, Jun 23, 2014 at 12:57 PM, Doug Anderson diand...@chromium.org
wrote:
Also when the screen stayed on, the embedded
Use the MCPM layer to handle core suspend/resume on Exynos5420.
Also, restore the entry address setup code post-resume.
Signed-off-by: Abhilash Kesavan a.kesa...@samsung.com
---
Hi Lorenzo and Nicolas,
I have re-worked the patch to use the residency value as an indicator of the
current state.
Quoting Javier Martinez Canillas (2014-07-02 03:17:54)
Hello Mike,
On 07/01/2014 07:29 PM, Mike Turquette wrote:
Quoting Javier Martinez Canillas (2014-06-26 11:15:36)
Like most clock drivers, the Maxim 77686 PMIC clock binding
follows the convention that the #clock-cells property is
This series fixes various shortcommings of the Samsung pin control driver
that have been spotted while using it on various platforms with multiple
use cases and requirements.
Most of the patches are independent of each other, with the exception of
patch 4/6 which depends on patch 3/6, due to
This patch makes the pinctrl-samsung driver configure GPIO direction on
its own, without using the pinctrl_gpio_direction_*() helpers. The
rationale behind this change is as follows:
- pinctrl-samsung does not need translation from GPIO namespace to
pinctrl namespace to handle GPIO operations
Handling of irq_chip operations for GPIO and WKUP external interrupts
is mostly the same, with the difference being offset of registers.
However currently the driver has all the code duplicated for both EINT
types, which is undesirable, because changes in irq_chip operations have
to be done to
One of remaining limitations of current pinctrl-samsung driver was
the inability to parse multiple pinmux/pinconf group nodes grouped
inside a single device tree node. It made defining groups of pins for
single purpose, but with different parameters very inconvenient.
This patch implements
Currently after configuring a GPIO pin as an interrupt related pinmux
registers are changed, but there is no protection from calling
gpio_direction_*() in a badly written driver, which would cause the same
pinmux register to be reconfigured for regular input/output and this
disabling interrupt
This patch adds .request() and .free() operations to gpio_chip of
pinctrl-samsung driver, which call pinctrl request and free helpers to
request and free pinctrl pin along with GPIO pin.
Signed-off-by: Tomasz Figa t.f...@samsung.com
---
drivers/pinctrl/pinctrl-samsung.c | 15 ++-
1
On Fri, Jun 13, 2014 at 09:29:50AM +0530, Naveen Krishna Chatradhi wrote:
Hence, spi-s3c64xx.c is broken since Jun 21 11:26:12 2013 and
considering the time with no compliants about the breakage.
I'm not clear what the breakage is? Some boards are broken but what's
the driver issue?
The following changes since commit b640a6037c9ecd1f0ad23a8e9b4ca5f5b4112508:
Merge tag 'sunxi-clk-for-3.16-2' of https://github.com/mripard/linux into
clk-next (2014-06-11 07:11:59 -0700)
are available in the git repository at:
Quoting Karol Wrona (2014-07-01 10:13:59)
s2mps11 clocks had registered callbacks for prepare ,unprepare and is_enabled.
During disabling unused clocks the lack of is_prepared caused that unused
s2mps11 clocks were not unprepared and stayed active.
Regmap_read is cached so it can be called
Quoting Tomasz Figa (2014-07-02 09:52:06)
The following changes since commit b640a6037c9ecd1f0ad23a8e9b4ca5f5b4112508:
Merge tag 'sunxi-clk-for-3.16-2' of https://github.com/mripard/linux into
clk-next (2014-06-11 07:11:59 -0700)
are available in the git repository at:
Hi Kukjin,
On 30.06.2014 23:32, Kukjin Kim wrote:
This series removes S5P64X0 and S5PC100 related codes in mainline,
because no more user now. And if its supporting is required later,
it will be done with using device tree.
[PATCH 01/17] ARM: S5P64X0: no more support S5P6440 and S5P6450
On 02.07.2014 19:13, Mike Turquette wrote:
Quoting Tomasz Figa (2014-07-02 09:52:06)
The following changes since commit b640a6037c9ecd1f0ad23a8e9b4ca5f5b4112508:
Merge tag 'sunxi-clk-for-3.16-2' of https://github.com/mripard/linux into
clk-next (2014-06-11 07:11:59 -0700)
are available
On 07/02/14 18:23, Mark Brown wrote:
On Wed, Jul 02, 2014 at 09:47:18AM +0200, Paul Bolle wrote:
Your commit 0aeaa68cf509 (ASoC: samsung: no more support for S5P6440
and S5P6450 SoCs) landed in next-20140702. It removed references to
MACH_SMDK6440 and MACH_SMDK6450 from sound/soc/samsung
On 07/03/14 03:02, Tomasz Figa wrote:
Hi Kukjin,
Hi,
On 30.06.2014 23:32, Kukjin Kim wrote:
This series removes S5P64X0 and S5PC100 related codes in mainline,
because no more user now. And if its supporting is required later,
it will be done with using device tree.
[PATCH 01/17] ARM:
Quoting Kukjin Kim (2014-06-25 03:36:51)
Tomasz Figa wrote:
Hi Tomasz,
On all Exynos SoCs there is a dedicated CLKOUT pin that allows many of
internal SoC clocks to be output from the SoC. The hardware structure
Yeah, because the CLKOUT pin is used for measure of the clock for debug
On Mon, Jun 30, 2014 at 10:12:16PM +0300, Vasily Khoruzhick wrote:
Use clk_prepare_enable/clk_disable_unprepare to make the driver
work properly with common clock framework.
Signed-off-by: Vasily Khoruzhick anars...@gmail.com
Pushed to l2-mtd.git. Thanks!
Brian
--
To unsubscribe from this
Hi Ajay,
Thanks a lot for your work on this.
Am 11.06.2014 20:26, schrieb Ajay Kumar:
This series is based on exynos-drm-next branch of Inki Dae's tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git
I have tested this after adding few DT changes for
35 matches
Mail list logo
