[ANN] asic3_mmc machine-specific write protect lock handling

Hello kernel-discuss,

      Following the discussion of WP lock handling some devices have,
http://handhelds.org/hypermail/kernel-discuss/19/1929.html , I've
implemented a way to configure such handling on per-machine basis. Two
most common cases: use native ASIC3 handling and card w/o WP lock,
don't require writing any specific code. See commit message below for
details.

      To override default setting (use ASIC3 stuff), you'll need to
provide structure like:

static struct tmio_mmc_hwconfig h3900_mmc_hwconfig = {
      .mmc_get_ro = (void*)-1,
};

and pass it via ASIC3's platform_data's .tmio_mmc_hwconfig field. See
h3900.c for example.

      I've tested these refactors to not produce obvious regressions,
and that (void*)-1 value works as expected.

  
===8<==============Original message text===============
Update of /cvs/linux/kernel26/include/linux/soc
In directory h7.handhelds.org:/tmp/cvs-serv20042/include/linux/soc

Modified Files:
        tmio_mmc.h
Log Message:
asic3_mmc: Add support for machine-specific write-protect lock handling.
This is done via tmio_mmc_hwconfig::mmc_get_ro field. It may have following
values:
NULL: Use ASIC3 SD/MMC WP status bit
(void*)-1: Assume the card is always R/W (for cards without write lock,
like miniSD).
otherwise: Use this function to get lock status.

Also, small refactor for tmio_mmc_hwconfig to be available as host->hwconfig
instead of digging down to platform_device.

_______________________________________________
Cvs-updates-kernel mailing list
Cvs-updates-kernel_at_handhelds.org
https://handhelds.org/mailman/listinfo/cvs-updates-kernel

===8<===========End of original message text===========

-- 
Best regards,
 Paul                          mailto:pmiscml_at_gmail.com