Re: [PATCH] mmc: core: add auto bkops support

From	Ulf Hansson <ulf.hansson@linaro.org>
Newsgroups	linux.kernel
Subject	Re: [PATCH] mmc: core: add auto bkops support
Date	2016-06-27 11:10 +0200
Message-ID	<rOAIi-6Df-17@gated-at.bofh.it> (permalink)
References	(3 earlier) <rJvpU-3Ie-11@gated-at.bofh.it> <rJvT1-3Sn-31@gated-at.bofh.it> <rJzjQ-6gW-27@gated-at.bofh.it> <rMNzX-28F-3@gated-at.bofh.it> <rN2fE-3kM-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

[...]

>>>> one possible way is to control it by mmc-utils on
>>>> user space?  So we should add a cmd for mmc-utils
>>>> there?
>>>
>>>
>>> That would be consistent with manual bkops.
>>>
>>
>>> From my first impression I agree, as that is the policy we have been
>>
>> sticking to when writing to persistent EXT_CSD persistent .
>> Although, in this case, I am actually wondering on what is the best
>> approach.
>
>
> I don't know what is the real meaning of "persistent". :)
> I don't know should we count auto bkops as the persistent
> registers....HS_TIMING and BUS_WIDTH should also be persistent
> registers as them are always used after initialization if not changing
> them?
>
> IHMO the more reasonable way is that:
> IIRC many settings for  EXT_CSD should be OTP, like hw-reset(162),
> reliable write(167) fw-configure(169)..etc, which are marked as R/W.
> These should be controlled by userpace or even by firmware when
> flashing emmc, like reliable write...

Yes, that's makes sense to me. OTP registers must only be written to
via mmc utils/userspace.

>
>
> I'm not sure whether should I updete this $SUBJUCT or migirating it to
> userspace... We need to come to an agreement :)
>

I don't have any issue to allow all non-OTP registers bits to be written.

Kind regards
Uffe

Back to linux.kernel | Previous | Next | Find similar | Unroll thread

Thread

Re: [PATCH] mmc: core: add auto bkops support Ulf Hansson <ulf.hansson@linaro.org> - 2016-06-27 11:10 +0200

csiph-web