* Rajendra Nayak [14 19:40]:
> On Tuesday 15 November 2011 03:00 AM, Tony Lindgren wrote:
> >* Rajendra Nayak [04 04:16]:
> >>@@ -1869,6 +1957,14 @@ static int __init omap_hsmmc_probe(struct
> >>platform_device *pdev)
> >>struct omap_hsmmc_host *host = NULL;
> >>struct resource *
On Tuesday 15 November 2011 03:00 AM, Tony Lindgren wrote:
* Rajendra Nayak [04 04:16]:
@@ -1869,6 +1957,14 @@ static int __init omap_hsmmc_probe(struct
platform_device *pdev)
struct omap_hsmmc_host *host = NULL;
struct resource *res;
int ret, irq;
+ const str
* Rajendra Nayak [04 04:16]:
> @@ -1869,6 +1957,14 @@ static int __init omap_hsmmc_probe(struct
> platform_device *pdev)
> struct omap_hsmmc_host *host = NULL;
> struct resource *res;
> int ret, irq;
> + const struct of_device_id *match;
> +
> + match = of_match_devi
On Saturday 05 November 2011 01:34 AM, Olof Johansson wrote:
On Fri, Nov 04, 2011 at 05:20:39PM +0530, Rajendra Nayak wrote:
Define dt bindings for the ti-omap-hsmmc, and adapt
the driver to extract data (which was earlier passed as
platform_data) from device tree node.
Signed-off-by: Rajendra
On Saturday 05 November 2011 02:55 AM, Cousson, Benoit wrote:
+Required properties:
+- compatible: Should be "ti,omap-hsmmc", "ti,omap2-hsmmc";
+n is controller instance starting 0, for OMAP2/3 controllers
No, no, no. You should not have to specify the unit-address in the
compatible
field. They
+ti,hsmmc-non-removable: non-removable slot (like eMMC)
Same here, non-removable should be standardized.
CHRP has a "built-in" property for this. That was standardised in 1998,
you could reuse it :-)
Segher
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body
On Fri, Nov 4, 2011 at 2:25 PM, Cousson, Benoit wrote:
> Hi Olof,
>
> On 11/4/2011 9:04 PM, Olof Johansson wrote:
>>
>> On Fri, Nov 04, 2011 at 05:20:39PM +0530, Rajendra Nayak wrote:
>>>
>>> Define dt bindings for the ti-omap-hsmmc, and adapt
>>> the driver to extract data (which was earlier pass
Hi Olof,
On 11/4/2011 9:04 PM, Olof Johansson wrote:
On Fri, Nov 04, 2011 at 05:20:39PM +0530, Rajendra Nayak wrote:
Define dt bindings for the ti-omap-hsmmc, and adapt
the driver to extract data (which was earlier passed as
platform_data) from device tree node.
Signed-off-by: Rajendra Nayak
-
On Fri, Nov 04, 2011 at 05:20:39PM +0530, Rajendra Nayak wrote:
> Define dt bindings for the ti-omap-hsmmc, and adapt
> the driver to extract data (which was earlier passed as
> platform_data) from device tree node.
>
> Signed-off-by: Rajendra Nayak
> ---
> .../devicetree/bindings/mmc/ti-omap-hs
Define dt bindings for the ti-omap-hsmmc, and adapt
the driver to extract data (which was earlier passed as
platform_data) from device tree node.
Signed-off-by: Rajendra Nayak
---
.../devicetree/bindings/mmc/ti-omap-hsmmc.txt | 50 +
drivers/mmc/host/omap_hsmmc.c
10 matches
Mail list logo
