sdhci: Use bus_topo_lock and taskqueue_bus for hotplug events
ClosedPublic
Actions

Authored by jhb on Mar 6 2025, 10:07 PM.

Tags

None

Referenced Files

	Unknown Object (File)
	Sun, Apr 6, 9:42 AM

	Unknown Object (File)
	Wed, Apr 2, 5:16 AM

	Unknown Object (File)
	Mar 20 2025, 3:36 PM

	Unknown Object (File)
	Mar 19 2025, 9:56 AM

	Unknown Object (File)
	Mar 11 2025, 2:51 AM

	Unknown Object (File)
	Mar 10 2025, 8:38 PM

	Unknown Object (File)
	Mar 10 2025, 6:07 PM

	Unknown Object (File)
	Mar 8 2025, 2:06 PM

View All 13 Files

Subscribers

None

Details

Reviewers

imp

Commits

rGaaf0a7302d10: sdhci: Use bus_topo_lock and taskqueue_bus for hotplug events

Summary

Drop SDHCI_LOCK and instead acquire bus_topo_lock when adding and
removing new-bus devices.

Diff Detail

Repository

rG FreeBSD src repository

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

jhb requested review of this revision.Mar 6 2025, 10:07 PM

jhb created this revision.

Harbormaster completed remote builds in B62807: Diff 151983.Mar 6 2025, 10:07 PM

jhb added a parent revision: D49270: mmc: Use bus_topo_lock and taskqueue_bus while adding/removing child devices.Mar 6 2025, 10:07 PM

jhb added a child revision: D49272: hdaa: Don't hold a mutex while creating child devices.

imp accepted this revision.Mar 6 2025, 10:19 PM

This revision is now accepted and ready to land.Mar 6 2025, 10:19 PM

Closed by commit rGaaf0a7302d10: sdhci: Use bus_topo_lock and taskqueue_bus for hotplug events (authored by jhb). · Explain WhyMar 10 2025, 5:36 PM

This revision was automatically updated to reflect the committed changes.

jhb added a commit: rGaaf0a7302d10: sdhci: Use bus_topo_lock and taskqueue_bus for hotplug events.

Revision Contents
Changeset List

Path

Size

sys/

dev/

sdhci/

sdhci.c

16 lines

Diff 152094

View Options

sdhci: Use bus_topo_lock and taskqueue_bus for hotplug eventsClosedPublicActions