On 04/19/2016 02:15 AM, Ulf Hansson wrote:
[...]
From this discussion I have understood that we clearly need a way to
describe mmc slots in DT!
Unfortunate we should have discussed this before you decided to ship
devices with DTBs containing non accepted DT bindings, but hey better
late than never! :-)
This is a point where the DT and mmc maintainers have a continual
misunderstanding of the facts.
There were requests to discuss the binding as far back as 2012:
https://www.linux-mips.org/archives/linux-mips/2012-05/msg00119.html
They were met with silence.
The firmware containing these bindings is out in the wild. If we
deprecate some of the bindings, the driver will still have to support
them in the future.
In the case of OCTEON based devices, the device tree bindings are a
firmware <--> kernel ABI as the device trees always come from the
firmware and not some other place.
David Daney
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
