diff for duplicates of <017c01d3c08a$cf903270$6eb09750$@codeaurora.org> diff --git a/a/1.txt b/N1/1.txt index 24ed072..307ca62 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,18 +1,23 @@ -Understood, what you mean. I assumed that the cpufreq-dt is generic driver, and adding architecture specific code to it is no not correct from architectural point of view. Anyway, I'm considering adding a platform specific cpufreq driver, which will handle the efuse data as well. +Understood, what you mean. I assumed that the cpufreq-dt is generic = +driver, and adding architecture specific code to it is no not correct = +from architectural point of view. Anyway, I'm considering adding a = +platform specific cpufreq driver, which will handle the efuse data as = +well. Meanwhile this is the way to use the generic driver. > -----Original Message----- > From: Stephen Boyd <sboyd@kernel.org> > Sent: Tuesday, March 20, 2018 22:06 -> To: ilialin@codeaurora.org; linux-arm-kernel@lists.infradead.org; linux-arm- +> To: ilialin@codeaurora.org; linux-arm-kernel@lists.infradead.org; = +linux-arm- > msm@vger.kernel.org; linux-clk@vger.kernel.org; sboyd@codeaurora.org > Cc: mark.rutland@arm.com; devicetree@vger.kernel.org; > rnayak@codeaurora.org; robh@kernel.org; will.deacon@arm.com; > amit.kucheria@linaro.org; tfinkel@codeaurora.org; > nicolas.dechesne@linaro.org; celster@codeaurora.org > Subject: RE: [PATCH v3 09/10] DT: QCOM: Add cpufreq-dt to msm8996 -> +>=20 > Quoting ilialin@codeaurora.org (2018-03-20 06:46:19) > > > From: Stephen Boyd <sboyd@kernel.org> Quoting Ilia Lin (2018-02-14 > > > 05:59:51) @@ -22,24 +27,27 @@ Meanwhile this is the way to use the generic driver. > > > > --- a/drivers/cpufreq/cpufreq-dt-platdev.c > > > > +++ b/drivers/cpufreq/cpufreq-dt-platdev.c > > > > @@ -95,6 +95,9 @@ -> > > > { .compatible = "xlnx,zynq-7000", }, -> > > > { .compatible = "xlnx,zynqmp", }, +> > > > { .compatible =3D "xlnx,zynq-7000", }, +> > > > { .compatible =3D "xlnx,zynqmp", }, > > > > -> > > > + { .compatible = "qcom,msm8996", }, -> > > > + { .compatible = "qcom,apq8096", }, +> > > > + { .compatible =3D "qcom,msm8996", }, +> > > > + { .compatible =3D "qcom,apq8096", }, > > > > + > > > > > > Why can't we base it on the kryocc node being present? -> > This could be good idea, if I would writing a platform specific cpufreq driver, +> > This could be good idea, if I would writing a platform specific = +cpufreq driver, > which may be a future option. -> +>=20 > Well maybe cpufreq-dt can also look at the cpus nodes for a cpu with a -> certain type (in this case kryo). Then we can add cpufreq dt based on that +> certain type (in this case kryo). Then we can add cpufreq dt based on = +that > CPU node being there. -> +>=20 > > > Or even populate > > > the cpufreq-dt from the kryocc driver? -> > There is a problem that during the clock probe the OPP table still doesn't +> > There is a problem that during the clock probe the OPP table still = +doesn't > exist. -> +>=20 > The OPP table is in DT? Why doesn't it exist? diff --git a/a/content_digest b/N1/content_digest index f2666ce..fbfd61d 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -7,36 +7,41 @@ "Subject\0RE: [PATCH v3 09/10] DT: QCOM: Add cpufreq-dt to msm8996\0" "Date\0Tue, 20 Mar 2018 22:34:04 +0200\0" "To\0'Stephen Boyd' <sboyd@kernel.org>" - linux-arm-kernel@lists.infradead.org - linux-arm-msm@vger.kernel.org - linux-clk@vger.kernel.org - " sboyd@codeaurora.org\0" - "Cc\0mark.rutland@arm.com" - devicetree@vger.kernel.org - rnayak@codeaurora.org - robh@kernel.org - will.deacon@arm.com - amit.kucheria@linaro.org - tfinkel@codeaurora.org - nicolas.dechesne@linaro.org - " celster@codeaurora.org\0" + <linux-arm-kernel@lists.infradead.org> + <linux-arm-msm@vger.kernel.org> + <linux-clk@vger.kernel.org> + " <sboyd@codeaurora.org>\0" + "Cc\0<mark.rutland@arm.com>" + <devicetree@vger.kernel.org> + <rnayak@codeaurora.org> + <robh@kernel.org> + <will.deacon@arm.com> + <amit.kucheria@linaro.org> + <tfinkel@codeaurora.org> + <nicolas.dechesne@linaro.org> + " <celster@codeaurora.org>\0" "\00:1\0" "b\0" - "Understood, what you mean. I assumed that the cpufreq-dt is generic driver, and adding architecture specific code to it is no not correct from architectural point of view. Anyway, I'm considering adding a platform specific cpufreq driver, which will handle the efuse data as well.\n" + "Understood, what you mean. I assumed that the cpufreq-dt is generic =\n" + "driver, and adding architecture specific code to it is no not correct =\n" + "from architectural point of view. Anyway, I'm considering adding a =\n" + "platform specific cpufreq driver, which will handle the efuse data as =\n" + "well.\n" "\n" "Meanwhile this is the way to use the generic driver.\n" "\n" "> -----Original Message-----\n" "> From: Stephen Boyd <sboyd@kernel.org>\n" "> Sent: Tuesday, March 20, 2018 22:06\n" - "> To: ilialin@codeaurora.org; linux-arm-kernel@lists.infradead.org; linux-arm-\n" + "> To: ilialin@codeaurora.org; linux-arm-kernel@lists.infradead.org; =\n" + "linux-arm-\n" "> msm@vger.kernel.org; linux-clk@vger.kernel.org; sboyd@codeaurora.org\n" "> Cc: mark.rutland@arm.com; devicetree@vger.kernel.org;\n" "> rnayak@codeaurora.org; robh@kernel.org; will.deacon@arm.com;\n" "> amit.kucheria@linaro.org; tfinkel@codeaurora.org;\n" "> nicolas.dechesne@linaro.org; celster@codeaurora.org\n" "> Subject: RE: [PATCH v3 09/10] DT: QCOM: Add cpufreq-dt to msm8996\n" - "> \n" + ">=20\n" "> Quoting ilialin@codeaurora.org (2018-03-20 06:46:19)\n" "> > > From: Stephen Boyd <sboyd@kernel.org> Quoting Ilia Lin (2018-02-14\n" "> > > 05:59:51)\n" @@ -46,26 +51,29 @@ "> > > > --- a/drivers/cpufreq/cpufreq-dt-platdev.c\n" "> > > > +++ b/drivers/cpufreq/cpufreq-dt-platdev.c\n" "> > > > @@ -95,6 +95,9 @@\n" - "> > > > { .compatible = \"xlnx,zynq-7000\", },\n" - "> > > > { .compatible = \"xlnx,zynqmp\", },\n" + "> > > > { .compatible =3D \"xlnx,zynq-7000\", },\n" + "> > > > { .compatible =3D \"xlnx,zynqmp\", },\n" "> > > >\n" - "> > > > + { .compatible = \"qcom,msm8996\", },\n" - "> > > > + { .compatible = \"qcom,apq8096\", },\n" + "> > > > + { .compatible =3D \"qcom,msm8996\", },\n" + "> > > > + { .compatible =3D \"qcom,apq8096\", },\n" "> > > > +\n" "> > >\n" "> > > Why can't we base it on the kryocc node being present?\n" - "> > This could be good idea, if I would writing a platform specific cpufreq driver,\n" + "> > This could be good idea, if I would writing a platform specific =\n" + "cpufreq driver,\n" "> which may be a future option.\n" - "> \n" + ">=20\n" "> Well maybe cpufreq-dt can also look at the cpus nodes for a cpu with a\n" - "> certain type (in this case kryo). Then we can add cpufreq dt based on that\n" + "> certain type (in this case kryo). Then we can add cpufreq dt based on =\n" + "that\n" "> CPU node being there.\n" - "> \n" + ">=20\n" "> > > Or even populate\n" "> > > the cpufreq-dt from the kryocc driver?\n" - "> > There is a problem that during the clock probe the OPP table still doesn't\n" + "> > There is a problem that during the clock probe the OPP table still =\n" + "doesn't\n" "> exist.\n" - "> \n" + ">=20\n" > The OPP table is in DT? Why doesn't it exist? -3cb5fd2d80b7b90d9e80819ed6a4541b72dbd8044a4674f931ae7e1e638dc88d +f0baa1ae5305479516842cdcf981e10b825bc1d6d8e5fbb107d6c85261782f41
diff --git a/a/1.txt b/N2/1.txt index 24ed072..4105480 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -5,15 +5,15 @@ Meanwhile this is the way to use the generic driver. > -----Original Message----- > From: Stephen Boyd <sboyd@kernel.org> > Sent: Tuesday, March 20, 2018 22:06 -> To: ilialin@codeaurora.org; linux-arm-kernel@lists.infradead.org; linux-arm- -> msm@vger.kernel.org; linux-clk@vger.kernel.org; sboyd@codeaurora.org -> Cc: mark.rutland@arm.com; devicetree@vger.kernel.org; -> rnayak@codeaurora.org; robh@kernel.org; will.deacon@arm.com; -> amit.kucheria@linaro.org; tfinkel@codeaurora.org; -> nicolas.dechesne@linaro.org; celster@codeaurora.org +> To: ilialin at codeaurora.org; linux-arm-kernel at lists.infradead.org; linux-arm- +> msm at vger.kernel.org; linux-clk at vger.kernel.org; sboyd at codeaurora.org +> Cc: mark.rutland at arm.com; devicetree at vger.kernel.org; +> rnayak at codeaurora.org; robh at kernel.org; will.deacon at arm.com; +> amit.kucheria at linaro.org; tfinkel at codeaurora.org; +> nicolas.dechesne at linaro.org; celster at codeaurora.org > Subject: RE: [PATCH v3 09/10] DT: QCOM: Add cpufreq-dt to msm8996 > -> Quoting ilialin@codeaurora.org (2018-03-20 06:46:19) +> Quoting ilialin at codeaurora.org (2018-03-20 06:46:19) > > > From: Stephen Boyd <sboyd@kernel.org> Quoting Ilia Lin (2018-02-14 > > > 05:59:51) > > > > diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c diff --git a/a/content_digest b/N2/content_digest index f2666ce..8bb2ac5 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -3,23 +3,10 @@ "ref\0152147812199.242365.11821734771337881765@swboyd.mtv.corp.google.com\0" "ref\0013a01d3c051$d65a9160$830fb420$@codeaurora.org\0" "ref\0152157637794.125118.12382168941652366593@swboyd.mtv.corp.google.com\0" - "From\0<ilialin@codeaurora.org>\0" - "Subject\0RE: [PATCH v3 09/10] DT: QCOM: Add cpufreq-dt to msm8996\0" + "From\0ilialin@codeaurora.org (ilialin at codeaurora.org)\0" + "Subject\0[PATCH v3 09/10] DT: QCOM: Add cpufreq-dt to msm8996\0" "Date\0Tue, 20 Mar 2018 22:34:04 +0200\0" - "To\0'Stephen Boyd' <sboyd@kernel.org>" - linux-arm-kernel@lists.infradead.org - linux-arm-msm@vger.kernel.org - linux-clk@vger.kernel.org - " sboyd@codeaurora.org\0" - "Cc\0mark.rutland@arm.com" - devicetree@vger.kernel.org - rnayak@codeaurora.org - robh@kernel.org - will.deacon@arm.com - amit.kucheria@linaro.org - tfinkel@codeaurora.org - nicolas.dechesne@linaro.org - " celster@codeaurora.org\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "Understood, what you mean. I assumed that the cpufreq-dt is generic driver, and adding architecture specific code to it is no not correct from architectural point of view. Anyway, I'm considering adding a platform specific cpufreq driver, which will handle the efuse data as well.\n" @@ -29,15 +16,15 @@ "> -----Original Message-----\n" "> From: Stephen Boyd <sboyd@kernel.org>\n" "> Sent: Tuesday, March 20, 2018 22:06\n" - "> To: ilialin@codeaurora.org; linux-arm-kernel@lists.infradead.org; linux-arm-\n" - "> msm@vger.kernel.org; linux-clk@vger.kernel.org; sboyd@codeaurora.org\n" - "> Cc: mark.rutland@arm.com; devicetree@vger.kernel.org;\n" - "> rnayak@codeaurora.org; robh@kernel.org; will.deacon@arm.com;\n" - "> amit.kucheria@linaro.org; tfinkel@codeaurora.org;\n" - "> nicolas.dechesne@linaro.org; celster@codeaurora.org\n" + "> To: ilialin at codeaurora.org; linux-arm-kernel at lists.infradead.org; linux-arm-\n" + "> msm at vger.kernel.org; linux-clk at vger.kernel.org; sboyd at codeaurora.org\n" + "> Cc: mark.rutland at arm.com; devicetree at vger.kernel.org;\n" + "> rnayak at codeaurora.org; robh at kernel.org; will.deacon at arm.com;\n" + "> amit.kucheria at linaro.org; tfinkel at codeaurora.org;\n" + "> nicolas.dechesne at linaro.org; celster at codeaurora.org\n" "> Subject: RE: [PATCH v3 09/10] DT: QCOM: Add cpufreq-dt to msm8996\n" "> \n" - "> Quoting ilialin@codeaurora.org (2018-03-20 06:46:19)\n" + "> Quoting ilialin at codeaurora.org (2018-03-20 06:46:19)\n" "> > > From: Stephen Boyd <sboyd@kernel.org> Quoting Ilia Lin (2018-02-14\n" "> > > 05:59:51)\n" "> > > > diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c\n" @@ -68,4 +55,4 @@ "> \n" > The OPP table is in DT? Why doesn't it exist? -3cb5fd2d80b7b90d9e80819ed6a4541b72dbd8044a4674f931ae7e1e638dc88d +b55f15e3908158c156fb9e202198f56b809562855908799b7da19c99dc607fbd
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.