On Sat, 2015-11-07 at 21:40 +0900, Krzysztof Kozlowski wrote:
> W dniu 06.11.2015 o 20:11, Sjoerd Simons pisze:
> > When a transfer completes there is a small window between the
> > descriptor
> > being unset as the current active one in the thread and it being
> > mark
change underneath it.
Signed-off-by: Sjoerd Simons <sjoerd.sim...@collabora.co.uk>
---
drivers/dma/pl330.c | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/drivers/dma/pl330.c b/drivers/dma/pl330.c
index 17ee758..6c8243b 100644
--- a/drivers/dma/pl330.c
+++ b/d
On Thu, 2015-10-08 at 16:41 +0200, Arnd Bergmann wrote:
> On Thursday 08 October 2015 11:27:13 Sjoerd Simons wrote:
> > On Thu, 2015-10-08 at 10:37 +0200, Arnd Bergmann wrote:
> > > On Thursday 08 October 2015 16:46:27 Krzysztof Kozlowski wrote:
> > > > On 08.10.2
without further comments when I indicated in the
cover letter that i used the NFS root use-case as one of the deciding
factors for y vs. m).
It would be really good to see someone put their foot down on the
general policy (e.g. the arm-soc maintainers?), such that this
discussion doesn't need to happen every time :)
--
Sjoerd Simons
Collabora Ltd.
--
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
15-September/0
04280.html
> From my point of view this is the same case as USB_NET_SMSC75XX or
> USB_NET_SMSC95XX, so:
> 1. Reviewed-by: Krzysztof Kozlowski <k.kozlow...@samsung.com>
> 2. +1 for CONFIG_PHY_SAMSUNG_USB2=y (regardless of fixing issues in
> the driver)
, it should be tested in kernelci before
appearing
in linux-next to prevent any boot issues.
I've pushed this patch into Collabora's for-next branch, which should
get picked up by kernelci soonish.
--
Sjoerd Simons
Collabora Ltd.
--
To unsubscribe from this list: send the line unsubscribe linux
:)
+ while (!pmu_raw_readl(S5P_PMU_SPARE2))
+ udelay(10);
Would love to see some documentation for this magical pmu register, but
i guess you can't have them all :)
--
Sjoerd Simons sjoerd.sim...@collabora.co.uk
Collabora Ltd.
--
To unsubscribe
turning the output signal low at
the end of a duty cycle. However if you turn off the clock at the start
of a duty cycle while the output signal is still high it will
unexpectedly remain high.
--
Sjoerd Simons sjoerd.sim...@collabora.co.uk
Collabora Ltd.
--
To unsubscribe from this list: send the line
On Wed, 2015-04-08 at 10:28 +0200, Lukasz Majewski wrote:
Hi Anand,
From: Sjoerd Simons sjoerd.sim...@collabora.co.uk
When disabling the samsung PWM the output state remains at the level
it was in the end of a pwm cycle. In other words, calling pwm_disable
when at 100% duty will keep
, but i might have missed it ofcourse. Seems
patchwork also missed it though:
https://patchwork.ozlabs.org/patch/446643/
Mind redoing you're acked-by so it gets picked up by patchwork ? :)
On Thu, 2015-03-05 at 09:14 +0100, Sjoerd Simons wrote:
When disabling the samsung PWM the output
Hey Jingoo, Kukjijn, Lukasz,
Pinging on this one again, could you please review this patch so it can
be merged through the PWM tree?
On Thu, 2015-03-05 at 09:14 +0100, Sjoerd Simons wrote:
When disabling the samsung PWM the output state remains at the level it
was in the end of a pwm cycle
-introducing the issues 3bdf878 (flickering
as the PWM got reset while in a PWM cycle). Only force an update of the
settings when at 100% duty, which shouldn't have a noticeable effect on
the output but is enough to ensure the behaviour is as expected on
disable.
Signed-off-by: Sjoerd Simons sjoerd.sim
+To Kukjin
Jingoo, Kukjin, could one of you review this patch to ensure it's the
right thing to do on samsung hardware?
On Thu, 2015-01-22 at 22:41 +0100, Sjoerd Simons wrote:
When disabling the samsung PWM the output state remains at the level it
was in the end of a pwm cycle. In other words
is for a pwrseq driver vs. it
being part of the mmc core would be. But if you do a pwrseq driver it
shouldn't be board specific e.g. call it mmc-pwrseq-emmc4.4 instead of
-odroid?
--
Sjoerd Simons sjoerd.sim...@collabora.co.uk
Collabora Ltd.
smime.p7s
Description: S/MIME cryptographic signature
On Tue, 2015-01-27 at 09:11 +0100, Marek Szyprowski wrote:
Hello,
This patchset fixes reboot hang issue on Hardkernel's Odroid boards with
eMMC card. Those boards are designed in such a way, that the eMMC nreset
signal is routed to SoC GPIO line instead of the board reset logic. To
properly
;
+ reg = 0x4000 0x7EA0;
};
chosen {
--
Just checked hardkernels bootloader which defines:
#define CONFIG_TRUSTZONE_RESERVED_DRAM 0x160
So looks good,
Reviewed-By: Sjoerd Simons sjoerd.sim...@collabora.co.uk
Hi,
Maybe is it related to the SoC not only
hooked up on the peach
pi chromebook for example and i would expect it to be hooked up on most
board with an eMMC
This change is consistent with most of the special purpose GPIO pins
defined in that file, so i don't see the problem with including it in
that pinctrl file
--
Sjoerd Simons sjoerd.sim
;
};
+ sd0_rst: sd0-rst {
+ samsung,pins = gpd1-0;
+ samsung,pin-function = 1;
I think this should be samsung,pin-function = 2; for that
functionality.
--
Sjoerd Simons sjoerd.sim...@collabora.co.uk
Collabora Ltd.
smime.p7s
Description
-introducing the issues 3bdf878 (flickering
as the PWM got reset while in a PWM cycle). Only force an update of the
settings when at 100% duty, which shouldn't have a noticeable effect on
the output but is enough to ensure the behaviour is as expected on
disable.
Signed-off-by: Sjoerd Simons sjoerd.sim
correctly.
Reviewed-By: Sjoerd Simons sjoerd.sim...@collabora.co.uk
Cc: Javier Martinez Canillas javier.marti...@collabora.co.uk
Cc: Sjoerd Simons sjoerd.sim...@collabora.co.uk
Signed-off-by: Kevin Hilman khil...@linaro.org
---
v2: use ti,ina231 as compatible string.
Applies on top of ARM
display.
Tested-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
--
Sjoerd Simons sjoerd.sim...@collabora.co.uk
Collabora Ltd.
smime.p7s
Description: S/MIME cryptographic signature
happen to have a git branch with these patches in? That would
make it convenient for me to give your patches a spin on my XU3
--
Sjoerd Simons sjoerd.sim...@collabora.co.uk
Collabora Ltd.
smime.p7s
Description: S/MIME cryptographic signature
: VDD_ARM
- A7 cluster: VDD_KFC
- GPU: VDD_G3D
- memory: VDD_MEM
In addition to adding the sensors, LDO26 from the PMIC needs to be
enabled because it's powering these sensor.
Cc: Javier Martinez Canillas javier.marti...@collabora.co.uk
Cc: Sjoerd Simons sjoerd.sim...@collabora.co.uk
Signed
On Wed, 2015-01-07 at 23:49 +, Jonathan Stone -SISA wrote:
On On Wed, 2015-01-07 at 18:37 +, Sjoerd Simons writes wrote:
On Wed, 2015-01-07 at 18:37 +, Anand Moon wrote:
[...]
Only 4 core cpu's are on my board. Also CpuFreq is not working.
Can you share some point
Add DTS for the Hardkernel Odroid XU3. The name of the DTS file is kept the
same as the vendors naming, which means it's prefixed with exynos5422
instead of exynos5800 as the SoC name even though it includes the
exyno5800 dtsi.
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
Also setup memory allocations for version 8 of the MFC as present in
Samsung Exynos 5422/5800 SoCs
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
---
arch/arm/mach-exynos/exynos.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-exynos/exynos.c b/arch/arm/mach-exynos
-introducing the issues 3bdf878 (flickering
as the PWM got reset while in a PWM cycle). Only force an update of the
settings when at 100% duty, which shouldn't have a noticeable effect on
the output but is enough to ensure the behaviour is as expected on
disable.
Signed-off-by: Sjoerd Simons sjoerd.sim
[ 46.590494] init: failsafe main process (2550) killed by TERM signal
[ 50.596528] smsc95xx 5-1.1:1.0 eth0: hardware isn't capable of remote
wakeup
-Anand Moon
On Monday, January 5, 2015 9:00 PM, Sjoerd Simons
sjoerd.sim...@collabora.co.uk wrote:
On Mon, 2015-01-05 at 17:18 +0900
?
--
Sjoerd Simons sjoerd.sim...@collabora.co.uk
Collabora Ltd.
smime.p7s
Description: S/MIME cryptographic signature
infrastructure turns it off as soon as it gets into
control, which works quite nicely (and keeps my sanity as that fan at
100% is *loud*)... So if you want to avoid unpleasant sounds, just
build with thermal :p
--
Sjoerd Simons sjoerd.sim...@collabora.co.uk
Collabora Ltd.
smime.p7s
Description: S/MIME
On Mon, 2015-01-05 at 17:18 +0900, Joonyoung Shim wrote:
Hi Sjoerd,
On 12/05/2014 04:27 AM, Sjoerd Simons wrote:
Add DTS for the Hardkernel Odroid XU3. The name of the DTS file is kept the
same as the vendors naming, which means it's prefixed with exynos5422
instead of exynos5800
On Thu, 2014-12-18 at 11:13 +0100, Lukasz Majewski wrote:
Several new properties to allow PWM fan working as a cooling device have been
combined into this single commit.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
.../devicetree/bindings/hwmon/pwm-fan.txt | 28
Add DTS for the Hardkernel Odroid XU3. The name of the DTS file is kept the
same as the vendors naming, which means it's prefixed with exynos5422
instead of exynos5800 as the SoC name even though it includes the
exyno5800 dtsi.
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
Also setup memory allocations for version 8 of the MFC as present in
Samsung Exynos 5422/5800 SoCs
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
---
arch/arm/mach-exynos/exynos.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-exynos/exynos.c b/arch/arm/mach-exynos
On Wed, 2014-12-03 at 11:53 -0800, Kevin Hilman wrote:
Sjoerd Simons sjoerd.sim...@collabora.co.uk writes:
Tried this on top of linux-next (next-20141125 and next20141203) and
boots fine on my odroid-xu3.
Thanks for doing this, I've been meaning to get a DTS upstream for this
platform
On Tue, 2014-12-02 at 15:17 +0900, Heesub Shin wrote:
Hello Simons,
On 12/01/2014 09:59 PM, Sjoerd Simons wrote:
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free
--
Sjoerd Simons sjoerd.sim...@collabora.co.uk
Collabora Ltd.
smime.p7s
Description: S/MIME cryptographic signature
Add DTS for the Hardkernel Odroid XU3. The name of the DTS file is kept the
same as the vendors naming, which means it's prefixed with exynos5422
instead of exynos5800 as the SoC name even though it includes the
exyno5800 dtsi.
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
---
arch
CONFIG_FHANDLE is required by systemd, which is the default init system
in more and more distributions. So lets enable it for Exynos as well
(it's already enabled in multi_v7_defconfig)
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
---
arch/arm/configs/exynos_defconfig | 1 +
1 file
On Tue, 2014-11-18 at 12:20 +0900, Inki Dae wrote:
This patch makes the deferred probe is tried up to 3 times in maximum.
However, this is considered only for Exynos drm so I think other SoC
drivers could also produce same issue. Therefore, the best way to resolve
this issue, infinite loop
Explicitly set the dr_mode for the dwc3 controller on the
Snow board to host mode. This is required to ensure the
controller is initialized in the right mode if the kernel is
build with USB gadget support.
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
---
arch/arm/boot/dts
On Thu, 2014-11-06 at 23:10 +0900, Inki Dae wrote:
This patch resovles the infinite loop issue incurred
when Exyno drm driver is enabled but all kms drivers
are disabled on Exynos board by returning -EPROBE_DEFER
only in case that there is kms device registered.
It would be nice if you could
:
5c42acdb9bab595482b966b22ab5e2f6f359
dbb62ef9ade6e92737d3fac199665b8b7c455959
Might be good to cherry-pick those into for-next at this point (they're
rather trivial)
--
Sjoerd Simons sjoerd.sim...@collabora.co.uk
Collabora Ltd.
smime.p7s
Description: S/MIME cryptographic signature
Explicitly set the dr_mode for the second dwc3 controller on the
Arndale Octa board to host mode. This is required to ensure the
controller is initialized in the right mode if the kernel is build with
USB gadget support
Reported-By: Andreas Färber afaer...@suse.de
Signed-off-by: Sjoerd Simons
Enable USB gadget support without support for any specific gadgets to
more easily catch cases where a devices dts doesn't specify the usb
controllers dr_mode while it should.
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
---
Changes in v4: Rebased on linux-samsung for-next
arch
for arndale octa
Changes in v4: Rebased on todays linux-samsungs for-next branch
Sjoerd Simons (3):
ARM: dts: exynos: Explicitly set dr_mode on peach-pit and peach-pi
ARM: dts: exynos: Explicitly set dr_mode on arndale-octa
ARM: exynos_defconfig: enable USB gadget support
arch/arm/boot/dts
with such a kernel configuration unless manually
change the mode. To resolve that explicitly configure the dual role
mode as host
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
Reviewed-by: Andreas Färber afaer...@suse.de
---
Changes in v2: alphabetically sort the dts entries
Changes in v3: Fix
-firmware.git/
Unfortunately there is no specific version information included about
the firmware. The commit that added it is fb5cda9c70277f6 dated Nov 28
17:43:06 2012 +0530, so that at least gives some information about the
time-frame.
--
Sjoerd Simons sjoerd.sim...@collabora.co.uk
Collabora
in no frame ever being output from the
decoder.
This patch reverts MFC v5 to the previous behaviour while keeping the
new behaviour for v6 and up.
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
---
drivers/media/platform/s5p-mfc/s5p_mfc.c | 7 ++-
1 file changed, 6 insertions
if this would fail to make it for 3.18 (one could
even argue the dt patches are 3.17 RC material!) as it fixes USB
functionality being broken depending on the kernel configuration used.
On Mon, 2014-09-15 at 12:52 +0200, Sjoerd Simons wrote:
When building a kernel with support for both USB host
in these series add the requird of match information to the EC
subdevices
I guess the first patch should through the i2c tree while the second one would
be for the input tree?
Sjoerd Simons (2):
i2c: cros-ec-tunnel: Add of match table
input: cros_ec_keyb: Add of match table
drivers/i2c/busses/i2c
To enable the cros_ec_keyb driver to be auto-loaded when build as
module add an of match table (and export it) to match the modalias
information passed on to userspace as the Cros EC MFD driver registers
the MFD subdevices with an of_compatibility string.
Signed-off-by: Sjoerd Simons sjoerd.sim
To enable the cros-ec-tunnel driver to be auto-loaded when build as a
module add an of match table (and export it) to match the modalias
information passed on to userspace as the Cros EC MFD driver registers
the MFD subdevices with an of_compatibility string.
Signed-off-by: Sjoerd Simons
with such a kernel configuration unless manually
change the mode. To resolve that explicitly configure the dual role
mode as host
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
Reviewed-by: Andreas Färber afaer...@suse.de
---
Changes in v2: alphabetically sort the dts entries
Changes in v3
DTS might need similar changes, so it would be
great if users of those board could verify this.
Changes in v2: alphabetically sort the dts entries
Changes in v3: Add DTS updates for arndale octa
Sjoerd Simons (3):
ARM: dts: exynos: Explicitly set dr_mode on peach-pit and peach-pi
ARM: dts
Explicitly set the dr_mode for the second dwc3 controller on the
Arndale Octa board to host mode. This is required to ensure the
controller is initialized in the right mode if the kernel is build with
USB gadget support
Reported-By: Andreas Färber afaer...@suse.de
Signed-off-by: Sjoerd Simons
Enable USB gadget support without support for any specific gadgets to
more easily catch cases where a devices dts doesn't specify the usb
controllers dr_mode while it should.
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
---
arch/arm/configs/exynos_defconfig | 1 +
1 file changed, 1
Hey Lee,
On Wed, 2014-09-10 at 10:28 +0100, Lee Jones wrote:
On Tue, 09 Sep 2014, Javier Martinez Canillas wrote:
[adding Lee Jones to cc list since I'm referring on a series he posted]
Hello Sjoerd,
On 09/09/2014 09:52 AM, Sjoerd Simons wrote:
For i2c devices in OF the modalias
-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
---
drivers/input/touchscreen/atmel_mxt_ts.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c
b/drivers/input/touchscreen/atmel_mxt_ts.c
index db178ed..57ff26d 100644
--- a/drivers/input
On Tue, 2014-09-09 at 11:29 +0100, Nick Dyer wrote:
On 09/09/14 11:21, Javier Martinez Canillas wrote:
On 09/09/2014 09:52 AM, Sjoerd Simons wrote:
For i2c devices in OF the modalias exposed to userspace is i2c:node
type, for the Maxtouch driver this is i2c:maxtouch.
Add maxtouch
On Wed, 2014-08-27 at 03:38 +0200, Andreas Färber wrote:
Am 26.08.2014 09:30, schrieb Sjoerd Simons:
Enable USB gadget support without support for any specific gadgets to
more easily catch cases where a devices dts doesn't specify the usb
controllers dr_mode while it should.
Signed-off
On Wed, 2014-08-27 at 04:08 +0200, Andreas Färber wrote:
Hi,
Am 26.08.2014 09:30, schrieb Sjoerd Simons:
I suspect other boards base using exynos5420/5800 might need the similar
fixes
(Arndale Octa and Samsung SMDK5420) to their dts files, so would be great if
folks with those board
SMDK5420) to their dts files, so would be great if
folks with those board could verify this.
Changes in v2: alphabetically sort the dts entries
Sjoerd Simons (2):
ARM: dts: exynos: Explicitly set dr_mode on peach-pit and peach-pi
ARM: exynos_defconfig: enable USB gadget support
arch/arm/boot/dts
Enable USB gadget support without support for any specific gadgets to
more easily catch cases where a devices dts doesn't specify the usb
controllers dr_mode while it should.
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
---
Changes in v2: none
arch/arm/configs/exynos_defconfig
with such a kernel configuration unless manually
change the mode. To resolve that explicitely configure the dual role
mode as host
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
---
Changes in v2: alphabetically sort the dts entries
arch/arm/boot/dts/exynos5420-peach-pit.dts | 8
To enable the cros-ec-tunnel driver to be auto-loaded when build as a
module add an of match table (and export it) to match the modalias
information passed on to userspace as the Cros EC MFD driver registers
the MFD subdevices with an of_compatibility string.
Signed-off-by: Sjoerd Simons
To enable the cros_ec_keyb driver to be auto-loaded when build as
module add an of match table (and export it) to match the modalias
information passed on to userspace as the Cros EC MFD driver registers
the MFD subdevices with an of_compatibility string.
Signed-off-by: Sjoerd Simons sjoerd.sim
they need to
export the necessary module aliases based to match the of information.
The two patches in these series add the requird of match information to the EC
subdevices
Changes in v2: Fix stray newline and indentation issues in the first patch
Sjoerd Simons (2):
i2c: cros-ec-tunnel: Add
Hey,
On Sat, 2014-08-23 at 17:42 +0400, Sergei Shtylyov wrote:
Hello.
On 8/23/2014 3:03 AM, Sjoerd Simons wrote:
To enable the cros_ec_keyb driver to be auto-loaded when build as
module add an of match table (and export it) to match the modalias
information passed on to userspace
.
--
Sjoerd Simons sjoerd.sim...@collabora.co.uk
Collabora Ltd.
smime.p7s
Description: S/MIME cryptographic signature
Add a MODULE_DEVICE_TABLE call for OF match tables. This allows the
module to be autoloaded based on devicetree information.
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
---
drivers/phy/phy-exynos5-usbdrd.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/phy/phy-exynos5
with such a kernel configuration unless manually
change the mode. To resolve that explicitely configure the dual role
mode as host
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
---
arch/arm/boot/dts/exynos5420-peach-pit.dts | 8
arch/arm/boot/dts/exynos5420.dtsi | 4
SMDK5420) to their dts files, so would be great if
folks with those board could verify this.
Sjoerd Simons (2):
ARM: dts: exynos: Explicitly set dr_mode on peach-pit and peach-pi
ARM: exynos_defconfig: enable USB gadget support
arch/arm/boot/dts/exynos5420-peach-pit.dts | 8
arch/arm/boot
Enable USB gadget support without support for any specific gadgets to
more easily catch cases where a devices dts doesn't specify the usb
controllers dr_mode while it should.
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
---
arch/arm/configs/exynos_defconfig | 1 +
1 file changed, 1
they need to
export the necessary module aliases based to match the of information.
The two patches in these series add the requird of match information to the EC
subdevices
Sjoerd Simons (2):
i2c: cros-ec-tunnel: Add of match table
input: cros_ec_keyb: Add of match table
drivers/i2c/busses
To enable the cros-ec-tunnel driver to be auto-loaded when build as a
module add an of match table (and export it) to match the modalias
information passed on to userspace as the Cros EC MFD driver registers
the MFD subdevices with an of_compatibility string.
Signed-off-by: Sjoerd Simons
To enable the cros_ec_keyb driver to be auto-loaded when build as
module add an of match table (and export it) to match the modalias
information passed on to userspace as the Cros EC MFD driver registers
the MFD subdevices with an of_compatibility string.
Signed-off-by: Sjoerd Simons sjoerd.sim
On Tue, 2014-07-29 at 14:38 +0900, Inki Dae wrote:
On 2014년 07월 28일 23:45, Sjoerd Simons wrote:
Hey Inki,
On Mon, 2014-07-28 at 23:17 +0900, Inki Dae wrote:
On 2014년 07월 28일 17:30, Sjoerd Simons wrote:
Sorry for late,
I don't see why Exynos drm driver should be auto-loaded module
Hey Inki,
On Mon, 2014-07-21 at 08:50 +0200, Sjoerd Simons wrote:
Hey Inki,
On Mon, 2014-07-21 at 12:02 +0900, Inki Dae wrote:
On 2014년 07월 19일 05:36, Sjoerd Simons wrote:
The exynos DRM module currently is not automatically loaded when build as
a
module. This is due to the simple
Hey Inki,
On Mon, 2014-07-28 at 23:17 +0900, Inki Dae wrote:
On 2014년 07월 28일 17:30, Sjoerd Simons wrote:
Sorry for late,
I don't see why Exynos drm driver should be auto-loaded module. I think
all devices covered by Exynos drm framework are not hot-plugged. Maybe
there is my missing point
Hey Inki,
On Mon, 2014-07-21 at 12:02 +0900, Inki Dae wrote:
On 2014년 07월 19일 05:36, Sjoerd Simons wrote:
The exynos DRM module currently is not automatically loaded when build as a
module. This is due to the simple fact that it doesn't have any
MODULE_DEVICE_TABLE entries whatsoever
to MODULE_DEVICE_TABLE
in one module, however commit 21bdd17b21b45ea solved that.
The first two patches revert the previous removals of MODULE_DEVICE_TABLE
calls, while the last one adds calls for the remaining OF match tables without a
MODULE_DEVICE_TABLE call.
Sjoerd Simons (3):
Revert drm/exynos: fix module build
Add MODULE_DEVICE_TABLE calls for the various OF match tables that
currently don't have one. This allows the module to be
autoloaded based on devicetree information.
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos_drm_fimc.c| 1 +
drivers/gpu/drm
the patch can be
reverted to restore support for autoloading
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos_dp_core.c | 1 +
drivers/gpu/drm/exynos/exynos_drm_dsi.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/exynos
21bdd17b21b45ea48e06e23918d681afbe0622e9 it is possible to have
multiple calls to MODULE_DEVICE_TABLE, so the patch can be
reverted to restore support for autoloading
Conflicts:
drivers/gpu/drm/exynos/exynos_drm_fimd.c
drivers/gpu/drm/exynos/exynos_drm_g2d.c
Signed-off-by: Sjoerd Simons sjoerd.sim
Allow phy-exynos-usb2 to be autoloaded based on devicetree information.
Tested on Odroid X2 with its USB subsystem build as modules.
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
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
+++ b/drivers/phy
entries.
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
---
arch/arm/boot/dts/exynos5250-arndale.dts | 4
arch/arm/boot/dts/exynos5250.dtsi| 15 ---
2 files changed, 19 deletions(-)
diff --git a/arch/arm/boot/dts/exynos5250-arndale.dts
b/arch/arm/boot/dts
88 matches
Mail list logo
