diff for duplicates of <20757797.djuaztrzGE@phil> diff --git a/a/1.txt b/N1/1.txt index 93e9402..b70bc3e 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,41 +1,32 @@ Hi Caesar, Am Freitag, 8. Januar 2016, 17:26:18 schrieb Caesar Wang: -> =E5=9C=A8 2016=E5=B9=B401=E6=9C=8807=E6=97=A5 18:05, Heiko Stuebner =E5= -=86=99=E9=81=93: +> 在 2016年01月07日 18:05, Heiko Stuebner 写道: > > Am Donnerstag, 7. Januar 2016, 16:25:47 schrieb Caesar Wang: -> >> SCLk_I2S_OUT is the noc bus clock for i2s module, this clock is us= -ed by +> >> SCLk_I2S_OUT is the noc bus clock for i2s module, this clock is used by > >> extra codecs. -> >>=20 +> >> > >> Due to it shouldn't belong to any driver, but we need it enabled, > >> so just mark it as the CLK_IGNORE_UNUSED flag. -> >=20 +> > > > What makes you think it shouldn't belong to any driver? -> >=20 -> > In most schematics I have, i2s_clkout is going to some clock-input = -of +> > +> > In most schematics I have, i2s_clkout is going to some clock-input of > > the -> > audio codec - probably the MCLK input on your rt5616. And while the= - new -> > rt5616 driver does not seem to do clock handling, it should just ha= -ndle +> > audio codec - probably the MCLK input on your rt5616. And while the new +> > rt5616 driver does not seem to do clock handling, it should just handle > > the clock using the normal APIs. ->=20 +> > You are right, that's seem has to find the root cause. -> I'm wonder that the codec/i2s is working in kernel v4.1 patch without= - it. ->=20 -> In general, the MLCK will be handled in i2s driver if the cpu side i= -s +> I'm wonder that the codec/i2s is working in kernel v4.1 patch without it. +> +> In general, the MLCK will be handled in i2s driver if the cpu side is > master. -looking at the rt5616 datasheet, that would be BCLK1 instead I think. T= -his=20 +looking at the rt5616 datasheet, that would be BCLK1 instead I think. This one does differentiate between being master/slave. -The master/sysclk (mclk) is also handled in other drivers in all cases.= -=20 +The master/sysclk (mclk) is also handled in other drivers in all cases. (da7213.c, da7219.c, max98090.c, max98095.c, probably more) diff --git a/a/content_digest b/N1/content_digest index cd2fd8b..eabf9e9 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -21,44 +21,35 @@ "Hi Caesar,\n" "\n" "Am Freitag, 8. Januar 2016, 17:26:18 schrieb Caesar Wang:\n" - "> =E5=9C=A8 2016=E5=B9=B401=E6=9C=8807=E6=97=A5 18:05, Heiko Stuebner =E5=\n" - "=86=99=E9=81=93:\n" + "> \345\234\250 2016\345\271\26401\346\234\21007\346\227\245 18:05, Heiko Stuebner \345\206\231\351\201\223:\n" "> > Am Donnerstag, 7. Januar 2016, 16:25:47 schrieb Caesar Wang:\n" - "> >> SCLk_I2S_OUT is the noc bus clock for i2s module, this clock is us=\n" - "ed by\n" + "> >> SCLk_I2S_OUT is the noc bus clock for i2s module, this clock is used by\n" "> >> extra codecs.\n" - "> >>=20\n" + "> >> \n" "> >> Due to it shouldn't belong to any driver, but we need it enabled,\n" "> >> so just mark it as the CLK_IGNORE_UNUSED flag.\n" - "> >=20\n" + "> > \n" "> > What makes you think it shouldn't belong to any driver?\n" - "> >=20\n" - "> > In most schematics I have, i2s_clkout is going to some clock-input =\n" - "of\n" + "> > \n" + "> > In most schematics I have, i2s_clkout is going to some clock-input of\n" "> > the\n" - "> > audio codec - probably the MCLK input on your rt5616. And while the=\n" - " new\n" - "> > rt5616 driver does not seem to do clock handling, it should just ha=\n" - "ndle\n" + "> > audio codec - probably the MCLK input on your rt5616. And while the new\n" + "> > rt5616 driver does not seem to do clock handling, it should just handle\n" "> > the clock using the normal APIs.\n" - ">=20\n" + "> \n" "> You are right, that's seem has to find the root cause.\n" - "> I'm wonder that the codec/i2s is working in kernel v4.1 patch without=\n" - " it.\n" - ">=20\n" - "> In general, the MLCK will be handled in i2s driver if the cpu side i=\n" - "s\n" + "> I'm wonder that the codec/i2s is working in kernel v4.1 patch without it.\n" + "> \n" + "> In general, the MLCK will be handled in i2s driver if the cpu side is\n" "> master.\n" "\n" - "looking at the rt5616 datasheet, that would be BCLK1 instead I think. T=\n" - "his=20\n" + "looking at the rt5616 datasheet, that would be BCLK1 instead I think. This \n" "one does differentiate between being master/slave.\n" "\n" - "The master/sysclk (mclk) is also handled in other drivers in all cases.=\n" - "=20\n" + "The master/sysclk (mclk) is also handled in other drivers in all cases. \n" "(da7213.c, da7219.c, max98090.c, max98095.c, probably more)\n" "\n" "\n" Heiko -23aa6d2034b711568edabbbd2affd6b3d6832879a923b13aaa2e72121e8833cb +ed613b5f4d1e34d2176255004374d2d7b86d9bc369da2722329f34e541131a7b
diff --git a/a/1.txt b/N2/1.txt index 93e9402..400d90b 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,41 +1,32 @@ Hi Caesar, Am Freitag, 8. Januar 2016, 17:26:18 schrieb Caesar Wang: -> =E5=9C=A8 2016=E5=B9=B401=E6=9C=8807=E6=97=A5 18:05, Heiko Stuebner =E5= -=86=99=E9=81=93: +> ? 2016?01?07? 18:05, Heiko Stuebner ??: > > Am Donnerstag, 7. Januar 2016, 16:25:47 schrieb Caesar Wang: -> >> SCLk_I2S_OUT is the noc bus clock for i2s module, this clock is us= -ed by +> >> SCLk_I2S_OUT is the noc bus clock for i2s module, this clock is used by > >> extra codecs. -> >>=20 +> >> > >> Due to it shouldn't belong to any driver, but we need it enabled, > >> so just mark it as the CLK_IGNORE_UNUSED flag. -> >=20 +> > > > What makes you think it shouldn't belong to any driver? -> >=20 -> > In most schematics I have, i2s_clkout is going to some clock-input = -of +> > +> > In most schematics I have, i2s_clkout is going to some clock-input of > > the -> > audio codec - probably the MCLK input on your rt5616. And while the= - new -> > rt5616 driver does not seem to do clock handling, it should just ha= -ndle +> > audio codec - probably the MCLK input on your rt5616. And while the new +> > rt5616 driver does not seem to do clock handling, it should just handle > > the clock using the normal APIs. ->=20 +> > You are right, that's seem has to find the root cause. -> I'm wonder that the codec/i2s is working in kernel v4.1 patch without= - it. ->=20 -> In general, the MLCK will be handled in i2s driver if the cpu side i= -s +> I'm wonder that the codec/i2s is working in kernel v4.1 patch without it. +> +> In general, the MLCK will be handled in i2s driver if the cpu side is > master. -looking at the rt5616 datasheet, that would be BCLK1 instead I think. T= -his=20 +looking at the rt5616 datasheet, that would be BCLK1 instead I think. This one does differentiate between being master/slave. -The master/sysclk (mclk) is also handled in other drivers in all cases.= -=20 +The master/sysclk (mclk) is also handled in other drivers in all cases. (da7213.c, da7219.c, max98090.c, max98095.c, probably more) diff --git a/a/content_digest b/N2/content_digest index cd2fd8b..86781be 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,64 +1,44 @@ "ref\01452155155-16232-1-git-send-email-wxt@rock-chips.com\0" "ref\0290434099.8XFZ9qmNRz@phil\0" "ref\0568F80BA.6060209@gmail.com\0" - "From\0Heiko Stuebner <heiko@sntech.de>\0" - "Subject\0Re: [PATCH v2 04/12] clk: rockchip: rk3036: enable the CLK_IGNORE_UNUSED flag for sclk_i2s_out\0" + "From\0heiko@sntech.de (Heiko Stuebner)\0" + "Subject\0[PATCH v2 04/12] clk: rockchip: rk3036: enable the CLK_IGNORE_UNUSED flag for sclk_i2s_out\0" "Date\0Fri, 08 Jan 2016 10:46:26 +0100\0" - "To\0Caesar Wang <caesar.upstream@gmail.com>\0" - "Cc\0Caesar Wang <wxt@rock-chips.com>" - Ulf Hansson <ulf.hansson@linaro.org> - Michael Turquette <mturquette@baylibre.com> - Stephen Boyd <sboyd@codeaurora.org> - linux-kernel@vger.kernel.org - linux-rockchip@lists.infradead.org - leecam@google.com - linux-arm-kernel@lists.infradead.org - keescook@google.com - linux-clk@vger.kernel.org - " leozwang@google.com\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "Hi Caesar,\n" "\n" "Am Freitag, 8. Januar 2016, 17:26:18 schrieb Caesar Wang:\n" - "> =E5=9C=A8 2016=E5=B9=B401=E6=9C=8807=E6=97=A5 18:05, Heiko Stuebner =E5=\n" - "=86=99=E9=81=93:\n" + "> ? 2016?01?07? 18:05, Heiko Stuebner ??:\n" "> > Am Donnerstag, 7. Januar 2016, 16:25:47 schrieb Caesar Wang:\n" - "> >> SCLk_I2S_OUT is the noc bus clock for i2s module, this clock is us=\n" - "ed by\n" + "> >> SCLk_I2S_OUT is the noc bus clock for i2s module, this clock is used by\n" "> >> extra codecs.\n" - "> >>=20\n" + "> >> \n" "> >> Due to it shouldn't belong to any driver, but we need it enabled,\n" "> >> so just mark it as the CLK_IGNORE_UNUSED flag.\n" - "> >=20\n" + "> > \n" "> > What makes you think it shouldn't belong to any driver?\n" - "> >=20\n" - "> > In most schematics I have, i2s_clkout is going to some clock-input =\n" - "of\n" + "> > \n" + "> > In most schematics I have, i2s_clkout is going to some clock-input of\n" "> > the\n" - "> > audio codec - probably the MCLK input on your rt5616. And while the=\n" - " new\n" - "> > rt5616 driver does not seem to do clock handling, it should just ha=\n" - "ndle\n" + "> > audio codec - probably the MCLK input on your rt5616. And while the new\n" + "> > rt5616 driver does not seem to do clock handling, it should just handle\n" "> > the clock using the normal APIs.\n" - ">=20\n" + "> \n" "> You are right, that's seem has to find the root cause.\n" - "> I'm wonder that the codec/i2s is working in kernel v4.1 patch without=\n" - " it.\n" - ">=20\n" - "> In general, the MLCK will be handled in i2s driver if the cpu side i=\n" - "s\n" + "> I'm wonder that the codec/i2s is working in kernel v4.1 patch without it.\n" + "> \n" + "> In general, the MLCK will be handled in i2s driver if the cpu side is\n" "> master.\n" "\n" - "looking at the rt5616 datasheet, that would be BCLK1 instead I think. T=\n" - "his=20\n" + "looking at the rt5616 datasheet, that would be BCLK1 instead I think. This \n" "one does differentiate between being master/slave.\n" "\n" - "The master/sysclk (mclk) is also handled in other drivers in all cases.=\n" - "=20\n" + "The master/sysclk (mclk) is also handled in other drivers in all cases. \n" "(da7213.c, da7219.c, max98090.c, max98095.c, probably more)\n" "\n" "\n" Heiko -23aa6d2034b711568edabbbd2affd6b3d6832879a923b13aaa2e72121e8833cb +b6469cbfd52d6beaa003bcc887cdd8b5f8ec156756995458132895c6cfe0a8ba
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.