Re: [PATCH v3 2/3] remoteproc: qcom: Hexagon resource handling

2016-11-21 Thread Avaneesh Kumar Dwivedi
On 11/19/2016 1:00 AM, Bjorn Andersson wrote: On Wed 16 Nov 07:17 PST 2016, Avaneesh Kumar Dwivedi wrote: On 11/8/2016 12:19 PM, Bjorn Andersson wrote: On Mon 07 Nov 04:37 PST 2016, Avaneesh Kumar Dwivedi wrote: Handling of clock and regulator resources as well as reset register programin

Re: [PATCH v3 2/3] remoteproc: qcom: Hexagon resource handling

2016-11-18 Thread Bjorn Andersson
On Wed 16 Nov 07:17 PST 2016, Avaneesh Kumar Dwivedi wrote: > > > On 11/8/2016 12:19 PM, Bjorn Andersson wrote: > >On Mon 07 Nov 04:37 PST 2016, Avaneesh Kumar Dwivedi wrote: > > > >>Handling of clock and regulator resources as well as reset > >>register programing differ according to version of

Re: [PATCH v3 2/3] remoteproc: qcom: Hexagon resource handling

2016-11-16 Thread Avaneesh Kumar Dwivedi
On 11/8/2016 12:19 PM, Bjorn Andersson wrote: On Mon 07 Nov 04:37 PST 2016, Avaneesh Kumar Dwivedi wrote: Handling of clock and regulator resources as well as reset register programing differ according to version of hexagon dsp hardware. Different version require different resources and diffe

Re: [PATCH v3 2/3] remoteproc: qcom: Hexagon resource handling

2016-11-07 Thread Bjorn Andersson
On Mon 07 Nov 04:37 PST 2016, Avaneesh Kumar Dwivedi wrote: > Handling of clock and regulator resources as well as reset > register programing differ according to version of hexagon > dsp hardware. Different version require different resources > and different parameters for same resource. Hence it

[PATCH v3 2/3] remoteproc: qcom: Hexagon resource handling

2016-11-07 Thread Avaneesh Kumar Dwivedi
Handling of clock and regulator resources as well as reset register programing differ according to version of hexagon dsp hardware. Different version require different resources and different parameters for same resource. Hence it is needed that resource handling is generic and independent of hexag