On Wed, Aug 29, 2012 at 08:48:15AM -0600, Daniel Drake wrote:
> Hi,
>
> At OLPC we are working hard to migrate from board files to the device
> tree for our existing ARM laptop XO-1.75, and we are also working
> directly with the DT (no board file) from day 1 with development of
> our upcoming XO-
On 08/29/2012 01:01 PM, Sascha Hauer wrote:
> On Wed, Aug 29, 2012 at 01:18:10PM +0300, Alexander Shishkin wrote:
>> Sascha Hauer writes:
>>
>>> On Wed, Aug 29, 2012 at 10:50:08AM +0300, Alexander Shishkin wrote:
Richard Zhao writes:
> i.MX usb controllers shares non-core registers,
Hi,
At OLPC we are working hard to migrate from board files to the device
tree for our existing ARM laptop XO-1.75, and we are also working
directly with the DT (no board file) from day 1 with development of
our upcoming XO-4 ARM laptop.
While the coding aspect is going fine, we have some open qu
To be able to load the McPDM and DMIC driver when booted with device tree.
Signed-off-by: Peter Ujfalusi
---
arch/arm/boot/dts/omap5.dtsi | 20
1 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index
In order to get the memory areas by name when booted with DT.
Signed-off-by: Peter Ujfalusi
---
arch/arm/boot/dts/omap4.dtsi |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 258435f..115a502 100644
--- a/a
Add the needed sections to enable audio support on BeagleBoard when booted
with DT blob.
Signed-off-by: Peter Ujfalusi
---
arch/arm/boot/dts/omap3-beagle.dts | 14 ++
1 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-beagle.dts
b/arch/arm/boot
Since the board is based on OMAP2420 we should include the dedicated dtsi
file (which includes the common omap2 dtsi).
Signed-off-by: Peter Ujfalusi
---
arch/arm/boot/dts/omap2420-h4.dts |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/boot/dts/omap2420-h4.dts
Create the sections describing the McBSP ports to be able to use them via
DT.
Signed-off-by: Peter Ujfalusi
---
arch/arm/boot/dts/omap5.dtsi | 36
1 files changed, 36 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/d
The McBSP IP within OMAP2420 and 2430 is different we need to create separate
dtsi files for them.
Signed-off-by: Peter Ujfalusi
---
arch/arm/boot/dts/omap2420.dtsi | 39 ++
arch/arm/boot/dts/omap2430.dtsi | 83 +++
2 files changed, 122 ins
Create the sections describing the McBSP ports to be able to use them via
DT.
Signed-off-by: Peter Ujfalusi
---
arch/arm/boot/dts/omap4.dtsi | 47 ++
1 files changed, 47 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/
Create the needed sections to be able to probe McBSP ports via DT.
Signed-off-by: Peter Ujfalusi
---
arch/arm/boot/dts/omap3.dtsi | 69 ++
1 files changed, 69 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/om
Hello,
I have extended and rebased the previous set:
'ARM/dts: omap McBSP and audio support for BeagleBoard'
Changes since v1:
- Rebased on current l-o:devel-dt branch
- Two new patch, one for OMAP4 to add reg-names for the mem areas, one for OMAP5
to add McPDM and DMIC section
The rest of the
From: Dong Aisheng
Originally the anatop regulator devices are populated by mfd anatop driver.
Since mfd anatop driver will be deleted later, we change to populate the
regulator devices by devicetree automatically.
This will cause some warning messages as follows during boot due to device
recreat
From: Dong Aisheng
The anatop registers are accessed via syscon now, no one will use
mfd anatop driver anymore, remove it.
Acked-by: Stephen Warren
Signed-off-by: Dong Aisheng
---
drivers/mfd/Kconfig|8 ---
drivers/mfd/Makefile |1 -
drivers/mfd/anatop-mfd.c | 124 ---
From: Dong Aisheng
Using syscon to access anatop registers.
Acked-by: Stephen Warren
Signed-off-by: Dong Aisheng
---
ChangeLog v2->v3:
* remove a few unneed codes
ChangeLog v1->v2:
* update to use generic regmap api
---
arch/arm/mach-imx/Kconfig |2 +-
arch/arm/mach-imx/mach-imx6q.
From: Dong Aisheng
Using syscon to access anatop register.
Acked-by: Mark Brown
Acked-by: Stephen Warren
Signed-off-by: Dong Aisheng
---
ChangeLog v2->v3:
* update to use syscon_node_to_regmap and use of_get_parent to get anatop node.
ChangeLog v1-v2:
* update to use generic regmap api
---
From: Dong Aisheng
There're a few anatop registers need to be accessed by different modules.
Add anatop registers into syscon support for easy access.
Acked-by: Stephen Warren
Signed-off-by: Dong Aisheng
---
arch/arm/boot/dts/imx6q.dtsi |4 ++--
1 files changed, 2 insertions(+), 2 deletio
From: Dong Aisheng
Add regmap based syscon driver.
This is usually used for access misc bits in registers which does not belong
to a specific module, for example, IMX IOMUXC GPR and ANATOP.
With this driver, client can use generic regmap API to access registers
which are registered into syscon.
From: Dong Aisheng
Include headfile for easy using.
Acked-by: Stephen Warren
Signed-off-by: Dong Aisheng
---
arch/arm/boot/dts/imx6q.dtsi |5 +
include/linux/fsl/imx6q-iomuxc-gpr.h | 319 ++
2 files changed, 324 insertions(+), 0 deletions(-)
diff
This patch series mainly adds an syscon driver which is used to access
general system controller registers like FSL IOMUXC GPR and ANATOP,
after that, we convert all the exist private access general registers code to
use
standard API from regmap to access registers.
Finally we remove the old mfd a
On Wed, Aug 29, 2012 at 01:18:10PM +0300, Alexander Shishkin wrote:
> Sascha Hauer writes:
>
> > On Wed, Aug 29, 2012 at 10:50:08AM +0300, Alexander Shishkin wrote:
> >> Richard Zhao writes:
> >>
> >> > i.MX usb controllers shares non-core registers, which may include
> >> > SoC specific contro
On Wed, Aug 29, 2012 at 01:18:10PM +0300, Alexander Shishkin wrote:
> Sascha Hauer writes:
>
> > On Wed, Aug 29, 2012 at 10:50:08AM +0300, Alexander Shishkin wrote:
> >> Richard Zhao writes:
> >>
> >> > i.MX usb controllers shares non-core registers, which may include
> >> > SoC specific contro
Add device nodes for the four instances of dw_mmc controllers in Exynos5250
and enable instance 0 and 2 for the smdk5250 board.
Signed-off-by: Thomas Abraham
---
arch/arm/boot/dts/exynos5250-smdk5250.dts | 55 +
arch/arm/boot/dts/exynos5250.dtsi | 32 +
Add entries if MSHC controllers in AUXDATA table for correct device name
initialization.
Signed-off-by: Abhilash Kesavan
Signed-off-by: Thomas Abraham
---
arch/arm/mach-exynos/include/mach/map.h |4
arch/arm/mach-exynos/mach-exynos5-dt.c |8
2 files changed, 12 insertions
Add clock instances for bus interface unit clock and card interface unit
clock of the all four MSHC controller instances.
Signed-off-by: Abhilash Kesavan
Signed-off-by: Thomas Abraham
---
arch/arm/mach-exynos/clock-exynos5.c | 45 --
1 files changed, 16 inserti
This patch series adds Exynos5250 platform support for MSHC controllers.
Thomas Abraham (3):
ARM: Samsung: Add support for MSHC controller clocks
ARM: Exynos5: Add AUXDATA support for MSHC controllers
ARM: dts: Add nodes for dw_mmc controllers for Samsung Exynos5250 platforms
arch/arm/boot
Samsung Exynos SoC's extend the dw-mshc controller for additional clock and bus
control. Add support for these extensions and include provide device tree based
discovery suppory as well.
Signed-off-by: Thomas Abraham
Acked-by: Will Newton
---
.../devicetree/bindings/mmc/exynos-dw-mshc.txt |
The core dw-mshc controller driver can let platform specific implementations
of the dw-mshc controller to control the hardware as required by such
implementations. This is acheived by invoking implementation specific (optional)
callbacks. Define the list of callbacks supported the add invocation po
Platform implementations of dw-mshc controller may choose to exterd the features
of the standard dw-mshc controller such as adding additional clocking options or
modifying the bus interface. Support for such implementation specific extensions
can be incorporated into dw_mmc-pltfm, but including mul
Add device tree based discovery support.
Signed-off-by: Thomas Abraham
Acked-by: Will Newton
---
.../devicetree/bindings/mmc/synposis-dw-mshc.txt | 79
drivers/mmc/host/dw_mmc-pltfm.c|9 ++
drivers/mmc/host/dw_mmc.c | 130 ++
If the write protect pad of the controller is not connected to the write
protect pin of the slot, the driver should be notified of this condition
so that incorrect check for write protection by reading the WRTORT
register can avoided. The get_ro platform callback can be used for in
such cases, but
Some platforms allow for clock gating and control of bus interface unit clock
and card interface unit clock. Add support for clock lookup of optional biu
and ciu clocks for clock gating and clock speed determination.
Signed-off-by: Abhilash Kesavan
Signed-off-by: Thomas Abraham
Acked-by: Will Ne
Instead of aborting the probe in case a slot initialization fails, allow
initialization of as many slots as possible. If there are atleast one
instance of slot that is successfully initialized, allow the driver probe
to succeed.
Signed-off-by: Thomas Abraham
Acked-by: Will Newton
---
drivers/mm
Use devm_* managed functions for simpler error handling.
Signed-off-by: Thomas Abraham
Acked-by: Will Newton
---
drivers/mmc/host/dw_mmc-pltfm.c | 29 -
1 files changed, 8 insertions(+), 21 deletions(-)
diff --git a/drivers/mmc/host/dw_mmc-pltfm.c b/drivers/mmc/ho
The 'struct dw_mci' maintains a copy of the pdev->dev instance instead of
maintaining a reference to that 'struct device' instance. Any resource
allocated using the device resource management kernel API with the instance
of 'struct device' in 'struct dw_mci' is then incorrect. Fix this by
convertin
This is the fifth version of the patch series that adds device tree support
for Synopsis Designware Mobile Storage Host Controller. All the review comments
from the v4 version have been addressed and rebased on mmc-next branch. Since
v4,
patches 6/9 and 9/9 have been modified. This has been tested
With the new devices (like, AM33XX and OMAP5) we now only support
DT boot mode of operation and now it is the time to start killing
slowly the dependency on hwmod, so with this patch, we are starting
with device resources.
The idea here is implemented considering to both boot modes -
- DT boot mo
On Wed, Aug 29, 2012 at 10:50:08AM +0300, Alexander Shishkin wrote:
> Richard Zhao writes:
>
> > i.MX usb controllers shares non-core registers, which may include
> > SoC specific controls. We take it as a usbmisc device and usbmisc
> > driver set operations needed by ci13xxx_imx driver.
> >
> >
On Wed, Aug 29, 2012 at 10:50:08AM +0300, Alexander Shishkin wrote:
> Richard Zhao writes:
>
> > i.MX usb controllers shares non-core registers, which may include
> > SoC specific controls. We take it as a usbmisc device and usbmisc
> > driver set operations needed by ci13xxx_imx driver.
> >
> >
Am Mittwoch, 29. August 2012, 01:09:37 schrieb Kukjin Kim:
> On 08/28/12 14:55, Heiko Stübner wrote:
> > Until now the Exynos-SoC was the only Samsung-SoC supporting the GPIOs
> > via the device tree. This patch implements dt-support for the
> > s3c24xx arches.
> >
> > The controllers contain only
40 matches
Mail list logo
