On Mon, Aug 25, 2014 at 05:04:20PM -0700, Kuninori Morimoto wrote: > > That's something we need to fix, but I don't think removing the stream names > > is the right way to do this. In a multi CODEC environment you'll quite > > likely end up with widgets of the same name. Ideally a route endpoint would > > be expressed by a tuple of DT node and pin name. But I don't think it is > > possible to mix integer and string elements in a property. It's not. Now that we have preprocessor support it's a lot easier to just use numbers though - the legibility problems from just using raw numbers in big tables don't apply so much any more. > Thank you for your advice. > "DT node and name" seems nice idea, but it works on DT case only ? > Anyway, I re-consider about this too. > It can be trial and error... I think that for hardware which has fairly monolithic audio blocks using DPCM it might be worth thinking about providing a way for the DT to look like the DT for a simple I2S DAI with the driver for the IP in the SoC filling in all the structure needed by DPCM.
Attachment:
signature.asc
Description: Digital signature
