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
Unknown Object (File)
Sat, Nov 16, 7:02 PM
Unknown Object (File)
Oct 13 2024, 8:45 AM
Unknown Object (File)
Oct 7 2024, 6:59 PM
Unknown Object (File)
Oct 4 2024, 4:04 PM
Unknown Object (File)
Oct 3 2024, 4:04 AM
Unknown Object (File)
Oct 2 2024, 6:00 AM
Unknown Object (File)
Sep 27 2024, 8:01 AM
Unknown Object (File)
Sep 26 2024, 9:11 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

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

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 ↗(On Diff #44046)

min(<this stuff>, MAXPHYS);

sys/dev/sdhci/sdhci.c
2524 ↗(On Diff #44046)

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.