From: Marek Vasut
Date: Sun, 13 Oct 2019 12:50:15 +0200
> On 10/13/19 2:21 AM, David Miller wrote:
>> From: David Miller
>> Date: Sat, 12 Oct 2019 17:20:55 -0700 (PDT)
>>
>>> From: Marek Vasut
>>> Date: Thu, 10 Oct 2019 20:25:08 +0200
>>>
The KSZ driver uses one regmap per register width
On 10/13/19 2:21 AM, David Miller wrote:
> From: David Miller
> Date: Sat, 12 Oct 2019 17:20:55 -0700 (PDT)
>
>> From: Marek Vasut
>> Date: Thu, 10 Oct 2019 20:25:08 +0200
>>
>>> The KSZ driver uses one regmap per register width (8/16/32), each with
>>> it's own lock, but accessing the same set
From: David Miller
Date: Sat, 12 Oct 2019 17:20:55 -0700 (PDT)
> From: Marek Vasut
> Date: Thu, 10 Oct 2019 20:25:08 +0200
>
>> The KSZ driver uses one regmap per register width (8/16/32), each with
>> it's own lock, but accessing the same set of registers. In theory, it
>> is possible to creat
From: Marek Vasut
Date: Thu, 10 Oct 2019 20:25:08 +0200
> The KSZ driver uses one regmap per register width (8/16/32), each with
> it's own lock, but accessing the same set of registers. In theory, it
> is possible to create a race condition between these regmaps, although
> the underlying bus (S
The KSZ driver uses one regmap per register width (8/16/32), each with
it's own lock, but accessing the same set of registers. In theory, it
is possible to create a race condition between these regmaps, although
the underlying bus (SPI or I2C) locking should assure nothing bad will
really happen an
