there is no hwmod entry for opt clocks this is extract from any clocks other than fck ick need to make use of clock fw apis if required  for fck ick do not use clock fw apis as omap device layer apis takes care of the same  there is a opt clk fld for other clocks  example  gpio has debounce clock there is a opt clk field en the hwmod structures but they are not enable when you enable the device  static int  enable clocks struct omap hwmod  oh the opt clocks are controlled by the device driver return so  looks like opt clocks has to be controlled by the device driver  therefore it is a software issue  the module should not dependeds of what are you running on the remote processor  can you please rephrase i am not sure i am following just telling we should not base a  module on what a remote processor is running  it should be generic  so the restriction from having one or multiple user should come from a  side  of curse if ducati side can manage only one user it can put a restriction on the rm running on ducati  however i think having only one user for all the resources is the safer way 