linux-kernel - RE: Bug: shared usb dt document is incorrect

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BN3PR0301MB084977B6D73E96960E4AC1D0818C0@BN3PR0301MB0849.namprd03.prod.outlook.com>
Date:	Wed, 29 Jul 2015 03:12:24 +0000
From:	Peter Chen <Peter.Chen@...escale.com>
To:	Rob Herring <robherring2@...il.com>,
	Tim Bird <tim.bird@...ymobile.com>
CC:	Antoine Ténart 
	<antoine.tenart@...e-electrons.com>,
	"linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Linux USB List <linux-usb@...r.kernel.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Bjorn Andersson <Bjorn.Andersson@...ymobile.com>
Subject: RE: Bug: shared usb dt document is incorrect

 
> > I was just doing some testing with USB on a Qualcomm SoC.
> >
> > I followed the instructions in the binding document:
> > Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt
> >
> > which has a compatible for "qcom,ci-hdrc", and is, in general, for
> > chipidea-based USB controllers.
> >
> > It says in the document that the property usb-phy is deprecated, and
> > to use phys and phy-names instead.  However, the Qualcomm driver for
> > this still uses usb-phy.  That driver is in:
> > drivers/usb/chipidea/ci_hdrc_msm.c
> 
> Deprecated means it still exists in the wild and should be maintained, but don't
> use it for new dts files.
> 

But how the new SoC (for new dts) which still uses current USB PHY driver?

Maybe we should not add additional description for this property,
it depends on which PHY driver (Generic PHY vs USB PHY)  this controller
will use, if it uses a new PHY driver, it must use generic PHY framework,  and will
use 'phy' and 'phy-names' corresponding.

Peter