Drop legacy support for omap3517
Get series with b4
b4 am 201501242314.58201@paliVersions newest first
- v1 Latest0 of 4 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 4 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] Drop legacy support for omap3517
Quoted 15 lines · On Saturday 24 January 2015 23:08:00 Arnd Bergmann wrote:
Quoted 10 lines · On Saturday 24 January 2015 13:00:00 Pali Roh?r wrote:
Another regression for DT setup (which does not occur for board code):
omap_hsmmcdriver does not exportslot_namesysfs entry because it not supported by DT yet. Entryslot_nameis used by userspace application to determinate if mmc block device is internal eMMC memory or external uSD card. So support for this property also in DT is needed.Here is simple patch which fix this problem:
The sysfs file only exists for the two OMAP drivers, and the naming is used only by board-n8x0, board-rx51 and board-omap3logic.
Quoted 5 lines
It may be better to add a board-specific hack for these to keep the existing user space working but not spread the use of this file anywhere else.
Arnd
Why? omap_hsmmc.c has already support for slot_name sysfs entry, just it is not filled from DT data (only from platform_data)...
Signature · 9 lines
Pali Roh?r pali.rohar at gmail.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150124/9901f95a/attachment.sig>