X-Git-Url: https://git.sur5r.net/?a=blobdiff_plain;f=doc%2Fdriver-model%2Fusb-info.txt;h=e07e5ba26106f5d9984ea8d07b61adc3223c9a6d;hb=7b4f17bf3653ffff0d5d7b76bb8c2d8c293db4ce;hp=66f2daec7c80b79a6bb7c8fa51b07e6e60a70b0a;hpb=e536ab8849b2b4f6d68bbc8e1d1f9bc033db06bd;p=u-boot

diff --git a/doc/driver-model/usb-info.txt b/doc/driver-model/usb-info.txt
index 66f2daec7c..e07e5ba261 100644
--- a/doc/driver-model/usb-info.txt
+++ b/doc/driver-model/usb-info.txt
@@ -84,7 +84,7 @@ The following primary data structures are in use:
 	This holds information about a device on the bus. All devices have
 	this structure, even the root hub. The controller itself does not
 	have this structure. You can access it for a device 'dev' with
-	dev_get_parentdata(dev). It matches the old structure except that the
+	dev_get_parent_priv(dev). It matches the old structure except that the
 	parent and child information is not present (since driver model
 	handles that). Once the device is set up, you can find the device
 	descriptor and current configuration descriptor in this structure.
@@ -279,7 +279,7 @@ USB hubs are scanned as in the section above. While hubs have their own
 uclass, they share some common elements with controllers:
 
 - they both attach private data to their children (struct usb_device,
-accessible for a child with dev_get_parentdata(child))
+accessible for a child with dev_get_parent_priv(child))
 - they both use usb_child_pre_probe() to set up their children as proper USB
 devices