On Fri, Oct 11, 2013 at 02:00:35AM +0100, Simon Horman wrote:
> [ CCed devicetree@xxxxxxxxxxxxxxx as this involves DT compatibility strings ]
Cheers!
>
> On Thu, Oct 10, 2013 at 11:08:03PM +0400, Valentine Barshak wrote:
> > RCAR Gen2 SoC has a different phy which is not compatible with
> > the older H1/M1 versions. This adds OF/platform device table
> > and PHY initialization callbacks for H2/M2 (Gen2) SoC.
Is the PHY combined with the rest of the controller, or are they
logically separate components in the SoC? I note that the Calxeda
Highbank SATA controller driver treats the phy and the controller as
separate entities, and describes the way the two are attached (though
the driver handles both). Would a similar approach work here?
[...]
> > +static struct of_device_id sata_rcar_match[] = {
> > + {
> > + .compatible = "renesas,rcar-sata",
> > + .data = (void *)RCAR_SATA
> > + },
> > + {
> > + .compatible = "renesas,sata-r8a7790",
> > + .data = (void *)RCAR_GEN2_SATA
> > + },
> > + {
> > + .compatible = "renesas,sata-r8a7791",
> > + .data = (void *)RCAR_GEN2_SATA
> > + },
> > + {},
These bindings will need documentation. A grep of any of these in
mainline's Documentation/devicetree shows up nothing (not even the
existing "renesas,rcar-sata" string used by the driver.
Thanks,
Mark.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
