Hi,
On Friday 12 December 2014 12:11 AM, Doug Anderson wrote:
> Kishon,
>
> On Thu, Dec 11, 2014 at 2:27 AM, Kishon Vijay Abraham I <kishon@xxxxxx> wrote:
>> I didn't mean that. You can get rid of this entire xlate stuff if you use
>> something like below
>>
>> phy@xxx {
>> compatible = "";
>> phy1:usb_phy {
>> }
>> phy2:usb_phy {
>> };
>> };
>>
>>
>> usb@xx {
>> compatible = "";
>> phys = <&phy1>; //doesn't need xlate
>> /* this needs xlate
>> phys = <&phy 1>;
>> */
>> phy-names = "phy";
>> };
>
> Is the syntax you proposed really better? Are you saying that you
> advocate never using "#phy-cells" other than 0 for new bindings? Is
No. It can still be used for configuring the PHY. For example, in the case of
PIPE3 PHY we configure it to USB PHY, SATA PHY or PCIE PHY depending on to
which controller the PHY is connected to.
I feel using phy-cells just for differentiating the PHY is pointless when you
have a separate node for each PHY.
Thanks
Kishon
--
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
