On Wed, Mar 20, 2019 at 06:49:25PM +0000, Suzuki K Poulose wrote:
In preparation to use a consistent device naming scheme,
clean up the device link tracking in replicator driver.
Use the "coresight" device instead of the "real" parent device
for all internal purposes. All other requests (e.g, power management,
DMA operations) must use the "real" device which is the parent device.
Since the CATU driver also uses the TMC-SG infrastructure, update
the callers to ensure they pass the appropriate device argument
for the tables.
Cc: Mathieu Poirier <mathie.poirier@xxxxxxxxxx>
Any reason for not getting rid of tmc_drvdata::dev like you did for the funnel,
replicator and catu?