[lkml]   [2019]   [Mar]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 08/25] coresight: tmc: Clean up device specific data
On 03/26/2019 09:53 PM, Mathieu Poirier wrote:
> Hi Suzuki,
> 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 <>

> Any reason for not getting rid of tmc_drvdata::dev like you did for the funnel,
> replicator and catu?

Nothing special, may be we use the dev more for various DMA operations.
But you're right, we can remove it.


 \ /
  Last update: 2019-03-27 15:41    [W:0.062 / U:4.580 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site