18c2ecf20Sopenharmony_ciWhat:		/sys/bus/fsl-mc/drivers/.../bind
28c2ecf20Sopenharmony_ciDate:		December 2016
38c2ecf20Sopenharmony_ciContact:	stuart.yoder@nxp.com
48c2ecf20Sopenharmony_ciDescription:
58c2ecf20Sopenharmony_ci		Writing a device location to this file will cause
68c2ecf20Sopenharmony_ci		the driver to attempt to bind to the device found at
78c2ecf20Sopenharmony_ci		this location. The format for the location is Object.Id
88c2ecf20Sopenharmony_ci		and is the same as found in /sys/bus/fsl-mc/devices/.
98c2ecf20Sopenharmony_ci
108c2ecf20Sopenharmony_ci                For example::
118c2ecf20Sopenharmony_ci
128c2ecf20Sopenharmony_ci		  # echo dpni.2 > /sys/bus/fsl-mc/drivers/fsl_dpaa2_eth/bind
138c2ecf20Sopenharmony_ci
148c2ecf20Sopenharmony_ciWhat:		/sys/bus/fsl-mc/drivers/.../unbind
158c2ecf20Sopenharmony_ciDate:		December 2016
168c2ecf20Sopenharmony_ciContact:	stuart.yoder@nxp.com
178c2ecf20Sopenharmony_ciDescription:
188c2ecf20Sopenharmony_ci		Writing a device location to this file will cause the
198c2ecf20Sopenharmony_ci		driver to attempt to unbind from the device found at
208c2ecf20Sopenharmony_ci		this location. The format for the location is Object.Id
218c2ecf20Sopenharmony_ci		and is the same as found in /sys/bus/fsl-mc/devices/.
228c2ecf20Sopenharmony_ci
238c2ecf20Sopenharmony_ci                For example::
248c2ecf20Sopenharmony_ci
258c2ecf20Sopenharmony_ci		  # echo dpni.2 > /sys/bus/fsl-mc/drivers/fsl_dpaa2_eth/unbind
26