On 02/25, Akinobu Mita wrote: > 2016-02-25 7:08 GMT+09:00 Stephen Boyd <sboyd@xxxxxxxxxxxxxx>: > > Agreed. Plus, the userspace regulator consumer doesn't have any > > DT binding for it, so I don't see why we would have a DT binding > > for the clk one. > > OK. I'll drop a DT binding part of this driver. > > I'll still try to expose this feature by platform device instead of > exposing under clk debugfs. Because we don't want to allow controlling > all clock devices (which may result abuse of the feature). Instead, > this userspace consumer only allows explicitly specified devices to > control. I'm pretty lost on this whole patch. Is it for debug? Or is it to put clk control into userspace? If it's for debug, why not just keep this patch around locally and use it for debugging? If it's for userspace clk control we need to have a larger discussion around the concept of that (since Rob doesn't think it should be done at all) and ABI (sysfs or ioctl?) before moving forward. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- 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
