Hello Lee,
On 01/20/2015 05:34 PM, Lee Jones wrote:
So, the Embedded Controller driver (drivers/mfd/cros_ec.c) falls into that
category and in fact has been in the mfd driver for a long time. Now, if
an mfd device support different type of buses (e.g: i2c, spi, etc) I see
that both the core
Hello Lee,
Thanks a lot for your feedback.
On 01/20/2015 08:50 AM, Lee Jones wrote:
@@ -59,9 +60,17 @@ struct cros_ec_command {
*
* @ec_name: name of EC device (e.g. 'chromeos-ec')
* @phys_name: name of physical comms layer (e.g. 'i2c-4')
- * @dev: Device pointer
+ * @dev: Device
Hello Lee,
On 01/20/2015 08:48 AM, Lee Jones wrote:
Looks okay to me, but I'd be happy with some more reviews from the
Chrome guys. I would especially like some knowledgeable type to
answer your EC_PROTO2_MAX_PARAM_SIZE question. If no one does, I
guess it can always be changed later.
Hello Lee,
Thanks a lot for your feedback.
On 01/20/2015 09:20 AM, Lee Jones wrote:
On Fri, 02 Jan 2015, Javier Martinez Canillas wrote:
The ChromeOS EC character device is an user-space interface to
allow applications to access the Embedded Controller.
Add a cell for this device so it's
Hello Lee,
On 01/20/2015 05:29 PM, Lee Jones wrote:
It's not a blocker, but it is a ridiculous name to use inside the
driver/ directory 'cos almost everything is a dev(ice) here.
Right, do you think that cros-ec-chardev will be a more suitable
name? Sorry, I'm really bad at naming
Hello Marek,
I wanted to test your IOMMU series on an Exynos5420 Peach Pit but the
kernel hangs with your series + dependencies on top of 3.19-rc5.
Bisecting I found that $subject is the offending commit. I've pushed
my test branch [0] in case I missed something.
On Fri, Jan 16, 2015 at 10:13
Hello Thierry,
On 01/05/2015 02:50 PM, Thierry Reding wrote:
On Fri, Jan 02, 2015 at 01:10:14PM +, Daniel Stone wrote:
Ajay's series don't apply cleanly anymore because it has been a while since
he posted it but he can rebase on top of 3.19-rc1 once it is released and
re-resend.
: rebased onto generic power domains dt bindings]
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
---
arch/arm/boot/dts/exynos5250.dtsi | 10 ++
1 file changed, 10 insertions(+)
This patch makes HDMI to work on my Exynos5250 Snow Chromebook:
Tested-by: Javier Martinez Canillas
dropped so here goes again:
For the whole series on an Exynos5420 Peach Pit and an Exynos5250 Snow
Chromebooks:
Tested-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Also I think the last update was that Ajay was going to resend this
based on v3.19-rc1 or something. Is that still
Hello Kukjin,
On 01/14/2015 04:17 PM, Kukjin Kim wrote:
pinctrl_0 {
+power_key_irq: power-key-irq {
+samsung,pins = gpx1-3;
+samsung,pin-function = 0xf;
I think, this setting should be same with exynos5250-spring but different.
from:
Hello Kukjin,
On 01/14/2015 04:28 PM, Kukjin Kim wrote:
I saw that you collected some DTS patches for 3.20 but these are not
included. Any comments about this series?
Yeah, but I don't think I checked all of submitted patches including
this at that time and I'll have a look at this series
On 01/14/2015 01:19 AM, Javier Martinez Canillas wrote:
I dug further on this issue and found that the cause is that the exynos_mixer
driver needs some clocks (CLK_HDMI and CLK_SCLK_HDMI) grabbed by exynos_hdmi
to be kept enabled after hdmi_poweroff (drivers/gpu/drm/exynos/exynos_hdmi.c
Hello Joonyoung,
On 01/13/2015 09:40 AM, Joonyoung Shim wrote:
These are the changes I have now [0]. Please let me know what you think.
Good, it's working with your patch without u-boot changes and reverting
of commit 2ed127697eb.
But i also get stripe hdmi output if hdmi/mixer
Hello Joonyoung,
On 01/13/2015 06:24 AM, Joonyoung Shim wrote:
Also, the SW_ACLK_300_DISP1 and USER_ACLK_300_DISP1 are needed for the FIMD
parent and input clock respectively. Adding those to the clocks list of the
DISP1 power domain gives me working display + HDMI on my Exynos5800 Peach Pi.
Hello Joonyoung,
On 01/13/2015 06:24 AM, Joonyoung Shim wrote:
Yes, I was not able to trigger that by running modetest but by turning off
my HDMI monitor and then turning it on again. When the monitor is turned
on then I see a Power domain power-domain disable failed and the imprecise
Hello Hongbo,
On Mon, Jan 12, 2015 at 11:51 AM, Hongbo Zhang hongbo.zh...@linaro.org wrote:
On 9 January 2015 at 23:34, Javier Martinez Canillas
Yes, please take a look to Marek series [0]. Keep in mind that the
series does not support all sysmmu revisions so IOMMU is not supported
for some
Hello,
On 01/02/2015 02:32 PM, Javier Martinez Canillas wrote:
The mainline ChromeOS Embedded Controller (EC) driver is still missing some
features that are present in the downstream ChromiumOS tree. These are:
- Low Pin Count (LPC) interface
- User-space device interface
- Access
Hello Kukjin,
On 01/02/2015 04:24 PM, Javier Martinez Canillas wrote:
This series adds some DTS snippets that were missing in the mainline
Snow and Peach Pit/Pi Device Trees but are present in the downstream
ChromeOS kernel.
The series is composed of the following patches:
Javier
Hello Joonyoung,
On 01/12/2015 07:40 AM, Joonyoung Shim wrote:
And also making changes to the clocks in the clk-exynos5420 driver. Can
you please explain the rationale for those changes? I'm asking because
without your clock changes (only adding the DISP1 pd and making the
devices as
-by: Kevin Hilman khil...@kernel.org
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
It looks to me like a very nice cleanup.
Reviewed-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
and on an Exynos5800 Peach Pi Chromebook:
Tested-by: Javier Martinez Canillas javier.marti
[adding Marek, Sjoerd and Joonyoung that were discussing about iommu
support in another thread]
Hello Hongbo,
On Fri, Jan 9, 2015 at 8:31 AM, Hongbo Zhang hongbo.zh...@linaro.org wrote:
Add linux-samsung-soc@vger.kernel.org mailing list.
On 7 January 2015 at 18:31, Hongbo Zhang
Hello Joonyoung,
On 01/07/2015 03:03 AM, Joonyoung Shim wrote:
On 01/06/2015 06:49 PM, Javier Martinez Canillas wrote:
Also I tried forcing the kernel to not disable unused power domains by
passing the pd_ignore_unused parameter to the kernel command line. I
see on the kernel log a genpd
Hello Marek,
On Fri, Dec 5, 2014 at 11:22 AM, Marek Szyprowski
m.szyprow...@samsung.com wrote:
On 2014-12-02 10:59, Sjoerd Simons wrote:
This is another attempt to finally make Exynos SYSMMU driver fully
integrated with DMA-mapping subsystem. The main change from previous
version is a rebase
Hello Krzysztof,
Hello Kukjin,
You dropped this patch since exynos drm was causing boot hangs on some
platforms but the fix for that issue is already in linux-next (commit:
f1e9203 clk: samsung: Fix Exynos 5420 pinctrl setup and clock disable
failure due to domain being gated) so I think
Hello Kukjin,
Hello Kukjin,
Hi Javier,
Happy new year :)
Thanks, happy new year for you as well!
You dropped this patch since exynos drm was causing boot hangs on some
platforms but the fix for that issue is already in linux-next (commit:
f1e9203 clk: samsung: Fix Exynos 5420
Hello Kukjin,
On Mon, Jan 5, 2015 at 2:20 PM, Kukjin Kim kg...@kernel.org wrote:
Javier Martinez Canillas wrote:
I hope he can merge those patches as 3.19 fixes during the -rc cycle
to avoid having another kernel release with a non-working display on
Exynos5 boards.
Hi,
Hmm...Probably
Hello Paolo,
On 12/24/2014 05:36 PM, Paolo Pisati wrote:
On Wed, Dec 10, 2014 at 09:35:31AM -0800, Kevin Hilman wrote:
I confirm it fixes the boot hang in linux-next (next-20141210) on my
exynos5800-peach-pi and exynos5420-arndale-octa. Tested both
exynos_defconfig and multi_v7_defconfig.
[adding Kukjin and Vivek as cc]
Hello Paolo,
On Tue, Dec 23, 2014 at 11:16 AM, Paolo Pisati p.pis...@gmail.com wrote:
Hi,
3.19-rc1 still misses these two patches:
156823e arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
03c16e7 ARM: exynos_defconfig: Enable options for
Hello Kukjin,
This series adds some DTS snippets that were missing in the mainline
Snow and Peach Pit/Pi Device Trees but are present in the downstream
ChromeOS kernel.
The series is composed of the following patches:
Javier Martinez Canillas (4):
ARM: dts: Add power and lid GPIO keys pinctrl
-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Tested-by: Kevin Hilman khil...@linaro.org
Signed-off-by: Kukjin Kim kgene@samsung.com
---
Hello Kukjin,
You dropped this patch since exynos drm was causing boot hangs on some
platforms but the fix for that issue is already in linux
snippets were taken from the downstream ChromeOS tree.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/boot/dts/exynos5250-snow.dts | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5250-snow.dts
b/arch/arm/boot/dts
patches:
Bill Richardson (4):
mfd: cros_ec: Add cros_ec_lpc driver for x86 devices
platform/chrome: Add Chrome OS EC userspace device interface
platform/chrome: Create sysfs attributes for the ChromeOS EC.
platform/chrome: Expose Chrome OS Lightbar to users
Javier Martinez Canillas (3
The ChromeOS Embedded Controller has to be accessed by applications.
A virtual character device is used as an interface with user-space.
Extend the struct cros_ec_device with the fields needed by the driver
of this virtual character device.
Signed-off-by: Javier Martinez Canillas javier.marti
is enumerated and usable.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/boot/dts/exynos5420-peach-pit.dts | 1 +
arch/arm/boot/dts/exynos5800-peach-pi.dts | 1 +
2 files changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5420-peach-pit.dts
b/arch
the same configuration found in the ChromeOS 3.8 kernel
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/boot/dts/exynos5420-peach-pit.dts | 81 ++
arch/arm/boot/dts/exynos5800-peach-pi.dts | 81 ++
2 files
The Exynos5420 Peach Pit and Exynos5800 Peach Pi boards have both
a power and lid GPIO keys but only the former was defined in the
DTS. Add DTS snippets for the lid GPIO key too. These were taken
from the downstream ChromeOS 3.8 kernel tree.
Signed-off-by: Javier Martinez Canillas javier.marti
From: Bill Richardson wfric...@chromium.org
This patch adds a device interface to access the
Chrome OS Embedded Controller from user-space.
Signed-off-by: Bill Richardson wfric...@chromium.org
Reviewed-by: Simon Glass s...@google.com
Signed-off-by: Javier Martinez Canillas javier.marti
The ChromeOS EC character device is an user-space interface to
allow applications to access the Embedded Controller.
Add a cell for this device so it's spawned from the mfd driver.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
Changes since v1: None, new patch
From: Bill Richardson wfric...@chromium.org
This adds the LPC interface to the Chrome OS EC. Like the
I2C and SPI drivers, this allows userspace access to the EC.
Signed-off-by: Bill Richardson wfric...@chromium.org
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Reviewed-by: Olof Johansson ol...@chromium.org
Tested-by: Doug Anderson diand...@chromium.org
Reviewed-by: Benson Leung ble...@chromium.org
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
Olof,
Lee Jones suggested that this should live under drivers/led instead
Hello Laurent and Tomi,
On 12/16/2014 12:37 AM, Laurent Pinchart wrote:
Hi Javier,
Tomi and Laurent,
You asked Ajay to change his series to use the video port and enpoints DT
bindings instead of phandles, could you please review his latest version?
I guess is now too late for 3.19 since
Hello Nick,
On 12/16/2014 05:16 PM, Nick Dyer wrote:
On 15/12/14 10:39, Javier Martinez Canillas wrote:
There are different multi-touch protocols used by Atmel maXTouch touchscreen
chips. Old chips use the T9 multi-touch object type while newer chips use the
T100 multi-touch object type
Hello Nick,
On 12/16/2014 05:39 PM, Nick Dyer wrote:
On 16/12/14 16:34, Javier Martinez Canillas wrote:
On 12/16/2014 05:16 PM, Nick Dyer wrote:
Nick Dyer (1):
Input: atmel_mxt_ts - Implement support for T100 touch object
I posted an updated version of this patch on 9th December and would
Hello Nick,
On 12/16/2014 06:07 PM, Nick Dyer wrote:
On 16/12/14 16:49, Javier Martinez Canillas wrote:
Awesome, what do you think about the change to have a common input device
initialization function that I squashed in your original patch?
mxt_initialize_t100_input_device
Hello Dmitry,
There are different multi-touch protocols used by Atmel maXTouch touchscreen
chips. Old chips use the T9 multi-touch object type while newer chips use the
T100 multi-touch object type. The Atmel touch driver currently only supports
the former so this series add support for the
.
Signed-off-by: Nick Dyer nick.d...@itdev.co.uk
Acked-by: Yufeng Shen mile...@chromium.org
[javier: Factor out T9 and T100 routines to have a common init function]
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
drivers/input/touchscreen/atmel_mxt_ts.c | 258
function to simplify the former.
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
[javier: Adapt to latest driver changes and modify commit message accordingly]
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
drivers/input/touchscreen/atmel_mxt_ts.c | 48
[adding arm-soc maintainers to cc]
Hello Kukjin,
On 12/02/2014 09:39 AM, Jingoo Han wrote:
On Tuesday, December 02, 2014 5:17 PM, Javier Martinez Canillas wrote:
On Mon, Nov 24, 2014 at 6:41 AM, Vivek Gautam gautam.vi...@samsung.com
wrote:
DP PHY now require pmu-system-controller to handle
Hello,
On 11/18/2014 07:20 AM, Ajay kumar wrote:
On Sat, Nov 15, 2014 at 3:24 PM, Ajay Kumar ajaykumar...@samsung.com wrote:
This series is based on master branch of Linus tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
This series has been in the mailing lists for
snippets were taken from the downstream ChromeOS tree.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/boot/dts/exynos5250-snow.dts | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5250-snow.dts
b/arch/arm/boot/dts
Hello Kukjin,
This series adds some DTS snippets that were missing in the mainline
Snow and Peach Pit/Pi Device Trees but are present in the downstream
ChromeOS kernel.
The series is composed of the following patches:
Javier Martinez Canillas (3):
ARM: dts: Add power and lid GPIO keys pinctrl
is enumerated and usable.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/boot/dts/exynos5420-peach-pit.dts | 1 +
arch/arm/boot/dts/exynos5800-peach-pi.dts | 1 +
2 files changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5420-peach-pit.dts
b/arch
The Exynos5420 Peach Pit and Exynos5800 Peach Pi boards have both
a power and lid GPIO keys but only the former was defined in the
DTS. Add DTS snippets for the lid GPIO key too. These were taken
from the downstream ChromeOS 3.8 kernel tree.
Signed-off-by: Javier Martinez Canillas javier.marti
-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Best regards,
Javier
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello Kukjin,
On 11/13/2014 03:38 AM, Kukjin Kim wrote:
On 11/11/14 21:04, Javier Martinez Canillas wrote:
The regulator core now has support to choose if a regulator
has to be enabled or disabled during system suspend and also
supports changing the regulator operating mode during runtime
Hello Sylwester,
On 12/05/2014 12:22 PM, Sylwester Nawrocki wrote:
Tested-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Can you confirm sound works with this patch on exynos5420 ? Or does
your Tested-by refer only to successful booting ?
I tested latest linux-next + clk
-by: Jingoo Han jg1@samsung.com
Tested-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Cc: Kukjin Kim kg...@kernel.org
Any opinions about $subject?
This patch is -rc material since is needed after commit a5ec598 (phy:
exynos-dp-video: Use syscon
support to control pmu register) which
Hello Kukjin,
On 11/20/2014 02:55 AM, Kukjin Kim wrote:
Yeah, it could be a best solution at this moment. Let me revert the commit
0ef76aea7a34 (ARM: exynos_defconfig: Enable options for display panel
support)
from -next in samsung tree.
Maybe now that all the issues with the Exynos DRM
/README.
Tony added that support to OMAP2+ defconfig in commit 673ce00c
(ARM: omap2plus_defconfig: Add support for distros with systemd)
so the same should be done in exynos_defconfig.
That can of course be a follow-up patch though, so for $subject:
Reviewed-by: Javier Martinez Canillas javier.marti
tested and patches #2, #3, #4 solves the boot failure I was facing.
So for the whole series on an Exynos5420 Peach Pit:
Tested-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Thanks a lot for solving this issue.
Best regards,
Javier
--
To unsubscribe from this list: send the line
Hello Krzysztof,
On 11/25/2014 10:22 AM, Krzysztof Kozlowski wrote:
Hmmm, that's strange. I've looked again at your dmesg and it is little
different than mine (when system fails).
1. Does your PMIC come up? In your dmesg:
[2.687297] max77802-pmic max77802-pmic: regulator init failed for
Hello Krzysztof,
On 11/25/2014 03:22 PM, Krzysztof Kozlowski wrote:
Any ideas?
Yes, I got. On Peach board the i2s0 is enabled in DTS. Probing it could
fail because it relies on enabling audss clocks (which cannot be
accessed).
I reproduced another hang on Arndale Octa after enabling i2s0
Hello Krzysztof,
On 11/25/2014 03:54 PM, Krzysztof Kozlowski wrote:
My patch only fixed the gate clocks but it didn't touched div and mux.
I'll prepare a v2 of it (I got some feedback) which I hope will fix both
cases: i2s and disabling unused clocks.
Perfect, I will gladly test on Peach
Hell Krzysztof,
On 11/22/2014 11:21 AM, Krzysztof Kozlowski wrote:
By bisecting I found that the commit introducing both regressions is:
ae43b32 (ARM: 8202/1: dmaengine: pl330: Add runtime Power Management
support v12)
By reverting ae43b32, next-20141121 boots with both
On 11/24/2014 10:38 AM, Javier Martinez Canillas wrote:
Hell Krzysztof
An unfortunate typo, this was Hello of course :-)
Best regards,
Javier
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info
Hello Ajay,
On 11/21/2014 09:57 PM, Javier Martinez Canillas wrote:
On 11/21/2014 06:32 PM, Ajay kumar wrote:
Hi,
I have rebased my bridge series on top of linux-next.
This is my git log:
4b38a6f Revert Revert ARM: exynos_defconfig: Enable options for
display panel support
6fb39a7 ARM
Hello Krzysztof,
On 11/24/2014 11:13 AM, Krzysztof Kozlowski wrote:
Ok, please let me know if you need anything else from me.
Thanks! I replied before seeing your response. Anyway the dmatests are
the same I got on Arndale Octa.
It seems that mau_epll has to be enabled... or something is
Hello Vivek, Thierry,
On 11/24/2014 12:29 PM, Vivek Gautam wrote:
Yes. Back at the time a decision was made that device trees need to be
stable ABI because eventually they'd be shipped with the device rather
than the distribution. As such it may not at all be possible to update
them (they
[adding Tushar Behera and Doug Anderson to cc list]
Hello,
On 11/24/2014 12:12 PM, Krzysztof Kozlowski wrote:
On pon, 2014-11-24 at 12:07 +0100, Javier Martinez Canillas wrote:
Hello Krzysztof,
It seems that mau_epll has to be enabled... or something is wrong with
clock hierarchy
Hello Krzysztof,
On 11/24/2014 04:18 PM, Krzysztof Kozlowski wrote:
Hi,
This is initial idea to solve dependency between AudioSS clocks
and main clock controller on Exynos platform.
This solves boot failure of Peach Pi/Pit and Arndale Octa [1].
I tested this series on an Exynos5420
Hello Vivek
On Wed, Nov 19, 2014 at 1:03 PM, Vivek Gautam gautamvivek1...@gmail.com wrote:
Tested-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Thanks for testing.
You are welcome
Kukjin,
Sorry for not adding Kukjin to the list and thereby for the delay
about this patch
Hello Inki,
On 11/20/2014 06:01 PM, Inki Dae wrote:
Ah, sorry. There was my misunderstanding. drm-next already is merged
to linux-next so I think we can do the integration test if
exynos-drm-next is merged to drm-next earlier. Anyway, I will try to
consider your opinion.
Cool, having
[adding Kukjin as cc and dropping dri-devel]
Hello Kevin,
On 11/20/2014 07:22 PM, Kevin Hilman wrote:
My kernel command line is almost the same with the difference that
I'm using clk_ignore_unused and I just checked that not passing
that parameter, makes linux-next to hang showing the same
Hello Kevin,
On 11/21/2014 05:38 PM, Kevin Hilman wrote:
So, I see two different boot failures on the Peach Pi[t] Chromebooks:
1) next20141121 boot fails due snd-soc-snow
Disabling CONFIG_SND_SOC_SNOW makes the boot to got a little further
but still fails with the second issue:
2)
Hello Ajay,
On 11/21/2014 06:32 PM, Ajay kumar wrote:
Hi,
I have rebased my bridge series on top of linux-next.
This is my git log:
4b38a6f Revert Revert ARM: exynos_defconfig: Enable options for
display panel support
6fb39a7 ARM: dts: peach-pit: represent the connection between bridge
Hello Vivek,
On 11/20/2014 08:51 AM, Vivek Gautam wrote:
I tested linux-next on Exynos5800 peach-pi board with linux-next and and the
two
patches $Subject and [0].
Below is my git hash:
4d9e6ee drm/exynos: Move platform drivers registration to module init
4545ed4 POSTED: arm: dts:
Hello Inki,
On Thu, Nov 20, 2014 at 2:56 PM, Inki Dae inki@samsung.com wrote:
If you try to build exynosdrm as module you will receive errors due to
multiple definitions of init_module, ie module_init/module_*_driver
macros can be used once per module.
Ah, right. we had ever tried same
Hello Inki,
On 11/20/2014 03:07 PM, Inki Dae wrote:
Could you re-base this patch on top of exynos-drm-next? I tried to
separate sub drivers into independent drivers but it seems that we need
more times. So I will merge your patch.
Sure, I'll rebase on top of exynos-drm-next and re-post so
Hello Inki,
On 11/20/2014 04:06 PM, Inki Dae wrote:
BTW, it would be great if exynos-drm-next is pulled in linux-next. That is
what most people use to test integration issues so you can catch earlier any
regression that may arise.
You have to email Stephen Rothwell s...@canb.auug.org.au and
Hello Paolo,
On 11/20/2014 04:57 PM, Paolo Pisati wrote:
On Thu, Nov 20, 2014 at 03:22:23PM +0530, Vivek Gautam wrote:
On linux-samsung tree the only patch that's missing apart from dptx-phy
patches
is the syscon patch from Pankaj Dubey:
b784b98 mfd: syscon: Decouple syscon interface from
Hello,
For completeness I'll comment what we talked with Kevin on IRC
since probably this is the same issue that Paolo is facing.
On 11/20/2014 05:41 PM, Kevin Hilman wrote:
Peach # setenv preboot usb start; sleep 1setenv bootargs console=tty1
console=ttySAC3,115200 debug earlyprintk rw
Hello Ajay,
On 11/18/2014 07:20 AM, Ajay kumar wrote:
On Sat, Nov 15, 2014 at 3:24 PM, Ajay Kumar ajaykumar...@samsung.com wrote:
This series is based on master branch of Linus tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
I applied your series on top of 3.18-rc5 +
Hello Ajay,
On 11/19/2014 10:38 AM, Ajay kumar wrote:
Hi Javier,
In the cover letter, I have mentioned that it is tested on Linus tree:
This series is based on master branch of Linus tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Kindly test the patches with
Hello Doug,
Thanks for your feedback.
On 11/18/2014 06:50 PM, Doug Anderson wrote:
This is common practice in the Chrome OS tree, but we've gotten
pushback from upstream questioning about whether spidev is really a
physical device. See:
Hello Kevin,
On 11/18/2014 11:46 PM, Kevin Hilman wrote:
Is anyone at Samsung testing linux-next? If so, on what platforms? It
would really be nice if your linux-next work was tested on these
publically-available 542x/5800 platforms (peach-pi, peach-pit,
odroid-xu3) which would also allow
Hello Kukjin,
On 11/19/2014 09:09 AM, Kukjin Kim wrote:
You say that you will apply this patch but I can't find it in any of
your branches.
Sorry for missing the patch in my tree. You can see it in a couple of
mins ;)
Great, thanks a lot!
Best regards,
Javier
--
To unsubscribe from
for the pointer!
If someone else is interested, I've pushed a branch [0] with 3.18-rc5 + all
the needed patches.
Ajay, feel free to add to your series:
Tested-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Best regards,
Javier
[0]: git://git.collabora.co.uk/git/user/javier/linux.git wip
-phy
node.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Cc: Jingoo Han jg1@samsung.com
Reviewed-by: Jingoo Han jg1@samsung.com
Tested-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Kukjin,
This patch is -rc material and is needed to have display working in
3.18
Hello Paolo,
On 11/19/2014 05:22 PM, Paolo Pisati wrote:
On Wed, Nov 19, 2014 at 12:20:53PM +0100, Javier Martinez Canillas wrote:
If someone else is interested, I've pushed a branch [0] with 3.18-rc5 + all
the needed patches.
Ajay, feel free to add to your series:
Tested-by: Javier
[adding Paolo and Vivek as cc]
Hello,
On 11/18/2014 07:41 PM, Kevin Hilman wrote:
It fixes the DRM deadlock, issue for me on exynos5800-peach-pi, but then
it proceeds to panic in the workqueue code called by the asoc max98090
codec[1].
If I then disable CONFIG_SND_SOC_SNOW, I can get it
anyways.
Patch looks good to me though:
Reviewed-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Best regards,
Javier
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
Hello Andreas,
On 11/19/2014 04:56 PM, Andreas Färber wrote:
multi_v7_defconfig has it as Y already, so build it in here, too, for
consistency, and therefore build in HWMON as well.
Signed-off-by: Andreas Färber afaer...@suse.de
Reviewed-by: Javier Martinez Canillas javier.marti
Hello Andreas,
On 11/19/2014 04:56 PM, Andreas Färber wrote:
The HP Chromebook 11 uses an Atmel maXTouch as trackpad.
The keymap was found by trial-and-error.
Signed-off-by: Andreas Färber afaer...@suse.de
Patch looks good to me.
Reviewed-by: Javier Martinez Canillas javier.marti
Hello Doug,
On 11/19/2014 06:19 PM, Doug Anderson wrote:
I wonder how the spidev user-space interface is supposed to be used
when booting with Device Trees.
OK. Please don't take my comments as a NAK on this patch. I should
have done the same grep myself before sending--sorry. I just
Hello Mark,
On 11/19/2014 06:47 PM, Mark Brown wrote:
These are bugs. The device tree should describe the hardware, spidev is
a Linux implementation detail. Provide a compatible string for the
device that is there just as you would for any other device.
Thanks a lot for your explanation.
Hello Inki,
Right, but at least, we could avoid kernel booting failure which is very
critical. Please know that this patch is temporary to avoid the kernel
booting failure although deferred probe request of Exynos drm could be
broken. For this, I will look into dd core to find out more
Hello Andrzej,
On Tue, Nov 18, 2014 at 11:48 AM, Andrzej Hajda a.ha...@samsung.com wrote:
So we have two issues here and your patch is only a workaround for the later.
This is the same issue Krzysztof reported two weeks ago and I answered
him with my diagnosis[1].
[1]:
[adding Kevin to cc list]
Hello Inki,
On Tue, Nov 18, 2014 at 11:52 AM, Inki Dae inki@samsung.com wrote:
On 2014년 11월 18일 19:42, Andrzej Hajda wrote:
On 11/06/2014 10:06 AM, Krzysztof Kozlowski wrote:
Hi,
On last next (next-20141104, next-20141105) booting locks after
initializing
to get interrupt.
I'm not familiar with this board but the patch looks good to me
assuming the IRQ is the correct one.
Reviewed-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Best regards,
Javier
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc
):
ARM: dts: Add spidev registration to exynos5250-snow
Javier Martinez Canillas (1):
ARM: exynos_defconfig: Enable user mode SPI device support
Simon Glass (1):
ARM: dts: Add SPI flash node for Peach boards
arch/arm/boot/dts/exynos5250-snow.dts | 20
arch/arm
601 - 700 of 1325 matches
Mail list logo
