>>> +void mmc_start_bkops(struct mmc_card *card)
>>> +{
>>> + int err;
>>> + int timeout;
>>> + u8 use_busy_signal;
>>> +
>>> + BUG_ON(!card);
>>> + if (!card->ext_csd.bkops_en || !(card->host->caps2 & MMC_CAP2_BKOPS))
>>
>> Can you please explain why we need to have MMC_CAP2_BKOPS in addition to
>> card->ext_csd.bkops_en?
> We can remove the MMC_CAP2_BKOPS. but if someone didn't want to use the
> bkops feature,
> then can control with that capability.
I don't think that the host can decide not to support BKOPs if it is
enabled on the card. In such a case we might run into performance
degradation or even non functionality of the card if it needs to perform
BKOPs.
Thanks,
Maya
--
Sent by consultant of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
