Javier, On Wed, Nov 19, 2014 at 2:07 AM, Javier Martinez Canillas <javier.martinez@xxxxxxxxxxxxxxx> wrote: > Hello Doug, > > Thanks for your feedback. > > On 11/18/2014 06:50 PM, Doug Anderson wrote: >> This is common practice in the Chrome OS tree, but we've gotten >> pushback from upstream questioning about whether "spidev" is really a >> physical device. See: >> >> http://www.spinics.net/lists/linux-samsung-soc/msg29563.html >> > > I see, I thought that it was a common practice in the mainline kernel > too since I saw that many board DTS currently have a spidev node: > > $ git grep 'compatible = "spidev"' arch/arm/boot/dts/ | wc -l > 19 > >> >> I don't really have an answer for something better to do here but I >> figured I'd at least bring up the point. >> > > I wonder how the spidev user-space interface is supposed to be used > when booting with Device Trees. OK. Please don't take my comments as a NAK on this patch. I should have done the same grep myself before sending--sorry. I just remembered the old conversation and looked for that instead. If the convention is to use "spidev" like this then I guess we're OK. I do wish it was a little more like "i2c" myself where you could get a direct access interface no matter what driver was bound underneath (and also if no drivers were bound underneath). ...but I could just be naive. ;) -Doug -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |