Hi Sergei,
On Fri, Jul 31, 2015 at 6:50 PM, Sergei Shtylyov
wrote:
> Hello.
>
>
> On 7/31/2015 5:23 AM, Magnus Damm wrote:
>
>>> The "compatible" property text contradicts even the example given in the
>>> MMCIF
>>> binding document itself; moreover, the Renesas MMCIF driver only matches
>>> on
On Friday 31 July 2015 11:23:04 Magnus Damm wrote:
> On Fri, Jul 31, 2015 at 4:59 AM, Sergei Shtylyov wrote:
> > The "compatible" property text contradicts even the example given in the
> > MMCIF binding document itself; moreover, the Renesas MMCIF driver only
> > matches on the generic "compatib
Hi Sergei,
On Fri, Jul 31, 2015 at 4:59 AM, Sergei Shtylyov
wrote:
> The "compatible" property text contradicts even the example given in the MMCIF
> binding document itself; moreover, the Renesas MMCIF driver only matches on
> the generic "compatible" string, and doesn't look for at SoC specif
Hello.
On 07/30/2015 10:59 PM, Sergei Shtylyov wrote:
The "compatible" property text contradicts even the example given in the MMCIF
binding document itself; moreover, the Renesas MMCIF driver only matches on
the generic "compatible" string, and doesn't look for at SoC specific strings
"
The "compatible" property text contradicts even the example given in the MMCIF
binding document itself; moreover, the Renesas MMCIF driver only matches on
the generic "compatible" string, and doesn't look for at SoC specific strings
currently at all. Thus describe "renesas,sh-mmcif" string as man
