nvpublic
> On 08/24/2012 06:36 PM, Bill Huang wrote:
> >>> On Sun, Aug 19, 2012 at 06:07:55PM -0700, Bill Huang wrote:
> Add DT property "ti,system-power-controller" telling whether or not
> this pmic is in charge of controlling the system power, so the
> power off routine can be hoo
Hi,
On Sat, Aug 25, 2012 at 11:43 PM, Marc Kleine-Budde wrote:
> On 08/24/2012 08:46 AM, Richard Zhao wrote:
>> Did you try both enableing and disabing DT pass build?
>
> Impossible on mx28 :) The platform always selects USE_DT, but on imx it
> builds without DT support.
>
>> On Thu, Aug 23, 2012
On 08/25/2012 08:53 AM, Sebastian Hesselbarth wrote:
> On 08/24/2012 05:34 AM, Stephen Warren wrote:
>> On 08/23/2012 05:01 PM, Sebastian Hesselbarth wrote:
>>> So possible, valid combinations for uart1 would be:
>>> (a) mpp_uart1;
>>> (b) mpp_uart1, mpp2, mpp3;
>>> (c) mpp_uart1, mpp21, mpp22;
>>>
Hi Heiko,
On 26 August 2012 03:23, 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 3 cells, as the underlying gpio controller
> does not
On 16:26 Sat 25 Aug , Stephen Warren wrote:
>
>
> Jean-Christophe PLAGNIOL-VILLARD wrote:
>
> >On 22:11 Tue 21 Aug , Stephen Warren wrote:
> >> From: Stephen Warren
> >>
> >> I figured the easiest way to get named constants into dtc would be to
> >> re-use an existing C pre-processor
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
---
.../devicetree/bindings/mmc/exynos-dw-mshc.txt | 79 +++
drivers/
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 extend 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
---
.../devicetree/bindings/mmc/synposis-dw-mshc.txt | 90 ++
drivers/mmc/host/dw_mmc-pltfm.c|9 ++
drivers/mmc/host/dw_mmc.c | 130 ++-
3 file
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
---
drivers/mmc/
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
---
drivers/mmc/host/dw_mmc.c | 23
Use devm_* managed functions for simpler error handling.
Signed-off-by: Thomas Abraham
---
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/host/dw_mmc-pltfm.c
index
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 fourth version of the patch series that adds device tree support
for Synopsis Designware Mobile Storage Host Controller. In this version, the
significant change is the spliting of Exynos specific code into a seperate
file, as suggested by Seungwon Jeon . Spliting the
Exynos specific cod
Dear Kevin Cernekee,
> On Sat, Aug 25, 2012 at 1:40 PM, Marek Vasut wrote:
> >> Are there any modern SPI flash parts that can't handle FAST_READ, or
> >> is this mostly for compatibility with legacy systems?
> >
> > We have to support all possibilities, not only "modern systems" .
>
> If the !F
Trivial patch that exports the of_irq_to_resource_table() symbol so that
modules can use it.
Signed-off-by: John Crispin
---
drivers/of/irq.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/of/irq.c b/drivers/of/irq.c
index ff8ab7b..a23ec77 100644
--- a/drivers/o
17 matches
Mail list logo
