This might add much value to the application and usage of Tablets and Mobile devices as the PCI is a very much developed and deeply penetrated in the existing major operating systems architecture. PCI has undergone developments and modifications at every layer in terms of power consumption, configuration and adaption. Now by keeping the upper architecture same and changing only the PHY in the standard it will be surely a revolution creating step in electronics industry.
I would have to be more familiar with the interface before I would consider it as a general-purpose communications abstraction. As far as I can see it implements a point-to-point link. Does it also include error detection and correction? Multiple virtual channels? Guaranteed latencies?
The abstraction that I am most used to is a network interface, which provides any number of delivery protocols. How would this compare to that?
In the meantime, here's a recent blog on MIPI by Patrick Mannion, and a link to a webinar on the subject (archived). The webinar is called: Demystify MIPI M-PHY Receiver Physical Layer Test Challenges.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.