On Wed, Nov 15, 2017 at 11:15:00PM -0600, Rob Herring wrote: > On Wed, Nov 15, 2017 at 02:10:32PM +0000, srinivas.kandagatla@xxxxxxxxxx wrote: > > From: Sagar Dharia <sdharia@xxxxxxxxxxxxxx> > > > > SLIMbus (Serial Low Power Interchip Media Bus) is a specification > > developed by MIPI (Mobile Industry Processor Interface) alliance. > > SLIMbus is a 2-wire implementation, which is used to communicate with > > peripheral components like audio-codec. > > > > This patch adds device tree bindings for the slimbus. > > > > Signed-off-by: Sagar Dharia <sdharia@xxxxxxxxxxxxxx> > > Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@xxxxxxxxxx> > > --- > > Documentation/devicetree/bindings/slimbus/bus.txt | 50 +++++++++++++++++++++++ > > 1 file changed, 50 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/slimbus/bus.txt > > Reviewed-by: Rob Herring <robh@xxxxxxxxxx> I still have some reservations about the putting the MID and PID in the compatible sting, are we sure this is what we want to do? As has been discussed previous the discoverability of SLIMbus is really theoretical since you really always need to bind a driver to power on the device, since power is not part of the bus itself. Many devices (ours included) will support SLIMbus and other interfaces, this means we will need a different compatible string between SLIMbus and I2C/SPI, which feels a little icky. Additionally it does make the compatible strings really unreadable and which is a little annoying when looking at device trees as you can't easily see what things are. Thanks, Charles -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
