This patch converts the pci_load_of_ranges function to use the new common
of_pci_range_parser.
Signed-off-by: Andrew Murray andrew.mur...@arm.com
Signed-off-by: Liviu Dudau liviu.du...@arm.com
---
arch/mips/pci/pci.c | 50 --
1 files changed, 16
This patchset factors out duplicated code associated with parsing PCI
DT ranges properties across the architectures and introduces a
ranges parser. This parser of_pci_range_parser can be used directly
by ARM host bridge drivers enabling them to obtain ranges from device
trees.
Compared to the v4
This patch factors out common implementation patterns to reduce overall kernel
code and provide a means for host bridge drivers to directly obtain struct
resources from the DT's ranges property without relying on architecture specific
DT handling. This will make it easier to write archiecture
The pci_process_bridge_OF_ranges function, used to parse the ranges
property of a PCI host device, is found in both Microblaze and PowerPC
architectures. These implementations are nearly identical. This patch
moves this common code to a common place.
Signed-off-by: Andrew Murray
Sachin Kamat wrote:
On 10 April 2013 02:01, Arnd Bergmann a...@arndb.de wrote:
On Monday 08 April 2013, Kukjin Kim wrote:
The following changes since commit
07961ac7c0ee8b546658717034fe692fd12eefa9:
Linux 3.9-rc5 (2013-03-31 15:12:43 -0700)
are available in the git repository
Hi Rob,
On Tuesday 09 of April 2013 16:43:48 Rob Herring wrote:
On Mon, Apr 8, 2013 at 1:19 PM, Kukjin Kim kgene@samsung.com
wrote:
The following changes since commit
da821eb7d42935b0f7056d98c75fd1150f6636f4:
Merge commit 'v3.9-rc5' into next/clk-exynos (2013-04-09 01:10:13
On 04/09/2013 04:27 PM, Vivek Gautam wrote:
From: Thomas Abraham thomas.abra...@linaro.org
Convert clk_enable/clk_disable to clk_prepare_enable/clk_disable_unprepare
calls as required by common clock framework.
Signed-off-by: Thomas Abraham thomas.abra...@linaro.org
Signed-off-by: Vivek
Sachin Kamat wrote:
Keypad pins/lines are board specific and should be added to respective
board dts files.
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
---
arch/arm/boot/dts/exynos4x12-pinctrl.dtsi | 56
-
1 files changed, 0 insertions(+), 56
Sachin Kamat wrote:
Added MFC related clock entries in exynos4.dtsi file.
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
Reviewed-by: Sylwester Nawrocki s.nawro...@samsung.com
Applied this series.
Thanks.
- Kukjin
--
To unsubscribe from this list: send the line unsubscribe
Heiko Stübner wrote:
The s3c24xx pins follow a similar pattern as the other Samsung SoCs and
can therefore reuse the already introduced infrastructure.
The s3c24xx SoCs have one design oddity in that the first 4 external
interrupts do not reside in the eint pending register but in the main
Heiko Stübner wrote:
This is the second installment of beginning devicetree support the
Samsung S3C24xx architectures and focuses on the s3c2416 for now.
Included is the devicetree support for the s3c24xx irq controller and
basic support for smdk2416 boards, which can sucessfully boot.
This patch, set up TX FIFO and RX FIFO of HSI2C controller based
on i2c message length.If we configure TX and RX FIFO for a default
value,the ALMOST_EMPTY and ALMOST_FULL will rise the interrupts
unnecessary.
Signed-off-by: Yuvaraj Kumar C D yuvaraj...@samsung.com
---
Vivek Gautam wrote:
Based on 'for-next' of linux-samsung tree with following patches
from Doug on top:
usb: Document clocks in samsung, exynos4210-ehci/ohci bindings
ARM: dts: add usb 2.0 clock references to exynos5250 device tree
Also depending upon following patch-series for
Kukjin Kim wrote:
From: Kukjin Kim kgene@samsung.com
As we discussed in mailing list, non-DT for EXYNOS SoCs will not be
supported from v3.10. This patch removes regarding files for non-DT
including board files.
Signed-off-by: Kukjin Kim kgene@samsung.com
I'd like to send this
Hi Heiko,
Basically looks good to me, but please see my inline comments about
handling of EINT0-3.
On Wednesday 10 of April 2013 01:35:12 Heiko Stübner wrote:
The s3c24xx pins follow a similar pattern as the other Samsung SoCs and
can therefore reuse the already introduced infrastructure.
Am Mittwoch, 10. April 2013, 12:15:48 schrieb Kukjin Kim:
Heiko Stübner wrote:
This is the second installment of beginning devicetree support the
Samsung S3C24xx architectures and focuses on the s3c2416 for now.
Included is the devicetree support for the s3c24xx irq controller and
Vivek Gautam wrote:
This patch-set is in continuation with patch-series:
[PATCH v4 0/4] Enable ehci, ohci and dwc3 devices on exynos5250
out of which follwowing patches have been picked up:
ARM: Exynos5250: Enabling ehci-s5p driver
ARM: Exynos5250: Enabling ohci-exynos driver
Based on
On 04/10/2013 12:34 PM, Kukjin Kim wrote:
Kukjin Kim wrote:
From: Kukjin Kim kgene@samsung.com
As we discussed in mailing list, non-DT for EXYNOS SoCs will not be
supported from v3.10. This patch removes regarding files for non-DT
including board files.
Signed-off-by: Kukjin Kim
This patch series includes some cleanups of the recently added FIMC-IS
driver and prerequisite patches for the FIMC-LITE module to make it
easier to reuse in the future exynos5-is driver.
Sylwester Nawrocki (7):
exynos4-is: Move the subdev group ID definitions to public header
exynos4-is:
Move the sub-device group ID definitions to the driver's public header
so they are available to other media drivers that need to share modules
found in exynos4-is.
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
Get the sensor subdev by walking media graph in both cases: when the
device is used as a subdev only and through video node. This allows
to not dereference the pipeline-subdevs[] array and makes the module
more generic and easier to re-use in other media driver.
Signed-off-by: Sylwester Nawrocki
Make the sensor subdevs host_data hold a pointer to struct fimc_source_info,
which is defined in the driver's public header, rather than a pointer to
struct fimc_sensor_info which is specific to exynos4-is media device driver.
The purpose of this change is to allow easier reuse of the fimc-lite
Instead of incrementing p_region_num field each time we set a bit
in the parameter mask calculate the number of bits set only when
this information is needed.
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
There is no need to check same bit before setting it, since we
always end up with a bit set. Remove some of the tests and make
set unconditional, in every place where all that needs to be done
is just setting a bit.
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Signed-off-by: Kyungmin
On Wed, Apr 10, 2013 at 3:20 PM, Sylwester Nawrocki
s.nawro...@samsung.com wrote:
On 04/09/2013 04:27 PM, Vivek Gautam wrote:
From: Thomas Abraham thomas.abra...@linaro.org
Convert clk_enable/clk_disable to clk_prepare_enable/clk_disable_unprepare
calls as required by common clock framework.
Hi Tomasz,
thanks for your comments, more inline.
Am Mittwoch, 10. April 2013, 12:36:39 schrieb Tomasz Figa:
Hi Heiko,
Basically looks good to me, but please see my inline comments about
handling of EINT0-3.
On Wednesday 10 of April 2013 01:35:12 Heiko Stübner wrote:
The s3c24xx pins
On Wednesday 10 of April 2013 14:20:22 Heiko Stübner wrote:
Hi Tomasz,
thanks for your comments, more inline.
Am Mittwoch, 10. April 2013, 12:36:39 schrieb Tomasz Figa:
Hi Heiko,
Basically looks good to me, but please see my inline comments about
handling of EINT0-3.
On
On 10 April 2013 05:00, Doug Anderson diand...@chromium.org wrote:
Thomas,
On Mon, Apr 8, 2013 at 10:59 PM, Thomas Abraham
thomas.abra...@linaro.org wrote:
@@ -2002,7 +1994,7 @@ static int dw_mci_init_slot(struct dw_mci *host,
unsigned int id)
if (ret) {
On Wednesday 10 April 2013, Sylwester Nawrocki wrote:
On 04/10/2013 12:34 PM, Kukjin Kim wrote:
Kukjin Kim wrote:
From: Kukjin Kim kgene@samsung.com
As we discussed in mailing list, non-DT for EXYNOS SoCs will not be
supported from v3.10. This patch removes regarding files for
Adding Ben H and Michal...
On 04/10/2013 02:29 AM, Andrew Murray wrote:
The pci_process_bridge_OF_ranges function, used to parse the ranges
property of a PCI host device, is found in both Microblaze and PowerPC
architectures. These implementations are nearly identical. This patch
moves this
Am Mittwoch, 10. April 2013, 14:31:29 schrieb Tomasz Figa:
On Wednesday 10 of April 2013 14:20:22 Heiko Stübner wrote:
Hi Tomasz,
thanks for your comments, more inline.
Am Mittwoch, 10. April 2013, 12:36:39 schrieb Tomasz Figa:
Hi Heiko,
Basically looks good to me, but
On 04/10/2013 02:59 PM, Arnd Bergmann wrote:
On Wednesday 10 April 2013, Sylwester Nawrocki wrote:
On 04/10/2013 12:34 PM, Kukjin Kim wrote:
Kukjin Kim wrote:
From: Kukjin Kim kgene@samsung.com
As we discussed in mailing list, non-DT for EXYNOS SoCs will not be
supported from v3.10.
Hi Arnd, Olof,
This is for replacing previous pull-request for
tags/cleanup-samsung-for-v3.10 because it included wrong e-mail address
for author.
Please pull this instead. Sorry for that.
Thanks.
- Kukjin
The following
Hi Arnd, Olof,
Please pull this instead of tags/dt-exynos-for-v3.10 because of wrong
e-mail address for author. Sorry for that.
Thanks.
- Kukjin
The following changes since commit da821eb7d42935b0f7056d98c75fd1150f6636f4:
Hi Arnd, Olof,
Please pull this instead of tags/mct-exynos-for-v3.10 because of wrong
e-mail address for author. Sorry for that.
Thanks.
- Kukjin
The following changes since commit 6dbe51c251a327e012439c4772097a13df43c5b8:
Hi Arnd, Olof,
This is one more pull-request for exynos dt update for v3.10.
Please pull.
Thanks.
- Kukjin
The following changes since commit 31d39248810072dec3279463d5fda0001721c01c:
ARM: dts: add mshc controller node for
On Wednesday 10 April 2013, Sylwester Nawrocki wrote:
Hmm, it turns out we are still actively using some boards based on
Exynos4210 EVT0 SoCs. And since it seems unlikely the patches from
Tomasz [1] adding basic DT support for those will get merged for
3.10, it would be a bit inconvenient to
Thomas,
On Wed, Apr 10, 2013 at 5:48 AM, Thomas Abraham
thomas.abra...@linaro.org wrote:
The call to regulator_enable() is prior to the call to mmc_add_host().
Hence, call to mmc_fre_host is not required in this case. So the above
change should be right.
Are you sure that mmc_free_host() is
On 04/10/13 22:55, Arnd Bergmann wrote:
On Wednesday 10 April 2013, Sylwester Nawrocki wrote:
Hmm, it turns out we are still actively using some boards based on
Exynos4210 EVT0 SoCs. And since it seems unlikely the patches from
Tomasz [1] adding basic DT support for those will get merged for
Thomas,
On Wed, Apr 10, 2013 at 6:56 AM, Doug Anderson diand...@chromium.org wrote:
On Wed, Apr 10, 2013 at 5:48 AM, Thomas Abraham
thomas.abra...@linaro.org wrote:
The call to regulator_enable() is prior to the call to mmc_add_host().
Hence, call to mmc_fre_host is not required in this case.
On 04/10/2013 02:29 AM, Andrew Murray wrote:
This patch factors out common implementation patterns to reduce overall kernel
code and provide a means for host bridge drivers to directly obtain struct
resources from the DT's ranges property without relying on architecture
specific
DT handling.
On 04/10/2013 02:29 AM, Andrew Murray wrote:
This patch converts the pci_load_of_ranges function to use the new common
of_pci_range_parser.
Signed-off-by: Andrew Murray andrew.mur...@arm.com
Signed-off-by: Liviu Dudau liviu.du...@arm.com
Reviewed-by: Rob Herring rob.herr...@calxeda.com
On Wednesday 10 of April 2013 15:45:48 Heiko Stübner wrote:
Am Mittwoch, 10. April 2013, 14:31:29 schrieb Tomasz Figa:
On Wednesday 10 of April 2013 14:20:22 Heiko Stübner wrote:
Hi Tomasz,
thanks for your comments, more inline.
Am Mittwoch, 10. April 2013, 12:36:39 schrieb
Am Mittwoch, 10. April 2013, 21:51:11 schrieb Tomasz Figa:
On Wednesday 10 of April 2013 15:45:48 Heiko Stübner wrote:
Am Mittwoch, 10. April 2013, 14:31:29 schrieb Tomasz Figa:
On Wednesday 10 of April 2013 14:20:22 Heiko Stübner wrote:
Hi Tomasz,
thanks for your comments, more
On Wednesday 10 of April 2013 22:11:03 Heiko Stübner wrote:
Am Mittwoch, 10. April 2013, 21:51:11 schrieb Tomasz Figa:
On Wednesday 10 of April 2013 15:45:48 Heiko Stübner wrote:
Am Mittwoch, 10. April 2013, 14:31:29 schrieb Tomasz Figa:
On Wednesday 10 of April 2013 14:20:22 Heiko
Am Mittwoch, 10. April 2013, 22:17:43 schrieb Tomasz Figa:
On Wednesday 10 of April 2013 22:11:03 Heiko Stübner wrote:
Am Mittwoch, 10. April 2013, 21:51:11 schrieb Tomasz Figa:
On Wednesday 10 of April 2013 15:45:48 Heiko Stübner wrote:
Am Mittwoch, 10. April 2013, 14:31:29 schrieb
Ben, Michal,
On Wed, 10 Apr 2013 08:13:54 -0500, Rob Herring wrote:
Adding Ben H and Michal...
On 04/10/2013 02:29 AM, Andrew Murray wrote:
The pci_process_bridge_OF_ranges function, used to parse the
ranges property of a PCI host device, is found in both Microblaze
and PowerPC
Dear Andrew Murray,
On Wed, 10 Apr 2013 08:29:26 +0100, Andrew Murray wrote:
diff --git a/include/linux/of_pci.h b/include/linux/of_pci.h
index bb115de..6852481 100644
--- a/include/linux/of_pci.h
+++ b/include/linux/of_pci.h
@@ -11,4 +11,7 @@ struct device_node;
struct device_node
On Monday 08 April 2013, Tomasz Figa wrote:
On Saturday 06 of April 2013 00:24:18 Tomasz Figa wrote:
On Friday 05 of April 2013 21:54:21 Arnd Bergmann wrote:
On Friday 05 April 2013, Tomasz Figa wrote:
I'm not sure what you mean by a register-level interface. Something like
The s3c24xx pins follow a similar pattern as the other Samsung SoCs and
can therefore reuse the already introduced infrastructure.
The s3c24xx SoCs have one design oddity in that the first 4 external
interrupts do not reside in the eint pending register but in the main
interrupt controller
On 04/04/2013 12:56 AM, Simon Horman wrote:
On Mon, Apr 01, 2013 at 05:21:12PM -0500, Rob Herring wrote:
From: Rob Herring rob.herr...@calxeda.com
This converts arm and arm64 to use CLKSRC_OF DT based initialization for
the arch timer. A new function arch_timer_arch_init is added to allow for
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
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
Cc: alsa-de...@alsa-project.org
Cc: Mark Brown broo...@opensource.wolfsonmicro.com
Cc:
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
The platform code knows the IRQ base, while the irqchip driver
should really not. This is a littly hacky because we still
hardwire the IRQ base to 160 for the combiner in the DT case,
when we should really use -1. Removing that line will cause
a linear IRQ domain to be use, as we should.
Hi everyone,
I have updated my series for multiplatform support of the ARM exynos
platform, based on what is currently queued up in arm-soc.
It would be really nice to still get this merged for 3.10. A lot of
the patches are really trivial, but there are some complex ones
as well.
To all
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
Cc: linux-fb...@vger.kernel.org
The number of combiners on a given SoC is a platform specific
constant, and we cannot encode this number on a multiplatform
kernel since the header file defining it is not available.
Allocating the structure dynamically ends up cleaner anyway
since we keep all the data local.
Signed-off-by: Arnd
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
Cc: rtc-li...@googlegroups.com
Cc: Alessandro Zummo a.zu...@towertech.it
The second argument to the module_device_table macro must be the
name of the device id array. In the samsung i2s driver, there
was a small typo, resulting in a build error when building it
as a loadable module.
Signed-off-by: Arnd Bergmann a...@arndb.de
Cc: alsa-de...@alsa-project.org
Cc: Mark
The spi-s3c64xx uses a Samsung proprietary interface for
talking to the DMA engine, which does not work with
multiplatform kernels.
This version of the patch leaves the old code in place,
behind an #ifdef. This can be removed in the future,
after the s3c64xx platform start supporting the regular
The idma_reg_addr_init function is used by the samsung i2s driver,
which can be a loadable module, so we have to export this function.
Signed-off-by: Arnd Bergmann a...@arndb.de
Cc: alsa-de...@alsa-project.org
Cc: Mark Brown broo...@opensource.wolfsonmicro.com
Cc: Liam Girdwood
[ CC Magnus Damm ]
On Wed, Apr 10, 2013 at 06:17:31PM -0500, Rob Herring wrote:
On 04/04/2013 12:56 AM, Simon Horman wrote:
On Mon, Apr 01, 2013 at 05:21:12PM -0500, Rob Herring wrote:
From: Rob Herring rob.herr...@calxeda.com
This converts arm and arm64 to use CLKSRC_OF DT based
We can find out the number of combined IRQs from the device
tree, but in case of ATAGS boot, the driver currently uses
hardcoded values based on the SoC type. We can't do that
in general for a multiplatform kernel, so let's instead pass
this information from platform code directly in case of
ATAGS
The IRQ_SPI() macro is not available in the driver when building with sparse
IRQs or multiplatform, so let's move all users of this into one function
that we can leave out when building DT-only.
Signed-off-by: Arnd Bergmann a...@arnd.de
Cc: Thomas Gleixner t...@linutronix.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 version of the patch adds the
generic dmaengine API as an alternative to the existing samsung
specific one. Once all the older
This makes it possible to enable the exynos platform as part of a
multiplatform kernel, in addition to keeping the single-platform
exynos support.
The multiplatform variant has a number of limitations at the moment:
* It only supports DT-enabled machines. This is not a problem in
the long run,
The new common clock drivers for exynos are using compile
time constants and soc_is_exynos* macros to provide backwards
compatibility for pre-DT systems, which is not possible with
multiplatform kernels. This moves all the necessary
information back into platform code and removes the mach/*
header
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
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
---
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
Cc: linux...@vger.kernel.org
Cc:
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
Cc: linux-...@vger.kernel.org
Cc: Wolfram
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
For the non-DT case, the mct_init() function requires access
to a couple of platform specific constants, but cannot include
the header files in case we are building for multiplatform.
This changes the interface to the platform so we pass all
the necessary data as arguments to mct_init.
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
Em Thu, 11 Apr 2013 02:04:53 +0200
Arnd Bergmann a...@arndb.de escreveu:
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.
The s3c-fb driver requires header files from the samsung platforms
to find its platform_data definition, but this no longer works on
multiplatform kernels, so let's move the data into a new header
file under include/linux/platform_data.
Signed-off-by: Arnd Bergmann a...@arndb.de
Cc:
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
Cc: linux-...@lists.infradead.org
Cc: Kyungmin Park
For a DT-only build we don't want to compile devs.c, but we do need
the mfc device, which is also referenced by the DT based platforms,
so move it all into one place.
Signed-off-by: Arnd Bergmann a...@arndb.de
---
arch/arm/plat-samsung/devs.c| 45 -
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
Cc:
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
Cc: alsa-de...@alsa-project.org
Cc: Mark Brown
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
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
On Thu, Apr 11, 2013 at 9:04 AM, Arnd Bergmann a...@arndb.de wrote:
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
Thanks Arnd.
On Thu, Apr 11, 2013 at 9:04 AM, Arnd Bergmann a...@arndb.de wrote:
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:
Hi,
On Wed, Apr 10 2013, Arnd Bergmann wrote:
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
Rui, Arnd,
As agreed in [1], I will be helping on the thermal maintenance.
On 10-04-2013 20:04, Arnd Bergmann wrote:
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
On Wednesday, April 10, 2013, Doug Anderson wrote:
Thomas,
On Wed, Apr 10, 2013 at 6:56 AM, Doug Anderson diand...@chromium.org wrote:
On Wed, Apr 10, 2013 at 5:48 AM, Thomas Abraham
thomas.abra...@linaro.org wrote:
The call to regulator_enable() is prior to the call to mmc_add_host().
On Wednesday, April 10, 2013 6:50 PM, Sylwester Nawrocki wrote:
On 04/09/2013 04:27 PM, Vivek Gautam wrote:
From: Thomas Abraham thomas.abra...@linaro.org
Convert clk_enable/clk_disable to clk_prepare_enable/clk_disable_unprepare
calls as required by common clock framework.
On Thursday, April 11, 2013 9:05 AM, Arnd Bergmann wrote:
The s3c-fb driver requires header files from the samsung platforms
to find its platform_data definition, but this no longer works on
multiplatform kernels, so let's move the data into a new header
file under
On Thursday, April 11, 2013 9:05 AM, Arnd Bergmann wrote:
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.
On Thursday, April 11, 2013 9:05 AM, Arnd Bergmann wrote:
The s3c-fb driver requires header files from the samsung platforms
to find its platform_data definition, but this no longer works on
multiplatform kernels, so let's move the data into a new header
file under
92 matches
Mail list logo
