On 09/09/15 04:33, Rajendra Nayak wrote:
On 09/09/2015 12:51 AM, Stephen Boyd wrote:
On 09/07, Rajendra Nayak wrote:
Yeah this might happen though because we've assigned the of_node
pointer to the tsens device before we register it on the platform
bus. The other way to pass that data down f
On 09/09/2015 09:03 AM, Rajendra Nayak wrote:
On 09/09/2015 12:51 AM, Stephen Boyd wrote:
On 09/07, Rajendra Nayak wrote:
Yeah this might happen though because we've assigned the of_node
pointer to the tsens device before we register it on the platform
bus. The other way to pass that data do
On 09/09/2015 12:51 AM, Stephen Boyd wrote:
On 09/07, Rajendra Nayak wrote:
Yeah this might happen though because we've assigned the of_node
pointer to the tsens device before we register it on the platform
bus. The other way to pass that data down from gcc to tsens would
be to not have an of_
On 09/07, Rajendra Nayak wrote:
> >
> >Yeah this might happen though because we've assigned the of_node
> >pointer to the tsens device before we register it on the platform
> >bus. The other way to pass that data down from gcc to tsens would
> >be to not have an of_node assigned to the tsens device
[]..
No. The driver should work just fine without having to
interrogate the device's compatible string. If we still need the
compatible check for some reason, then we can always match based
on qcom,gcc-msm8960, qcom,gcc-apq8064, etc. But I don't see why
Thats not quite possible I guess. 2 driv
On 09/02, Rajendra Nayak wrote:
> Stephen,
>
> >Also, I don't like having a subnode in DT. Why can't we use the
> >same node as the GCC node and create a virtual child device here
> >for tsens? We can assign the same of_node that this platform
> >device has so that DT keeps working
Stephen,
Also, I don't like having a subnode in DT. Why can't we use the
same node as the GCC node and create a virtual child device here
for tsens? We can assign the same of_node that this platform
device has so that DT keeps working correctly.
So the current driver looks up data based on com
[]..
Also, I don't like having a subnode in DT. Why can't we use the
same node as the GCC node and create a virtual child device here
for tsens? We can assign the same of_node that this platform
device has so that DT keeps working correctly.
So the current driver looks up data based on compatib
On 08/12, Bjorn Andersson wrote:
> On Wed 12 Aug 14:57 PDT 2015, Stephen Boyd wrote:
>
> > Here's the patch I'm suggesting. The device name is probably wrong, but
> > you get the idea.
>
> Looks very much like my take on it as well, I do however have concerns
> that suddenly the node called "clo
On 08/13, Rajendra Nayak wrote:
> >On 11/08/15 23:49, Stephen Boyd wrote:
> >>On 07/08, Rajendra Nayak wrote:
> >>>diff --git a/drivers/clk/qcom/gcc-msm8960.c
> >>>b/drivers/clk/qcom/gcc-msm8960.c
> >>>index eb6a4f9..2c80d03 100644
> >>>--- a/drivers/clk/qcom/gcc-msm8960.c
> >>>+++ b/drivers/clk/qc
On 11/08/15 23:49, Stephen Boyd wrote:
On 07/08, Rajendra Nayak wrote:
diff --git a/drivers/clk/qcom/gcc-msm8960.c
b/drivers/clk/qcom/gcc-msm8960.c
index eb6a4f9..2c80d03 100644
--- a/drivers/clk/qcom/gcc-msm8960.c
+++ b/drivers/clk/qcom/gcc-msm8960.c
@@ -15,6 +15,7 @@
#include
#include
On Wed 12 Aug 14:57 PDT 2015, Stephen Boyd wrote:
> On 08/12/2015 01:18 PM, Bjorn Andersson wrote:
> > On Tue 11 Aug 15:49 PDT 2015, Stephen Boyd wrote:
> >
> >> On 07/08, Rajendra Nayak wrote:
> >>> diff --git a/drivers/clk/qcom/gcc-msm8960.c
> >>> b/drivers/clk/qcom/gcc-msm8960.c
> >>> index eb
On 08/12/2015 01:18 PM, Bjorn Andersson wrote:
On Tue 11 Aug 15:49 PDT 2015, Stephen Boyd wrote:
On 07/08, Rajendra Nayak wrote:
diff --git a/drivers/clk/qcom/gcc-msm8960.c b/drivers/clk/qcom/gcc-msm8960.c
index eb6a4f9..2c80d03 100644
--- a/drivers/clk/qcom/gcc-msm8960.c
+++ b/drivers/clk/qco
On Tue 11 Aug 15:49 PDT 2015, Stephen Boyd wrote:
> On 07/08, Rajendra Nayak wrote:
> > diff --git a/drivers/clk/qcom/gcc-msm8960.c b/drivers/clk/qcom/gcc-msm8960.c
> > index eb6a4f9..2c80d03 100644
> > --- a/drivers/clk/qcom/gcc-msm8960.c
> > +++ b/drivers/clk/qcom/gcc-msm8960.c
> > @@ -15,6 +15,
On 11/08/15 23:49, Stephen Boyd wrote:
On 07/08, Rajendra Nayak wrote:
diff --git a/drivers/clk/qcom/gcc-msm8960.c b/drivers/clk/qcom/gcc-msm8960.c
index eb6a4f9..2c80d03 100644
--- a/drivers/clk/qcom/gcc-msm8960.c
+++ b/drivers/clk/qcom/gcc-msm8960.c
@@ -15,6 +15,7 @@
#include
#include
On 07/08, Rajendra Nayak wrote:
> diff --git a/drivers/clk/qcom/gcc-msm8960.c b/drivers/clk/qcom/gcc-msm8960.c
> index eb6a4f9..2c80d03 100644
> --- a/drivers/clk/qcom/gcc-msm8960.c
> +++ b/drivers/clk/qcom/gcc-msm8960.c
> @@ -15,6 +15,7 @@
> #include
> #include
> #include
> +#include
> #in
From: Srinivas Kandagatla
This patch adds support to add child devices to gcc as some of the
registers mapped by gcc are used by things like thermal sensors.
Signed-off-by: Srinivas Kandagatla
---
drivers/clk/qcom/gcc-msm8960.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --g
17 matches
Mail list logo