This patch returns error when 'dma-cells' property not found
in the corresponding device node. With out this change there
is a crash in the generic dma incompatible platforms.
Signed-off-by: Padmavathi Venna padm...@samsung.com
---
Based on Vinod Koul next branch.
drivers/dma/of-dma.c |8
This patch register the dma controller with generic dma helpers only
in DT case. This also adds some extra error handling in the driver.
Signed-off-by: Padmavathi Venna padm...@samsung.com
Reported-by: Sachin Kamat sachin.ka...@linaro.org
---
Based on Vinod Koul next branch.
Changes since V1:
On 03/05/2013 03:25 AM, Padmavathi Venna wrote:
This patch returns error when 'dma-cells' property not found
in the corresponding device node. With out this change there
is a crash in the generic dma incompatible platforms.
Signed-off-by: Padmavathi Venna padm...@samsung.com
NAK.
This patch removes custom way of adding spi dma channels and
adds according to new generic DMA DT bindings on samsung exynos4
and exynos5440 platforms.
Signed-off-by: Padmavathi Venna padm...@samsung.com
---
arch/arm/boot/dts/exynos4.dtsi| 15 +--
On Tue, Mar 5, 2013 at 3:13 PM, Rob Herring robherri...@gmail.com wrote:
On 03/05/2013 03:25 AM, Padmavathi Venna wrote:
This patch returns error when 'dma-cells' property not found
in the corresponding device node. With out this change there
is a crash in the generic dma incompatible
On 5 March 2013 15:34, Padmavathi Venna padm...@samsung.com wrote:
This patch removes custom way of adding spi dma channels and
adds according to new generic DMA DT bindings on samsung exynos4
and exynos5440 platforms.
Signed-off-by: Padmavathi Venna padm...@samsung.com
---
On Tuesday 05 March 2013 03:43:52 Rob Herring wrote:
On 03/05/2013 03:25 AM, Padmavathi Venna wrote:
This patch returns error when 'dma-cells' property not found
in the corresponding device node. With out this change there
is a crash in the generic dma incompatible platforms.
On Tue, Mar 5, 2013 at 3:36 PM, Sachin Kamat sachin.ka...@linaro.org wrote:
On 5 March 2013 15:34, Padmavathi Venna padm...@samsung.com wrote:
This patch removes custom way of adding spi dma channels and
adds according to new generic DMA DT bindings on samsung exynos4
and exynos5440 platforms.
On 03/05/2013 11:06 AM, Sachin Kamat wrote:
On 5 March 2013 15:34, Padmavathi Venna padm...@samsung.com wrote:
This patch removes custom way of adding spi dma channels and
adds according to new generic DMA DT bindings on samsung exynos4
and exynos5440 platforms.
Signed-off-by: Padmavathi
This patch removes custom way of adding spi dma channels and
adds according to new generic DMA DT bindings on samsung exynos4
and exynos5440 platforms.
Signed-off-by: Padmavathi Venna padm...@samsung.com
---
Changes since V1:
- Corrected the pdma phandle in spi1 node.
On 03/05/2013 04:15 AM, Arnd Bergmann wrote:
On Tuesday 05 March 2013 03:43:52 Rob Herring wrote:
On 03/05/2013 03:25 AM, Padmavathi Venna wrote:
This patch returns error when 'dma-cells' property not found
in the corresponding device node. With out this change there
is a crash in the generic
The move is necessary to support early debug output
on exynos with multiplatform configurations. This
implies also moving the plat/debug-macro.S file, but
we are leaving the remaining users of that file
in place, to avoid adding large numbers of extra
configuration options to Kconfig.debug
No other file in the kernel besides i2c-s3c2410.c uses
the current plat/regs-iic.h, so we can simply move the
header file to live in the same directory as the driver,
as a preparation to multiplatform builds.
Signed-off-by: Arnd Bergmann a...@arndb.de
---
arch/arm/mach-s3c24xx/mach-rx1950.c
Nothing outside of the rtc driver includes plat/regs-rtc.h,
so we can simply move the file into the same directory,
which allows us to build the file as platform-independent
code.
Signed-off-by: Arnd Bergmann a...@arndb.de
---
arch/arm/plat-samsung/include/plat/regs-rtc.h | 71
When we enable CONFIG_SPARSE_IRQ, we have to set the
value of NR_IRQS in the machine_desc for legacy IRQ
domains, and any file referring to the number of
interrupts or a specific number must include the
mach/irqs.h header file explicitly.
Signed-off-by: Arnd Bergmann a...@arndb.de
---
Multiplatform kernels rely on the common clock implementation,
which conflicts with Samsung's own implementation of the same
interface. This disables all code that provides or requires
the nonstandard version.
Signed-off-by: Arnd Bergmann a...@arndb.de
---
arch/arm/mach-exynos/Makefile|
As a preparation for multiplatform support, this introduces
a new Kconfig symbol to split the ATAGS based EXYNOS platforms
from the DT based ones. Turning off CONFIG_EXYNOS_ATAGS disables
all platforms that are not yet converted to DT, and we can
have code that relies on DT checking for this
This enables the exynos platform to be selected as part
of a CONFIG_ARCH_MULTIPLATFORM kernel. This still
breaks a number of drivers, which we will have to
enable again one by one. Single-platform configurations
should not be impacted by this.
Signed-off-by: Arnd Bergmann a...@arndb.de
---
The definitions have moved to include/linux/usb/samsung-usb-phy.h,
and plat/usb-phy.h is unavailable from drivers in a multiplatform
configuration.
Also fix up the plat/usb-phy.h header file to use the definitions
from the new header instead of providing a separate copy.
Signed-off-by: Arnd
Hi everyone,
Although I'm not present at the Linaro Connect hacking
sessions, I am participating remotely and have tried
hacking on multiplatform support for Exynos. This patch
set is far from complete, but I think the patches
can be useful anyway.
The series gets increasingly fishy towards the
With multiplatform kernels, we cannot use hardwired IRQ
numbers in device drivers. This changes the idma driver
to use a proper resource, like all other drivers do.
Signed-off-by: Arnd Bergmann a...@arndb.de
---
arch/arm/plat-samsung/devs.c | 6 ++
sound/soc/samsung/idma.c | 10
With the common clock interface, there is no way to
provide the clock_source sysfs attribute for the
samsung serial ports. Given that this file was
purely informational and had fixed contents, we have
reason to believe that no user space programs
were relying on it.
The sysfs file is not
There are a few bugs in the samsung serial driver when
built as a loadable module, which makes the console
code unavailable, as well as giving no access to
the 'printascii' early debug function. This adds
the appropriate compile time conditionals.
Signed-off-by: Arnd Bergmann a...@arndb.de
---
The spi-s3c64xx uses a Samsung proprietary interface for
talking to the DMA engine, which does not work with
multiplatform kernels. Since the driver can also operate
in PIO mode without any DMA, older platforms that do
not support the DMA engine API will still work, although
slower.
The
In multiplatform configurations, we cannot include headers
provided by only the exynos platform. Fortunately a number
of drivers that include those headers do not actually need
them, so we can just remove the inclusions.
Signed-off-by: Arnd Bergmann a...@arndb.de
---
As a preparation for multiplatform, this changes the exynos
combiner irqchip to no longer make any assumptions about
using specific IRQ numbers or the number of combiners in the
system.
For this, we have to revert to always initializing the combiner
explicitly from architecture code, rather than
In multiplatform configurations, we cannot include headers
provided by only the exynos platform. Fortunately a number
of drivers that include those headers do not actually need
them, so we can just remove the inclusions.
Signed-off-by: Arnd Bergmann a...@arndb.de
---
In order to build the exynos kernel with CONFIG_ARCH_MULTIPLATFORM,
we must convert all users of the Samsung private DMA interface to
the generic dmaengine API. This converts the sound/soc drivers,
breaking the older s3c platforms in the process, since they do not
support the dmaengine interface
The registers for the Samsung S3C serial port are currently defined in
the platform specific arch/arm/plat-samsung/include/plat/regs-serial.h
file, which is not visible to multiplatform capable drivers.
Unfortunately, it is not possible to move the file into a more local
place as we should
In multiplatform configurations, we cannot include headers
provided by only the exynos platform. Fortunately a number
of drivers that include those headers do not actually need
them, so we can just remove the inclusions.
Signed-off-by: Arnd Bergmann a...@arndb.de
---
The plat/iis.h and plat/ac97.h files in the samsung platform are
only needed by the ASoC drivers, so they can be moved into the
same directory, as one more step towards a multiplatform build.
Signed-off-by: Arnd Bergmann a...@arndb.de
---
arch/arm/mach-s3c24xx/dma-s3c2410.c| 2 -
Nothing uses the NAND register definitions other than the
actual driver, so we can move the header file into the
same local directory, which lets us build it in a multiplatform
configuration.
Signed-off-by: Arnd Bergmann a...@arndb.de
---
arch/arm/plat-samsung/include/plat/regs-onenand.h | 63
plat/regs-sdhci.h is not used anywhere but in the sdhci-s3c
driver, so it can become a local file there and all other
inclusions removed.
plat/sdhci.h is used only to define the platform devices,
and with the exception of the platform_data structure not
needed by the driver, so we can split out
With CONFIG_ARCH_MULTIPLATFORM, we can no longer have
our own mach/gpio.h included by the kernel-wide linux/gpio.h
header, and disabling the gpio-samsung driver means we cannot
use any of the private interfaces. This patch disables
all code referring to the driver and gets things to build
again,
The Samsung PWM driver uses magic pointers that are mapped
at boot time to point its MMIO registers. This fails horribly
with a multiplatform kernel, which can not rely on platform
specific header files to contain the right values, aside from
this being a really bad idea in general.
This changes
On 27 December 2012 22:28, Kukjin Kim kgene@samsung.com wrote:
Thomas Abraham wrote:
Hi Linus,
On 14 December 2012 21:21, Linus Walleij linus.wall...@linaro.org wrote:
On Thu, Dec 13, 2012 at 12:54 PM, Thomas Abraham
thomas.abra...@linaro.org wrote:
Add Samsung Exynos5250 SoC
* Arnd Bergmann a...@arndb.de [130305 09:51]:
Hi everyone,
Although I'm not present at the Linaro Connect hacking
sessions, I am participating remotely and have tried
hacking on multiplatform support for Exynos. This patch
set is far from complete, but I think the patches
can be useful
Hi Arnd,
First of all, thanks for your great effort on making Exynos multiplatform-
friendly.
I have added my two cents inline.
On Tuesday 05 of March 2013 18:42:10 Arnd Bergmann wrote:
Hi everyone,
Although I'm not present at the Linaro Connect hacking
sessions, I am participating
Commit 25e9d28d927d2e1731df53f60cde53d75bcb7c36 (ARM: EXYNOS: remove
system mmu initialization from exynos tree) removed the Kconfig symbol
EXYNOS_DEV_SYSMMU. Remove its last traces too.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
0) Untested.
1) Please note that this patch changes the
On Tuesday 05 March 2013, Tomasz Figa wrote:
With this patch set, we can build mach-exynos as part
of a multiplatform kernel, with the following caveats:
* Only DT based boards are supported
As far as I'm aware, there are plans to drop non-DT Exynos support. Kgene
should know more
On Tuesday 05 March 2013, Rob Herring wrote:
Why would you call of_dma_controller_register() for a dma
engine that does not support slave channels, when that is the
only purpose of that interface?
Well maybe then that function should be allowed to fail without erroring
out. I just fixed
On Tuesday 05 March 2013, Heiko Stübner wrote:
If I remember correctly Kgene mentioning some time back, that someone was
working on converting the s3c dma to dmaengine, but I never heard anything
more about it.
Ok, let's see if we can find out what happened to that.
So personally I would
Am Dienstag, 5. März 2013, 18:42:10 schrieb Arnd Bergmann:
Hi everyone,
Although I'm not present at the Linaro Connect hacking
sessions, I am participating remotely and have tried
hacking on multiplatform support for Exynos. This patch
set is far from complete, but I think the patches
can
On Tuesday 05 March 2013, Arnd Bergmann wrote:
The s3c64xx_dma code is also interesting because
it has both an implementation of the s3c_dma interface in
arch/arm/mach-s3c64xx/dma.c and one using the generic interface in
drivers/dma/amba-pl08x.c.
This actually brings me to an interesting
On Tuesday 05 of March 2013 21:54:22 Arnd Bergmann wrote:
On Tuesday 05 March 2013, Arnd Bergmann wrote:
The s3c64xx_dma code is also interesting because
it has both an implementation of the s3c_dma interface in
arch/arm/mach-s3c64xx/dma.c and one using the generic interface in
On Tuesday 05 March 2013, Tomasz Figa wrote:
AFAIR, the PL080 in S3C64xx is a slightly customized variant and requires
some modifications to the driver. However I'm saying this only based on
what I remember from the past, as I haven't checked current version of the
driver yet, so it's
Am Dienstag, 5. März 2013, 22:54:22 schrieb Arnd Bergmann:
On Tuesday 05 March 2013, Arnd Bergmann wrote:
The s3c64xx_dma code is also interesting because
it has both an implementation of the s3c_dma interface in
arch/arm/mach-s3c64xx/dma.c and one using the generic interface in
On Monday 04 March 2013, Padmavathi Venna wrote:
This patch adds #dma-cells property to PL330 DMA controller
nodes for supporting generic dma dt bindings on samsung exynos
platforms. #dma-channels and #dma-requests are not required now
but added in advance.
Signed-off-by: Padmavathi Venna
On Tuesday 05 March 2013, Heiko Stübner wrote:
Am Dienstag, 5. März 2013, 22:54:22 schrieb Arnd Bergmann:
On Tuesday 05 March 2013, Arnd Bergmann wrote:
We still need a solution for the ASoC drivers, but they are
not as essential. We could probably move the wrapper files
from
On Tuesday 05 of March 2013 19:19:02 Arnd Bergmann wrote:
On Tuesday 05 March 2013, Tomasz Figa wrote:
With this patch set, we can build mach-exynos as part
of a multiplatform kernel, with the following caveats:
* Only DT based boards are supported
As far as I'm aware, there are
On Mon, 2013-03-04 at 11:04 +0530, Padmavathi Venna wrote:
This patch adds #dma-cells property to PL330 DMA controller nodes for
supporting generic dma dt bindings on SOCFPGA platform. #dma-channels
and #dma-requests are not required now but added in advance.
Signed-off-by: Padmavathi Venna
Tomasz,
Thanks for your response.
On Sat, Mar 2, 2013 at 3:48 AM, Tomasz Figa tomasz.f...@gmail.com wrote:
The 4 patches above are already merged in Kgene's for-next-next (for 3.10)
branch.
Excellent. I see them now. I haven't yet seen them show up in
linux-next (which is where I tend to
On 6 March 2013 04:59, Doug Anderson diand...@chromium.org wrote:
Tomasz,
Thanks for your response.
On Sat, Mar 2, 2013 at 3:48 AM, Tomasz Figa tomasz.f...@gmail.com wrote:
The 4 patches above are already merged in Kgene's for-next-next (for 3.10)
branch.
Excellent. I see them now. I
Thomas,
On Mon, Mar 4, 2013 at 6:04 AM, Thomas Abraham
thomas.abra...@linaro.org wrote:
Ok. I will repost this patch again with pinctrl_1 and pinctrl_2
included. I had not included this in the earlier patch since I was not
sure of the best pin grouping for the camera and c2c interface.
OK,
Doug Anderson wrote:
Tomasz,
Thanks for your response.
On Sat, Mar 2, 2013 at 3:48 AM, Tomasz Figa tomasz.f...@gmail.com wrote:
The 4 patches above are already merged in Kgene's for-next-next (for
3.10)
branch.
Excellent. I see them now. I haven't yet seen them show up in
On 6 March 2013 05:20, Doug Anderson diand...@chromium.org wrote:
Thomas,
On Mon, Mar 4, 2013 at 6:04 AM, Thomas Abraham
thomas.abra...@linaro.org wrote:
Ok. I will repost this patch again with pinctrl_1 and pinctrl_2
included. I had not included this in the earlier patch since I was not
Thomas,
On Tue, Mar 5, 2013 at 3:49 PM, Thomas Abraham
thomas.abra...@linaro.org wrote:
Yes, I am currently held up with supporting default pin states at slot
level. One option that could be considered is to list out the default
pin states for all slots in the parent node of the slots. So it
Thomas,
On Tue, Mar 5, 2013 at 4:01 PM, Thomas Abraham
thomas.abra...@linaro.org wrote:
So now I have: pinctrl_0 is SPI[46], pinctrl_1 is SPI[45], pinctrl_2
is SPI[50] and pinctrl_3 is SPI[47]. I am yet to test this and
confirm. If you feel these are wrong, could you please let me know.
Yes,
From: Naveen Krishna Ch ch.nav...@samsung.com
Fixes the compilation warnings and potential NULL pointer
dereferencing pointed out by Dan Carpenter.
Signed-off-by: Naveen Krishna Ch ch.nav...@samsung.com
---
drivers/iio/adc/exynos_adc.c | 24 +---
1 file changed, 17
On Wed, Mar 6, 2013 at 4:07 AM, Arnd Bergmann a...@arndb.de wrote:
On Monday 04 March 2013, Padmavathi Venna wrote:
This patch adds #dma-cells property to PL330 DMA controller
nodes for supporting generic dma dt bindings on samsung exynos
platforms. #dma-channels and #dma-requests are not
Hi Viresh,
Again thanks for your review comments.
On Tue, Mar 5, 2013 at 6:48 AM, Viresh Kumar viresh.ku...@linaro.org wrote:
On 2 March 2013 15:04, Amit Daniel Kachhap amit.dan...@samsung.com wrote:
This patch adds dvfs support for exynos5440 SOC. This soc has 4 cores and
they run at same
On 6 March 2013 13:35, amit kachhap amit.kach...@gmail.com wrote:
On Tue, Mar 5, 2013 at 6:48 AM, Viresh Kumar viresh.ku...@linaro.org wrote:
+static void exynos_cpufreq_work(struct work_struct *work)
+{
+ unsigned int cur_pstate, index;
+ struct cpufreq_policy *policy =
62 matches
Mail list logo
