summaryrefslogtreecommitdiff
path: root/block/blk-core.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2024-02-10 18:56:39 +0300
committerLinus Torvalds <torvalds@linux-foundation.org>2024-02-10 18:56:39 +0300
commita38ff5bbf9799dd944c762412aaebc54818407f5 (patch)
tree4a89dae3d71435e593fac78ea3e2f80900c7ac08 /block/blk-core.c
parent5a7ec87063c0fbb7706fdccb0cc890757da6f4a1 (diff)
parent7ed4380009e96d9e9c605e12822e987b35b05648 (diff)
downloadlinux-a38ff5bbf9799dd944c762412aaebc54818407f5.tar.xz
Merge tag 'firewire-fixes-6.8-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394
Pull firewire fix from Takashi Sakamoto: "A change to accelerate the device detection step in some cases. In the self-identification step after bus-reset, all nodes in the same bus broadcast selfID packet including the value of gap count. The value is related to the cable hops between nodes, and used to calculate the subaction gap and the arbitration reset gap. When each node has the different value of the gap count, the asynchronous communication between them is unreliable, since an asynchronous transaction could be interrupted by another asynchronous transaction before completion. The gap count inconsistency can be resolved by several ways; e.g. the transfer of PHY configuration packet and generation of bus-reset. The current implementation of firewire stack can correctly detect the gap count inconsistency, however the recovery action from the inconsistency tends to be delayed after reading configuration ROM of root node. This results in the long time to probe devices in some combinations of hardware. Here the stack is changed to schedule the action as soon as possible" * tag 'firewire-fixes-6.8-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394: firewire: core: send bus reset promptly on gap count error
Diffstat (limited to 'block/blk-core.c')
0 files changed, 0 insertions, 0 deletions