[...]

 >

quoted

Actually we always use R1B with CMD6 as per spec.

I fully agree that R1B is preferable, but it's not against the spec to
send CMD13 to poll for busy.

Moreover, we need to cope with the scenario when the host has
specified a maximum timeout that isn't sufficiently long enough for
the requested operation. Do you have another proposal for how to
manage this, but disabling MMC_RSP_BUSY?

Let's assume you driver would get a R1B for the CMD6 (we force it),
then what timeout would the driver be using if we would set
cmd.busy_timeout to 30ms?

/s/30ms/30s

Kind regards
Uffe