Page MenuHomeFreeBSD

Use information about max data size that the controller is able to operate
ClosedPublic

Authored by kibab on Jun 18 2018, 9:54 PM.
Tags
None
Referenced Files
F110598753: D15892.id55687.diff
Thu, Feb 20, 5:17 PM
Unknown Object (File)
Thu, Feb 6, 4:12 AM
Unknown Object (File)
Sat, Jan 25, 7:41 PM
Unknown Object (File)
Fri, Jan 24, 4:56 PM
Unknown Object (File)
Fri, Jan 24, 5:05 AM
Unknown Object (File)
Jan 18 2025, 5:54 PM
Unknown Object (File)
Dec 31 2024, 10:08 PM
Unknown Object (File)
Dec 9 2024, 5:58 PM
Subscribers

Details

Summary

Using DFLTPHYS/MAXPHYS is not always OK, instead make it possible for the
controller driver to provide maximum data size to MMCCAM, and use it there.

The old stack already does this.

Diff Detail

Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 17425
Build 17257: arc lint + arc unit

Event Timeline

The Allwinner part seems ok.

This revision is now accepted and ready to land.Jun 18 2018, 9:57 PM
This revision now requires review to proceed.Jun 19 2018, 11:29 AM
sys/cam/mmc/mmc_da.c
1514

min(<this stuff>, MAXPHYS);

sys/dev/sdhci/sdhci.c
2524

where does the mmc.host_maxa_data get set here? It looks like the break should be deleted and then 'else max_data = 65536;' added.

  • Address comments in D15892 wrt max_data setting and MIN(MAX_PHYS,...)
  • MIN(MAXPHYS) for D15892
This revision is now accepted and ready to land.Apr 1 2019, 6:24 PM
This revision was automatically updated to reflect the committed changes.