diff for duplicates of <20130820000625.4443.23018@quantum> diff --git a/a/1.txt b/N1/1.txt index 6daad8b..948cb65 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -5,7 +5,8 @@ Quoting Mark Rutland (2013-08-19 02:35:43) > > > > > > > Also I would make this option required. Use a dummy clock for > > > > > > > mux > > > > > > > inputs that are grounded for a specific SoC. -> > > > > > +> > > > > > = + > > > > > > Some clocks are not from CCM and we haven't defined in > > > > > > imx6q-clk.txt, > > > > > > so in most cases we can't provide a phandle for them, eg: @@ -15,24 +16,36 @@ Quoting Mark Rutland (2013-08-19 02:35:43) > > > > > > looks more flexible to me and a default one is ensured even if > > > > > > it's > > > > > > missing. -> > > > > -> > > > > <&clks 0> is the dummy clock. This can be used for all input clocks +> > > > > = + +> > > > > <&clks 0> is the dummy clock. This can be used for all input cloc= +ks > > > > > not > > > > > defined by the SoC. -> > > > +> > > > = + > > > > Where does this assumption come from? Is it documented anywhere? -> > > +> > > = + > > > This is how all i.MX clock bindings currently are. See > > > Documentation/devicetree/bindings/clock/imx*-clock.txt -> > +> > = + > > OK, thanks. -> > -> > I guess we need some discussion on dummy clocks vs skipped clocks. I think +> > = + +> > I guess we need some discussion on dummy clocks vs skipped clocks. I th= +ink = + > > we want some consistency on this, don't we? -> > -> > If we really need a dummy clock, then we might also want a generic way to +> > = + +> > If we really need a dummy clock, then we might also want a generic way = +to = + > > specify it. -> +> = + > What do we actually mean by a "dummy clock"? We already have bindings > for "fixed-clock" and co friends describe relatively simple > preconfigured clocks. @@ -47,10 +60,12 @@ I'll add this to the todo list. Regards, Mike -> +> = + > If a clock isn't actually wired, we shouldn't describe it at all, or > we're describing what Linux wants to think rather than what the hardware > actually is. That can easily be handled with clock-names. -> +> = + > Thanks, > Mark. diff --git a/a/content_digest b/N1/content_digest index ea2ce0b..5b73696 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -33,7 +33,8 @@ "> > > > > > > Also I would make this option required. Use a dummy clock for\n" "> > > > > > > mux\n" "> > > > > > > inputs that are grounded for a specific SoC.\n" - "> > > > > > \n" + "> > > > > > =\n" + "\n" "> > > > > > Some clocks are not from CCM and we haven't defined in\n" "> > > > > > imx6q-clk.txt,\n" "> > > > > > so in most cases we can't provide a phandle for them, eg:\n" @@ -43,24 +44,36 @@ "> > > > > > looks more flexible to me and a default one is ensured even if\n" "> > > > > > it's\n" "> > > > > > missing.\n" - "> > > > > \n" - "> > > > > <&clks 0> is the dummy clock. This can be used for all input clocks\n" + "> > > > > =\n" + "\n" + "> > > > > <&clks 0> is the dummy clock. This can be used for all input cloc=\n" + "ks\n" "> > > > > not\n" "> > > > > defined by the SoC.\n" - "> > > > \n" + "> > > > =\n" + "\n" "> > > > Where does this assumption come from? Is it documented anywhere?\n" - "> > > \n" + "> > > =\n" + "\n" "> > > This is how all i.MX clock bindings currently are. See\n" "> > > Documentation/devicetree/bindings/clock/imx*-clock.txt\n" - "> > \n" + "> > =\n" + "\n" "> > OK, thanks.\n" - "> > \n" - "> > I guess we need some discussion on dummy clocks vs skipped clocks. I think \n" + "> > =\n" + "\n" + "> > I guess we need some discussion on dummy clocks vs skipped clocks. I th=\n" + "ink =\n" + "\n" "> > we want some consistency on this, don't we?\n" - "> > \n" - "> > If we really need a dummy clock, then we might also want a generic way to \n" + "> > =\n" + "\n" + "> > If we really need a dummy clock, then we might also want a generic way =\n" + "to =\n" + "\n" "> > specify it.\n" - "> \n" + "> =\n" + "\n" "> What do we actually mean by a \"dummy clock\"? We already have bindings\n" "> for \"fixed-clock\" and co friends describe relatively simple\n" "> preconfigured clocks.\n" @@ -75,12 +88,14 @@ "Regards,\n" "Mike\n" "\n" - "> \n" + "> =\n" + "\n" "> If a clock isn't actually wired, we shouldn't describe it at all, or\n" "> we're describing what Linux wants to think rather than what the hardware\n" "> actually is. That can easily be handled with clock-names.\n" - "> \n" + "> =\n" + "\n" "> Thanks,\n" > Mark. -3bd0fd02c436b64602b877ab497afe8687b50a70ad380ee952f81cb47d44617c +4509eb0470c22218ac9a7f8ec4a3c9013f9fa6ae36e0644bffe3de18f1f896b3
diff --git a/a/content_digest b/N2/content_digest index ea2ce0b..eaf630f 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -8,22 +8,22 @@ "Date\0Mon, 19 Aug 2013 17:06:25 -0700\0" "To\0Mark Rutland <mark.rutland@arm.com>" " Tomasz Figa <tomasz.figa@gmail.com>\0" - "Cc\0devicetree@vger.kernel.org <devicetree@vger.kernel.org>" - alsa-devel@alsa-project.org <alsa-devel@alsa-project.org> - lars@metafoo.de <lars@metafoo.de> + "Cc\0Sascha Hauer <s.hauer@pengutronix.de>" + Nicolin Chen <b42378@freescale.com> ian.campbell@citrix.com <ian.campbell@citrix.com> Pawel Moll <Pawel.Moll@arm.com> - swarren@wwwdotorg.org <swarren@wwwdotorg.org> - festevam@gmail.com <festevam@gmail.com> - Sascha Hauer <s.hauer@pengutronix.de> - Nicolin Chen <b42378@freescale.com> - timur@tabi.org <timur@tabi.org> - rob.herring@calxeda.com <rob.herring@calxeda.com> + galak@codeaurora.org <galak@codeaurora.org> broonie@kernel.org <broonie@kernel.org> + lars@metafoo.de <lars@metafoo.de> p.zabel@pengutronix.de <p.zabel@pengutronix.de> - galak@codeaurora.org <galak@codeaurora.org> + linuxppc-dev@lists.ozlabs.org <linuxppc-dev@lists.ozlabs.org> + alsa-devel@alsa-project.org <alsa-devel@alsa-project.org> + devicetree@vger.kernel.org <devicetree@vger.kernel.org> + timur@tabi.org <timur@tabi.org> + rob.herring@calxeda.com <rob.herring@calxeda.com> shawn.guo@linaro.org <shawn.guo@linaro.org> - " linuxppc-dev@lists.ozlabs.org <linuxppc-dev@lists.ozlabs.org>\0" + festevam@gmail.com <festevam@gmail.com> + " swarren@wwwdotorg.org <swarren@wwwdotorg.org>\0" "\00:1\0" "b\0" "Quoting Mark Rutland (2013-08-19 02:35:43)\n" @@ -83,4 +83,4 @@ "> Thanks,\n" > Mark. -3bd0fd02c436b64602b877ab497afe8687b50a70ad380ee952f81cb47d44617c +3242e6a9008eb682c1c85859e1929d6bc7d22e5e31603e2f0a918a6f160aece1
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.