diff options
| author | Linus Walleij | 2017-05-19 15:37:30 +0200 |
|---|---|---|
| committer | Ulf Hansson | 2017-06-20 10:30:26 +0200 |
| commit | 0493f6fe5bdee8ac101a1a0c449971c2d4665e99 (patch) | |
| tree | f863aaf707e68d23263634ec9246cb609c8e8a50 /drivers/mmc/core/mmc_ops.c | |
| parent | mmc: block: Move DRV OP issue function (diff) | |
| download | kernel-qcow2-linux-0493f6fe5bdee8ac101a1a0c449971c2d4665e99.tar.gz kernel-qcow2-linux-0493f6fe5bdee8ac101a1a0c449971c2d4665e99.tar.xz kernel-qcow2-linux-0493f6fe5bdee8ac101a1a0c449971c2d4665e99.zip | |
mmc: block: Move boot partition locking into a driver op
This moves the boot partition lock command (issued from sysfs)
into a custom block layer request, just like the ioctl()s,
getting rid of yet another instance of mmc_get_card().
Since we now have two operations issuing special DRV_OP's, we
rename the result variable ->drv_op_result.
Tested by locking the boot partition from userspace:
> cd /sys/devices/platform/soc/80114000.sdi4_per2/mmc_host/mmc3/
mmc3:0001/block/mmcblk3/mmcblk3boot0
> echo 1 > ro_lock_until_next_power_on
[ 178.645324] mmcblk3boot1: Locking boot partition ro until next power on
[ 178.652221] mmcblk3boot0: Locking boot partition ro until next power on
Also tested this with a huge dd job in the background: it
is now possible to lock the boot partitions on the card even
under heavy I/O.
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Diffstat (limited to 'drivers/mmc/core/mmc_ops.c')
0 files changed, 0 insertions, 0 deletions