diff for duplicates of <1797170.duyCyYzgBk@jernej-laptop>
diff --git a/a/1.txt b/N1/1.txt
index a30dd7e..6ef044a 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,17 +1,17 @@
Dne ponedeljek, 25. junij 2018 ob 05:51:41 CEST je Chen-Yu Tsai napisal(a):
> On Mon, Jun 25, 2018 at 3:52 AM, Jernej Škrabec
>
-> <jernej.skrabec@gmail.com> wrote:
+> <jernej.skrabec-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > Dne četrtek, 21. junij 2018 ob 17:35:45 CEST je Jernej Škrabec napisal(a):
> >> Dne četrtek, 21. junij 2018 ob 03:23:27 CEST je Chen-Yu Tsai napisal(a):
> >> > On Thu, Jun 21, 2018 at 3:37 AM, Jernej Škrabec
-> >> > <jernej.skrabec@siol.net>
+> >> > <jernej.skrabec-gGgVlfcn5nU@public.gmane.org>
> >>
> >> wrote:
> >> > > Dne sobota, 16. junij 2018 ob 07:48:38 CEST je Chen-Yu Tsai
napisal(a):
> >> > >> On Sat, Jun 16, 2018 at 1:33 AM, Jernej Škrabec
-> >> > >> <jernej.skrabec@siol.net>
+> >> > >> <jernej.skrabec-gGgVlfcn5nU@public.gmane.org>
> >> > >
> >> > > wrote:
> >> > >> > Dne petek, 15. junij 2018 ob 19:13:17 CEST je Chen-Yu Tsai
@@ -19,7 +19,7 @@ napisal(a):
> > napisal(a):
> >> > >> >> On Sat, Jun 16, 2018 at 12:41 AM, Jernej Škrabec
> >> > >> >>
-> >> > >> >> <jernej.skrabec@siol.net> wrote:
+> >> > >> >> <jernej.skrabec-gGgVlfcn5nU@public.gmane.org> wrote:
> >> > >> >> > Hi,
> >> > >> >> >
> >> > >> >> > Dne petek, 15. junij 2018 ob 10:31:10 CEST je Maxime Ripard
@@ -37,7 +37,7 @@ wrote:
> >> > >> >> >> >
> >> > >> >> >> > Add support for such TCONs.
> >> > >> >> >> >
-> >> > >> >> >> > Signed-off-by: Jernej Skrabec <jernej.skrabec@siol.net>
+> >> > >> >> >> > Signed-off-by: Jernej Skrabec <jernej.skrabec-gGgVlfcn5nU@public.gmane.org>
> >> > >> >> >> > ---
> >> > >> >> >> >
> >> > >> >> >> > drivers/gpu/drm/sun4i/sun4i_tcon.c | 11 +++++++++++
@@ -308,4 +308,12 @@ Maybe quirk can be added that it doesn't set clock rate at all if it is
connected to TVE?
Best regards,
-Jernej
\ No newline at end of file
+Jernej
+
+
+
+
+--
+You received this message because you are subscribed to the Google Groups "linux-sunxi" group.
+To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
+For more options, visit https://groups.google.com/d/optout.
\ No newline at end of file
diff --git a/a/content_digest b/N1/content_digest
index 87e9461..a8a2b53 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -8,31 +8,34 @@
"ref\0CAGb2v67wVpAKk-5kSpnbnBXz7DkHToPa6bwuRBnsfHovw74HVQ\@mail.gmail.com\0"
]
[
- "From\0Jernej \305\240krabec <jernej.skrabec\@gmail.com>\0"
+ "ref\0CAGb2v67wVpAKk-5kSpnbnBXz7DkHToPa6bwuRBnsfHovw74HVQ-JsoAwUIsXosN+BqQ9rBEUg\@public.gmane.org\0"
]
[
- "Subject\0Re: [linux-sunxi] Re: [PATCH v2 11/27] drm/sun4i: tcon: Add support for tcon-top gate\0"
+ "From\0Jernej \305\240krabec <jernej.skrabec-Re5JQEeQqe8AvxtiuMwx3w\@public.gmane.org>\0"
+]
+[
+ "Subject\0Re: Re: [PATCH v2 11/27] drm/sun4i: tcon: Add support for tcon-top gate\0"
]
[
"Date\0Mon, 25 Jun 2018 09:58:57 +0200\0"
]
[
- "To\0linux-sunxi\@googlegroups.com",
- " wens\@csie.org\0"
+ "To\0linux-sunxi-/JYPxA39Uh5TLH3MbocFFw\@public.gmane.org",
+ " wens-jdAy2FN1RRM\@public.gmane.org\0"
]
[
- "Cc\0Maxime Ripard <maxime.ripard\@bootlin.com>",
- " Rob Herring <robh+dt\@kernel.org>",
- " David Airlie <airlied\@linux.ie>",
- " Gustavo Padovan <gustavo\@padovan.org>",
- " Maarten Lankhorst <maarten.lankhorst\@linux.intel.com>",
- " Sean Paul <seanpaul\@chromium.org>",
- " Mark Rutland <mark.rutland\@arm.com>",
- " dri-devel <dri-devel\@lists.freedesktop.org>",
- " devicetree <devicetree\@vger.kernel.org>",
- " linux-arm-kernel <linux-arm-kernel\@lists.infradead.org>",
- " linux-kernel <linux-kernel\@vger.kernel.org>",
- " linux-clk <linux-clk\@vger.kernel.org>\0"
+ "Cc\0Maxime Ripard <maxime.ripard-LDxbnhwyfcJBDgjK7y7TUQ\@public.gmane.org>",
+ " Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A\@public.gmane.org>",
+ " David Airlie <airlied-cv59FeDIM0c\@public.gmane.org>",
+ " Gustavo Padovan <gustavo-THi1TnShQwVAfugRpC6u6w\@public.gmane.org>",
+ " Maarten Lankhorst <maarten.lankhorst-VuQAYsv1563Yd54FQh9/CA\@public.gmane.org>",
+ " Sean Paul <seanpaul-F7+t8E8rja9g9hUCZPvPmw\@public.gmane.org>",
+ " Mark Rutland <mark.rutland-5wv7dgnIgG8\@public.gmane.org>",
+ " dri-devel <dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW\@public.gmane.org>",
+ " devicetree <devicetree-u79uwXL29TY76Z2rM5mHXA\@public.gmane.org>",
+ " linux-arm-kernel <linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r\@public.gmane.org>",
+ " linux-kernel <linux-kernel-u79uwXL29TY76Z2rM5mHXA\@public.gmane.org>",
+ " linux-clk <linux-clk-u79uwXL29TY76Z2rM5mHXA\@public.gmane.org>\0"
]
[
"\0000:1\0"
@@ -44,17 +47,17 @@
"Dne ponedeljek, 25. junij 2018 ob 05:51:41 CEST je Chen-Yu Tsai napisal(a):\n",
"> On Mon, Jun 25, 2018 at 3:52 AM, Jernej \305\240krabec\n",
"> \n",
- "> <jernej.skrabec\@gmail.com> wrote:\n",
+ "> <jernej.skrabec-Re5JQEeQqe8AvxtiuMwx3w\@public.gmane.org> wrote:\n",
"> > Dne \304\215etrtek, 21. junij 2018 ob 17:35:45 CEST je Jernej \305\240krabec napisal(a):\n",
"> >> Dne \304\215etrtek, 21. junij 2018 ob 03:23:27 CEST je Chen-Yu Tsai napisal(a):\n",
"> >> > On Thu, Jun 21, 2018 at 3:37 AM, Jernej \305\240krabec\n",
- "> >> > <jernej.skrabec\@siol.net>\n",
+ "> >> > <jernej.skrabec-gGgVlfcn5nU\@public.gmane.org>\n",
"> >> \n",
"> >> wrote:\n",
"> >> > > Dne sobota, 16. junij 2018 ob 07:48:38 CEST je Chen-Yu Tsai \n",
"napisal(a):\n",
"> >> > >> On Sat, Jun 16, 2018 at 1:33 AM, Jernej \305\240krabec\n",
- "> >> > >> <jernej.skrabec\@siol.net>\n",
+ "> >> > >> <jernej.skrabec-gGgVlfcn5nU\@public.gmane.org>\n",
"> >> > > \n",
"> >> > > wrote:\n",
"> >> > >> > Dne petek, 15. junij 2018 ob 19:13:17 CEST je Chen-Yu Tsai\n",
@@ -62,7 +65,7 @@
"> > napisal(a):\n",
"> >> > >> >> On Sat, Jun 16, 2018 at 12:41 AM, Jernej \305\240krabec\n",
"> >> > >> >> \n",
- "> >> > >> >> <jernej.skrabec\@siol.net> wrote:\n",
+ "> >> > >> >> <jernej.skrabec-gGgVlfcn5nU\@public.gmane.org> wrote:\n",
"> >> > >> >> > Hi,\n",
"> >> > >> >> > \n",
"> >> > >> >> > Dne petek, 15. junij 2018 ob 10:31:10 CEST je Maxime Ripard\n",
@@ -80,7 +83,7 @@
"> >> > >> >> >> > \n",
"> >> > >> >> >> > Add support for such TCONs.\n",
"> >> > >> >> >> > \n",
- "> >> > >> >> >> > Signed-off-by: Jernej Skrabec <jernej.skrabec\@siol.net>\n",
+ "> >> > >> >> >> > Signed-off-by: Jernej Skrabec <jernej.skrabec-gGgVlfcn5nU\@public.gmane.org>\n",
"> >> > >> >> >> > ---\n",
"> >> > >> >> >> > \n",
"> >> > >> >> >> > drivers/gpu/drm/sun4i/sun4i_tcon.c | 11 +++++++++++\n",
@@ -351,7 +354,15 @@
"connected to TVE?\n",
"\n",
"Best regards,\n",
- "Jernej"
+ "Jernej\n",
+ "\n",
+ "\n",
+ "\n",
+ "\n",
+ "-- \n",
+ "You received this message because you are subscribed to the Google Groups \"linux-sunxi\" group.\n",
+ "To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0\@public.gmane.org\n",
+ "For more options, visit https://groups.google.com/d/optout."
]
-d3971958807ed87b5397fffb800c693be0852750d4912e8d633c1a0df93f2aca
+ad54618d79970ebf916b3e97fa840ee861e38a213906feccfb30fc627e85324f
diff --git a/a/1.txt b/N2/1.txt
index a30dd7e..2b7b5f7 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -1,49 +1,51 @@
Dne ponedeljek, 25. junij 2018 ob 05:51:41 CEST je Chen-Yu Tsai napisal(a):
-> On Mon, Jun 25, 2018 at 3:52 AM, Jernej Škrabec
->
+> On Mon, Jun 25, 2018 at 3:52 AM, Jernej =C5=A0krabec
+>=20
> <jernej.skrabec@gmail.com> wrote:
-> > Dne četrtek, 21. junij 2018 ob 17:35:45 CEST je Jernej Škrabec napisal(a):
-> >> Dne četrtek, 21. junij 2018 ob 03:23:27 CEST je Chen-Yu Tsai napisal(a):
-> >> > On Thu, Jun 21, 2018 at 3:37 AM, Jernej Škrabec
+> > Dne =C4=8Detrtek, 21. junij 2018 ob 17:35:45 CEST je Jernej =C5=A0krabe=
+c napisal(a):
+> >> Dne =C4=8Detrtek, 21. junij 2018 ob 03:23:27 CEST je Chen-Yu Tsai napi=
+sal(a):
+> >> > On Thu, Jun 21, 2018 at 3:37 AM, Jernej =C5=A0krabec
> >> > <jernej.skrabec@siol.net>
-> >>
+> >>=20
> >> wrote:
-> >> > > Dne sobota, 16. junij 2018 ob 07:48:38 CEST je Chen-Yu Tsai
+> >> > > Dne sobota, 16. junij 2018 ob 07:48:38 CEST je Chen-Yu Tsai=20
napisal(a):
-> >> > >> On Sat, Jun 16, 2018 at 1:33 AM, Jernej Škrabec
+> >> > >> On Sat, Jun 16, 2018 at 1:33 AM, Jernej =C5=A0krabec
> >> > >> <jernej.skrabec@siol.net>
-> >> > >
+> >> > >=20
> >> > > wrote:
> >> > >> > Dne petek, 15. junij 2018 ob 19:13:17 CEST je Chen-Yu Tsai
-> >
+> >=20
> > napisal(a):
-> >> > >> >> On Sat, Jun 16, 2018 at 12:41 AM, Jernej Škrabec
-> >> > >> >>
+> >> > >> >> On Sat, Jun 16, 2018 at 12:41 AM, Jernej =C5=A0krabec
+> >> > >> >>=20
> >> > >> >> <jernej.skrabec@siol.net> wrote:
> >> > >> >> > Hi,
-> >> > >> >> >
+> >> > >> >> >=20
> >> > >> >> > Dne petek, 15. junij 2018 ob 10:31:10 CEST je Maxime Ripard
-> >>
+> >>=20
> >> napisal(a):
> >> > >> >> >> Hi,
-> >> > >> >> >>
-> >> > >> >> >> On Tue, Jun 12, 2018 at 10:00:20PM +0200, Jernej Skrabec
+> >> > >> >> >>=20
+> >> > >> >> >> On Tue, Jun 12, 2018 at 10:00:20PM +0200, Jernej Skrabec=20
wrote:
> >> > >> >> >> > TV TCONs connected to TCON TOP have to enable additional
> >> > >> >> >> > gate
> >> > >> >> >> > in
> >> > >> >> >> > order
> >> > >> >> >> > to work.
-> >> > >> >> >> >
+> >> > >> >> >> >=20
> >> > >> >> >> > Add support for such TCONs.
-> >> > >> >> >> >
+> >> > >> >> >> >=20
> >> > >> >> >> > Signed-off-by: Jernej Skrabec <jernej.skrabec@siol.net>
> >> > >> >> >> > ---
-> >> > >> >> >> >
+> >> > >> >> >> >=20
> >> > >> >> >> > drivers/gpu/drm/sun4i/sun4i_tcon.c | 11 +++++++++++
> >> > >> >> >> > drivers/gpu/drm/sun4i/sun4i_tcon.h | 4 ++++
> >> > >> >> >> > 2 files changed, 15 insertions(+)
-> >> > >> >> >> >
+> >> > >> >> >> >=20
> >> > >> >> >> > diff --git a/drivers/gpu/drm/sun4i/sun4i_tcon.c
> >> > >> >> >> > b/drivers/gpu/drm/sun4i/sun4i_tcon.c index
> >> > >> >> >> > 08747fc3ee71..0afb5a94a414
@@ -54,18 +56,20 @@ wrote:
> >> > >> >> >> > sun4i_tcon_init_clocks(struct
> >> > >> >> >> > device
> >> > >> >> >> > *dev,
-> >> > >> >> >> >
+> >> > >> >> >> >=20
> >> > >> >> >> > dev_err(dev, "Couldn't get the TCON bus
> >> > >> >> >> > clock\n");
> >> > >> >> >> > return PTR_ERR(tcon->clk);
-> >> > >> >> >> >
+> >> > >> >> >> > =20
> >> > >> >> >> > }
-> >> > >> >> >> >
+> >> > >> >> >> >=20
> >> > >> >> >> > +
> >> > >> >> >> > + if (tcon->quirks->has_tcon_top_gate) {
-> >> > >> >> >> > + tcon->top_clk = devm_clk_get(dev, "tcon-top");
+> >> > >> >> >> > + tcon->top_clk =3D devm_clk_get(dev, "tcon-top=
+");
> >> > >> >> >> > + if (IS_ERR(tcon->top_clk)) {
-> >> > >> >> >> > + dev_err(dev, "Couldn't get the TCON TOP
+> >> > >> >> >> > + dev_err(dev, "Couldn't get the TCON T=
+OP
> >> > >> >> >> > bus
> >> > >> >> >> > clock\n");
> >> > >> >> >> > + return PTR_ERR(tcon->top_clk);
@@ -73,25 +77,29 @@ wrote:
> >> > >> >> >> > + clk_prepare_enable(tcon->top_clk);
> >> > >> >> >> > + }
> >> > >> >> >> > +
-> >> > >> >> >>
+> >> > >> >> >>=20
> >> > >> >> >> Is it required for the TCON itself to operate, or does the
> >> > >> >> >> TCON
-> >> > >> >> >> requires the TCON TOP, which in turn requires that clock to be
+> >> > >> >> >> requires the TCON TOP, which in turn requires that clock to=
+ be
> >> > >> >> >> functional?
-> >> > >> >> >>
+> >> > >> >> >>=20
> >> > >> >> >> I find it quite odd to have a clock that isn't meant for a
> >> > >> >> >> particular
-> >> > >> >> >> device to actually be wired to another device. I'm not saying
+> >> > >> >> >> device to actually be wired to another device. I'm not sayi=
+ng
> >> > >> >> >> this
> >> > >> >> >> isn't the case, but it would be a first.
-> >> > >> >> >
-> >> > >> >> > Documentation doesn't say much about that gate. I did few tests
+> >> > >> >> >=20
+> >> > >> >> > Documentation doesn't say much about that gate. I did few te=
+sts
> >> > >> >> > and
> >> > >> >> > TCON
-> >> > >> >> > registers can be read and written even if TCON TOP TV TCON gate
+> >> > >> >> > registers can be read and written even if TCON TOP TV TCON g=
+ate
> >> > >> >> > is
> >> > >> >> > disabled. However, there is no image, as expected.
-> >> > >> >>
+> >> > >> >>=20
> >> > >> >> The R40 manual does include it in the diagram, on page 504.
> >> > >> >> There's
> >> > >> >> also
@@ -106,8 +114,9 @@ wrote:
> >> > >> >> module
> >> > >> >> or
> >> > >> >> channel clock, strangely routed.
-> >> > >> >>
-> >> > >> >> > More interestingly, I enabled test pattern directly in TCON to
+> >> > >> >>=20
+> >> > >> >> > More interestingly, I enabled test pattern directly in TCON =
+to
> >> > >> >> > eliminate
> >> > >> >> > influence of the mixer. As soon as I disabled that gate, test
> >> > >> >> > pattern
@@ -115,19 +124,22 @@ wrote:
> >> > >> >> > HDMI screen was gone, which suggest that this gate influences
> >> > >> >> > something
> >> > >> >> > inside TCON.
-> >> > >> >> >
-> >> > >> >> > Another test I did was that I moved enable/disable gate code to
+> >> > >> >> >=20
+> >> > >> >> > Another test I did was that I moved enable/disable gate code=
+ to
> >> > >> >> > sun4i_tcon_channel_set_status() and it worked just as well.
-> >> > >> >> >
+> >> > >> >> >=20
> >> > >> >> > I'll ask AW engineer what that gate actually does, but from
> >> > >> >> > what I
> >> > >> >> > saw,
> >> > >> >> > I
-> >> > >> >> > would say that most appropriate location to enable/disable TCON
+> >> > >> >> > would say that most appropriate location to enable/disable T=
+CON
> >> > >> >> > TOP
> >> > >> >> > TV
> >> > >> >> > TCON
-> >> > >> >> > gate is TCON driver. Alternatively, TCON TOP driver could check
+> >> > >> >> > gate is TCON driver. Alternatively, TCON TOP driver could ch=
+eck
> >> > >> >> > if
> >> > >> >> > any
> >> > >> >> > TV
@@ -135,14 +147,16 @@ wrote:
> >> > >> >> > doesn't
> >> > >> >> > sound
> >> > >> >> > right to me for some reason.
-> >> > >> >>
-> >> > >> >> If what I said above it true, then yes, the appropriate location
+> >> > >> >>=20
+> >> > >> >> If what I said above it true, then yes, the appropriate locati=
+on
> >> > >> >> to
> >> > >> >> enable
> >> > >> >> it is the TCON driver, but moreover, the representation of the
> >> > >> >> clock
> >> > >> >> tree
-> >> > >> >> should be fixed such that the TCON takes the clock from the TCON
+> >> > >> >> should be fixed such that the TCON takes the clock from the TC=
+ON
> >> > >> >> TOP
> >> > >> >> as
> >> > >> >> its
@@ -150,136 +164,146 @@ wrote:
> >> > >> >> patch,
> >> > >> >> but
> >> > >> >> you'd add another for all the clock routing.
-> >> > >> >
+> >> > >> >=20
> >> > >> > Can you be more specific? I not sure what you mean here.
-> >> > >>
+> >> > >>=20
> >> > >> For clock related properties in the device tree:
-> >> > >>
+> >> > >>=20
> >> > >> &tcon_top {
-> >> > >>
-> >> > >> clocks = <&ccu CLK_BUS_TCON_TOP>,
-> >> > >>
+> >> > >>=20
+> >> > >> clocks =3D <&ccu CLK_BUS_TCON_TOP>,
+> >> > >> =20
> >> > >> <&ccu CLK_TCON_TV0>,
> >> > >> <&tve0>,
> >> > >> <&ccu CLK_TCON_TV1>,
> >> > >> <&tve1>;
-> >> > >>
-> >> > >> clock-names = "bus", "tcon-tv0", "tve0", "tcon-tv1", "tve1";
-> >> > >> clock-output-names = "tcon-top-tv0", "tcon-top-tv1";
-> >> > >>
+> >> > >> =20
+> >> > >> clock-names =3D "bus", "tcon-tv0", "tve0", "tcon-tv1", "tve1";
+> >> > >> clock-output-names =3D "tcon-top-tv0", "tcon-top-tv1";
+> >> > >>=20
> >> > >> };
-> >> > >>
+> >> > >>=20
> >> > >> &tcon_tv0 {
-> >> > >>
-> >> > >> clocks = <&ccu CLK_BUS_TCON_TV0>, <&tcon_top 0>'
-> >> > >> clock-names = "ahb", "tcon-ch1";
-> >> > >>
+> >> > >>=20
+> >> > >> clocks =3D <&ccu CLK_BUS_TCON_TV0>, <&tcon_top 0>'
+> >> > >> clock-names =3D "ahb", "tcon-ch1";
+> >> > >>=20
> >> > >> };
-> >> > >>
+> >> > >>=20
> >> > >> A diagram would look like:
> >> > >> | This part is TCON TOP |
-> >> > >>
+> >> > >> =20
> >> > >> v v
-> >> > >>
+> >> > >>=20
> >> > >> CCU CLK_TCON_TV0 --|----\ |
-> >> > >>
+> >> > >>=20
> >> > >> | mux ---- gate ----|-- TCON_TV0
-> >> > >>
+> >> > >>=20
> >> > >> TVE0 --------------|----/ |
-> >> > >>
+> >> > >>=20
> >> > >> And the same goes for TCON_TV1 and TVE1.
-> >> > >>
-> >> > >> The user manual is a bit lacking on how TVE outputs a clock though.
-> >> > >
+> >> > >>=20
+> >> > >> The user manual is a bit lacking on how TVE outputs a clock thoug=
+h.
+> >> > >=20
> >> > > I didn't yet received any response on HW details from AW till now,
> >> > > but I
> >> > > would like to post new version of patches soon.
-> >> > >
+> >> > >=20
> >> > > While chaining like you described could be implemented easily, I
> >> > > don't
> >> > > think it really represents HW as it is. Tests showed that these two
> >> > > clocks are independent, otherwise register writes/reads wouldn't be
-> >> > > possible with tcon- top gate disabled. I chose tcon-top bus clock as
+> >> > > possible with tcon- top gate disabled. I chose tcon-top bus clock =
+as
> >> > > a
> >> > > parent becase if it is not enabled, it simply won't work.
-> >> >
+> >> >=20
> >> > AFAIK with the TCONs, even when the TCON channel clock (not the bus
> >> > clock)
> >> > is disabled, register accesses still work.
-> >>
+> >>=20
> >> You're right, I just tested that.
-> >>
+> >>=20
> >> > I'm saying that the TCON TOP
> >> > gate is downstream from the TCON channel clock in the CCU. These are
> >> > not
> >> > related to the TCON bus clock in the CCU, which affects register
> >> > access.
-> >> >
+> >> >=20
> >> > Did Allwinner provide any information regarding the hierarchy of the
> >> > clocks?
-> >>
+> >>=20
> >> No reponse for now.
-> >>
-> >> > > However, if everyone feels chaining is the best way to implement it,
+> >>=20
+> >> > > However, if everyone feels chaining is the best way to implement i=
+t,
> >> > > I'll
> >> > > do it.
-> >> >
-> >> > I would like to get it right and match actual hardware. My proposal is
+> >> >=20
+> >> > I would like to get it right and match actual hardware. My proposal =
+is
> >> > based on my understanding from the diagrams in the user manual.
-> >>
+> >>=20
> >> So for now, your explanation is the most reasonable. Should we go ahead
> >> and
> >> implement your idea?
-> >>
+> >>=20
> >> Please note that H6 has TCON-TOP too, but it has only one LCD TCON and
> >> one
> >> TV TCON instead of two of each kind. That means we will have hole in
> >> indices (tcon_lcd0 is 1, tcon_tv0 is 3, which is aligned with R40) and
> >> different TCON- TOP binding (no tcon_tv1 channel clock), but setup is
> >> exactly the same.
-> >
-> > I just noticed issue with this proposal. If we have following clock chain
+> >=20
+> > I just noticed issue with this proposal. If we have following clock cha=
+in
> > for HDMI, everythings is ok:
-> >
+> >=20
> > TCON-TV0 -> TCON-TOP-TV0
-> >
+> >=20
> > TCON TV sets TCON-TOP-TV0 clock rate, which in turn sets TCON-TV0 clock
> > and
> > everything works.
-> >
+> >=20
> > However, when TVE will be configured, it would look like this:
-> >
+> >=20
> > TVE0 -> TCON-TOP-TV0
-> >
+> >=20
> > TVE driver will set TVE0 clock to 216 MHz and TCON TV would set
> > TCON-TOP-TV0 rate which in turn sets TVE0 clock to something like 13.5
> > MHz (or whatever is the right clock rate for PAL and NTSC). As you can
> > see, same clock is set to two different rates by two different drivers.
-> >
-> > It *might* still work, since encoders set clock rate after TCON (at least
+> >=20
+> > It *might* still work, since encoders set clock rate after TCON (at lea=
+st
> > that is my experience for HDMI pipeline), but that is still wrong.
-> >
+> >=20
> > To overcome above issue, I would stick to original proposal with
> > additional
-> > clock specified in TCON TV DT node. That way TCON driver would always set
-> > clock rate to TCON-TV0 clock. If TVE0 is enabled, TCON wouldn't interfere
+> > clock specified in TCON TV DT node. That way TCON driver would always s=
+et
+> > clock rate to TCON-TV0 clock. If TVE0 is enabled, TCON wouldn't interfe=
+re
> > with setting clock rate, because TCON-TV0 clock would be decoupled in
> > TCON-TOP mux.
-> >
+> >=20
> > What do you think?
->
-> I think this is the wrong representation, and worse, you are trying to work
+>=20
+> I think this is the wrong representation, and worse, you are trying to wo=
+rk
> around software issues with it.
->
+>=20
> So to confirm some details, the TVE expects 216 MHz clock, and it expects
> the TCON to run and output data at 216 MHz as well. Is that correct?
-Yes, from my understanding. 216 MHz is correct at least for PAL and NTSC, e.g.
+Yes, from my understanding. 216 MHz is correct at least for PAL and NTSC, e=
+=2Eg.=20
TV mode. TVE on R40 is also capable of RGB mode (VGA connector).
->
+>=20
> Would any settings for the TCON differ between when HDMI or TVE is used?
->
+>=20
Apart of clock, no, other settings would be the same.
@@ -290,21 +314,26 @@ Please check this table in BSP:
https://github.com/BPI-SINOVOIP/BPI-M2U-bsp/blob/master/linux-sunxi/drivers/
video/sunxi/disp2/tv/drv_tv.c#L24
-216 MHz is applicable for low resolution, interlaced modes. Modes like 1080P,
+216 MHz is applicable for low resolution, interlaced modes. Modes like 1080=
+P,=20
1080I have expected standard timing.
->
-> I think these kinds of quirks should be handled in the software, instead of
+>=20
+> I think these kinds of quirks should be handled in the software, instead =
+of
> being papered over.
-Ok, that works for me too. I would just like to have such design that would
+Ok, that works for me too. I would just like to have such design that would=
+=20
later allow implementing TVE driver without much issues.
-BTW, H3 TV TCON which is connected to TVE doesn't have TCON-TV channel clock
-at all, since it is controlled with TVE clock (same case as it would be here,
+BTW, H3 TV TCON which is connected to TVE doesn't have TCON-TV channel cloc=
+k=20
+at all, since it is controlled with TVE clock (same case as it would be her=
+e,=20
if TCON TOP mux is switched to TVE clock source).
-Maybe quirk can be added that it doesn't set clock rate at all if it is
+Maybe quirk can be added that it doesn't set clock rate at all if it is=20
connected to TVE?
Best regards,
diff --git a/a/content_digest b/N2/content_digest
index 87e9461..2ae81da 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -42,51 +42,53 @@
]
[
"Dne ponedeljek, 25. junij 2018 ob 05:51:41 CEST je Chen-Yu Tsai napisal(a):\n",
- "> On Mon, Jun 25, 2018 at 3:52 AM, Jernej \305\240krabec\n",
- "> \n",
+ "> On Mon, Jun 25, 2018 at 3:52 AM, Jernej =C5=A0krabec\n",
+ ">=20\n",
"> <jernej.skrabec\@gmail.com> wrote:\n",
- "> > Dne \304\215etrtek, 21. junij 2018 ob 17:35:45 CEST je Jernej \305\240krabec napisal(a):\n",
- "> >> Dne \304\215etrtek, 21. junij 2018 ob 03:23:27 CEST je Chen-Yu Tsai napisal(a):\n",
- "> >> > On Thu, Jun 21, 2018 at 3:37 AM, Jernej \305\240krabec\n",
+ "> > Dne =C4=8Detrtek, 21. junij 2018 ob 17:35:45 CEST je Jernej =C5=A0krabe=\n",
+ "c napisal(a):\n",
+ "> >> Dne =C4=8Detrtek, 21. junij 2018 ob 03:23:27 CEST je Chen-Yu Tsai napi=\n",
+ "sal(a):\n",
+ "> >> > On Thu, Jun 21, 2018 at 3:37 AM, Jernej =C5=A0krabec\n",
"> >> > <jernej.skrabec\@siol.net>\n",
- "> >> \n",
+ "> >>=20\n",
"> >> wrote:\n",
- "> >> > > Dne sobota, 16. junij 2018 ob 07:48:38 CEST je Chen-Yu Tsai \n",
+ "> >> > > Dne sobota, 16. junij 2018 ob 07:48:38 CEST je Chen-Yu Tsai=20\n",
"napisal(a):\n",
- "> >> > >> On Sat, Jun 16, 2018 at 1:33 AM, Jernej \305\240krabec\n",
+ "> >> > >> On Sat, Jun 16, 2018 at 1:33 AM, Jernej =C5=A0krabec\n",
"> >> > >> <jernej.skrabec\@siol.net>\n",
- "> >> > > \n",
+ "> >> > >=20\n",
"> >> > > wrote:\n",
"> >> > >> > Dne petek, 15. junij 2018 ob 19:13:17 CEST je Chen-Yu Tsai\n",
- "> > \n",
+ "> >=20\n",
"> > napisal(a):\n",
- "> >> > >> >> On Sat, Jun 16, 2018 at 12:41 AM, Jernej \305\240krabec\n",
- "> >> > >> >> \n",
+ "> >> > >> >> On Sat, Jun 16, 2018 at 12:41 AM, Jernej =C5=A0krabec\n",
+ "> >> > >> >>=20\n",
"> >> > >> >> <jernej.skrabec\@siol.net> wrote:\n",
"> >> > >> >> > Hi,\n",
- "> >> > >> >> > \n",
+ "> >> > >> >> >=20\n",
"> >> > >> >> > Dne petek, 15. junij 2018 ob 10:31:10 CEST je Maxime Ripard\n",
- "> >> \n",
+ "> >>=20\n",
"> >> napisal(a):\n",
"> >> > >> >> >> Hi,\n",
- "> >> > >> >> >> \n",
- "> >> > >> >> >> On Tue, Jun 12, 2018 at 10:00:20PM +0200, Jernej Skrabec \n",
+ "> >> > >> >> >>=20\n",
+ "> >> > >> >> >> On Tue, Jun 12, 2018 at 10:00:20PM +0200, Jernej Skrabec=20\n",
"wrote:\n",
"> >> > >> >> >> > TV TCONs connected to TCON TOP have to enable additional\n",
"> >> > >> >> >> > gate\n",
"> >> > >> >> >> > in\n",
"> >> > >> >> >> > order\n",
"> >> > >> >> >> > to work.\n",
- "> >> > >> >> >> > \n",
+ "> >> > >> >> >> >=20\n",
"> >> > >> >> >> > Add support for such TCONs.\n",
- "> >> > >> >> >> > \n",
+ "> >> > >> >> >> >=20\n",
"> >> > >> >> >> > Signed-off-by: Jernej Skrabec <jernej.skrabec\@siol.net>\n",
"> >> > >> >> >> > ---\n",
- "> >> > >> >> >> > \n",
+ "> >> > >> >> >> >=20\n",
"> >> > >> >> >> > drivers/gpu/drm/sun4i/sun4i_tcon.c | 11 +++++++++++\n",
"> >> > >> >> >> > drivers/gpu/drm/sun4i/sun4i_tcon.h | 4 ++++\n",
"> >> > >> >> >> > 2 files changed, 15 insertions(+)\n",
- "> >> > >> >> >> > \n",
+ "> >> > >> >> >> >=20\n",
"> >> > >> >> >> > diff --git a/drivers/gpu/drm/sun4i/sun4i_tcon.c\n",
"> >> > >> >> >> > b/drivers/gpu/drm/sun4i/sun4i_tcon.c index\n",
"> >> > >> >> >> > 08747fc3ee71..0afb5a94a414\n",
@@ -97,18 +99,20 @@
"> >> > >> >> >> > sun4i_tcon_init_clocks(struct\n",
"> >> > >> >> >> > device\n",
"> >> > >> >> >> > *dev,\n",
- "> >> > >> >> >> > \n",
+ "> >> > >> >> >> >=20\n",
"> >> > >> >> >> > dev_err(dev, \"Couldn't get the TCON bus\n",
"> >> > >> >> >> > clock\\n\");\n",
"> >> > >> >> >> > return PTR_ERR(tcon->clk);\n",
- "> >> > >> >> >> > \n",
+ "> >> > >> >> >> > =20\n",
"> >> > >> >> >> > }\n",
- "> >> > >> >> >> > \n",
+ "> >> > >> >> >> >=20\n",
"> >> > >> >> >> > +\n",
"> >> > >> >> >> > + if (tcon->quirks->has_tcon_top_gate) {\n",
- "> >> > >> >> >> > + tcon->top_clk = devm_clk_get(dev, \"tcon-top\");\n",
+ "> >> > >> >> >> > + tcon->top_clk =3D devm_clk_get(dev, \"tcon-top=\n",
+ "\");\n",
"> >> > >> >> >> > + if (IS_ERR(tcon->top_clk)) {\n",
- "> >> > >> >> >> > + dev_err(dev, \"Couldn't get the TCON TOP\n",
+ "> >> > >> >> >> > + dev_err(dev, \"Couldn't get the TCON T=\n",
+ "OP\n",
"> >> > >> >> >> > bus\n",
"> >> > >> >> >> > clock\\n\");\n",
"> >> > >> >> >> > + return PTR_ERR(tcon->top_clk);\n",
@@ -116,25 +120,29 @@
"> >> > >> >> >> > + clk_prepare_enable(tcon->top_clk);\n",
"> >> > >> >> >> > + }\n",
"> >> > >> >> >> > +\n",
- "> >> > >> >> >> \n",
+ "> >> > >> >> >>=20\n",
"> >> > >> >> >> Is it required for the TCON itself to operate, or does the\n",
"> >> > >> >> >> TCON\n",
- "> >> > >> >> >> requires the TCON TOP, which in turn requires that clock to be\n",
+ "> >> > >> >> >> requires the TCON TOP, which in turn requires that clock to=\n",
+ " be\n",
"> >> > >> >> >> functional?\n",
- "> >> > >> >> >> \n",
+ "> >> > >> >> >>=20\n",
"> >> > >> >> >> I find it quite odd to have a clock that isn't meant for a\n",
"> >> > >> >> >> particular\n",
- "> >> > >> >> >> device to actually be wired to another device. I'm not saying\n",
+ "> >> > >> >> >> device to actually be wired to another device. I'm not sayi=\n",
+ "ng\n",
"> >> > >> >> >> this\n",
"> >> > >> >> >> isn't the case, but it would be a first.\n",
- "> >> > >> >> > \n",
- "> >> > >> >> > Documentation doesn't say much about that gate. I did few tests\n",
+ "> >> > >> >> >=20\n",
+ "> >> > >> >> > Documentation doesn't say much about that gate. I did few te=\n",
+ "sts\n",
"> >> > >> >> > and\n",
"> >> > >> >> > TCON\n",
- "> >> > >> >> > registers can be read and written even if TCON TOP TV TCON gate\n",
+ "> >> > >> >> > registers can be read and written even if TCON TOP TV TCON g=\n",
+ "ate\n",
"> >> > >> >> > is\n",
"> >> > >> >> > disabled. However, there is no image, as expected.\n",
- "> >> > >> >> \n",
+ "> >> > >> >>=20\n",
"> >> > >> >> The R40 manual does include it in the diagram, on page 504.\n",
"> >> > >> >> There's\n",
"> >> > >> >> also\n",
@@ -149,8 +157,9 @@
"> >> > >> >> module\n",
"> >> > >> >> or\n",
"> >> > >> >> channel clock, strangely routed.\n",
- "> >> > >> >> \n",
- "> >> > >> >> > More interestingly, I enabled test pattern directly in TCON to\n",
+ "> >> > >> >>=20\n",
+ "> >> > >> >> > More interestingly, I enabled test pattern directly in TCON =\n",
+ "to\n",
"> >> > >> >> > eliminate\n",
"> >> > >> >> > influence of the mixer. As soon as I disabled that gate, test\n",
"> >> > >> >> > pattern\n",
@@ -158,19 +167,22 @@
"> >> > >> >> > HDMI screen was gone, which suggest that this gate influences\n",
"> >> > >> >> > something\n",
"> >> > >> >> > inside TCON.\n",
- "> >> > >> >> > \n",
- "> >> > >> >> > Another test I did was that I moved enable/disable gate code to\n",
+ "> >> > >> >> >=20\n",
+ "> >> > >> >> > Another test I did was that I moved enable/disable gate code=\n",
+ " to\n",
"> >> > >> >> > sun4i_tcon_channel_set_status() and it worked just as well.\n",
- "> >> > >> >> > \n",
+ "> >> > >> >> >=20\n",
"> >> > >> >> > I'll ask AW engineer what that gate actually does, but from\n",
"> >> > >> >> > what I\n",
"> >> > >> >> > saw,\n",
"> >> > >> >> > I\n",
- "> >> > >> >> > would say that most appropriate location to enable/disable TCON\n",
+ "> >> > >> >> > would say that most appropriate location to enable/disable T=\n",
+ "CON\n",
"> >> > >> >> > TOP\n",
"> >> > >> >> > TV\n",
"> >> > >> >> > TCON\n",
- "> >> > >> >> > gate is TCON driver. Alternatively, TCON TOP driver could check\n",
+ "> >> > >> >> > gate is TCON driver. Alternatively, TCON TOP driver could ch=\n",
+ "eck\n",
"> >> > >> >> > if\n",
"> >> > >> >> > any\n",
"> >> > >> >> > TV\n",
@@ -178,14 +190,16 @@
"> >> > >> >> > doesn't\n",
"> >> > >> >> > sound\n",
"> >> > >> >> > right to me for some reason.\n",
- "> >> > >> >> \n",
- "> >> > >> >> If what I said above it true, then yes, the appropriate location\n",
+ "> >> > >> >>=20\n",
+ "> >> > >> >> If what I said above it true, then yes, the appropriate locati=\n",
+ "on\n",
"> >> > >> >> to\n",
"> >> > >> >> enable\n",
"> >> > >> >> it is the TCON driver, but moreover, the representation of the\n",
"> >> > >> >> clock\n",
"> >> > >> >> tree\n",
- "> >> > >> >> should be fixed such that the TCON takes the clock from the TCON\n",
+ "> >> > >> >> should be fixed such that the TCON takes the clock from the TC=\n",
+ "ON\n",
"> >> > >> >> TOP\n",
"> >> > >> >> as\n",
"> >> > >> >> its\n",
@@ -193,136 +207,146 @@
"> >> > >> >> patch,\n",
"> >> > >> >> but\n",
"> >> > >> >> you'd add another for all the clock routing.\n",
- "> >> > >> > \n",
+ "> >> > >> >=20\n",
"> >> > >> > Can you be more specific? I not sure what you mean here.\n",
- "> >> > >> \n",
+ "> >> > >>=20\n",
"> >> > >> For clock related properties in the device tree:\n",
- "> >> > >> \n",
+ "> >> > >>=20\n",
"> >> > >> &tcon_top {\n",
- "> >> > >> \n",
- "> >> > >> clocks = <&ccu CLK_BUS_TCON_TOP>,\n",
- "> >> > >> \n",
+ "> >> > >>=20\n",
+ "> >> > >> clocks =3D <&ccu CLK_BUS_TCON_TOP>,\n",
+ "> >> > >> =20\n",
"> >> > >> <&ccu CLK_TCON_TV0>,\n",
"> >> > >> <&tve0>,\n",
"> >> > >> <&ccu CLK_TCON_TV1>,\n",
"> >> > >> <&tve1>;\n",
- "> >> > >> \n",
- "> >> > >> clock-names = \"bus\", \"tcon-tv0\", \"tve0\", \"tcon-tv1\", \"tve1\";\n",
- "> >> > >> clock-output-names = \"tcon-top-tv0\", \"tcon-top-tv1\";\n",
- "> >> > >> \n",
+ "> >> > >> =20\n",
+ "> >> > >> clock-names =3D \"bus\", \"tcon-tv0\", \"tve0\", \"tcon-tv1\", \"tve1\";\n",
+ "> >> > >> clock-output-names =3D \"tcon-top-tv0\", \"tcon-top-tv1\";\n",
+ "> >> > >>=20\n",
"> >> > >> };\n",
- "> >> > >> \n",
+ "> >> > >>=20\n",
"> >> > >> &tcon_tv0 {\n",
- "> >> > >> \n",
- "> >> > >> clocks = <&ccu CLK_BUS_TCON_TV0>, <&tcon_top 0>'\n",
- "> >> > >> clock-names = \"ahb\", \"tcon-ch1\";\n",
- "> >> > >> \n",
+ "> >> > >>=20\n",
+ "> >> > >> clocks =3D <&ccu CLK_BUS_TCON_TV0>, <&tcon_top 0>'\n",
+ "> >> > >> clock-names =3D \"ahb\", \"tcon-ch1\";\n",
+ "> >> > >>=20\n",
"> >> > >> };\n",
- "> >> > >> \n",
+ "> >> > >>=20\n",
"> >> > >> A diagram would look like:\n",
"> >> > >> | This part is TCON TOP |\n",
- "> >> > >> \n",
+ "> >> > >> =20\n",
"> >> > >> v v\n",
- "> >> > >> \n",
+ "> >> > >>=20\n",
"> >> > >> CCU CLK_TCON_TV0 --|----\\ |\n",
- "> >> > >> \n",
+ "> >> > >>=20\n",
"> >> > >> | mux ---- gate ----|-- TCON_TV0\n",
- "> >> > >> \n",
+ "> >> > >>=20\n",
"> >> > >> TVE0 --------------|----/ |\n",
- "> >> > >> \n",
+ "> >> > >>=20\n",
"> >> > >> And the same goes for TCON_TV1 and TVE1.\n",
- "> >> > >> \n",
- "> >> > >> The user manual is a bit lacking on how TVE outputs a clock though.\n",
- "> >> > > \n",
+ "> >> > >>=20\n",
+ "> >> > >> The user manual is a bit lacking on how TVE outputs a clock thoug=\n",
+ "h.\n",
+ "> >> > >=20\n",
"> >> > > I didn't yet received any response on HW details from AW till now,\n",
"> >> > > but I\n",
"> >> > > would like to post new version of patches soon.\n",
- "> >> > > \n",
+ "> >> > >=20\n",
"> >> > > While chaining like you described could be implemented easily, I\n",
"> >> > > don't\n",
"> >> > > think it really represents HW as it is. Tests showed that these two\n",
"> >> > > clocks are independent, otherwise register writes/reads wouldn't be\n",
- "> >> > > possible with tcon- top gate disabled. I chose tcon-top bus clock as\n",
+ "> >> > > possible with tcon- top gate disabled. I chose tcon-top bus clock =\n",
+ "as\n",
"> >> > > a\n",
"> >> > > parent becase if it is not enabled, it simply won't work.\n",
- "> >> > \n",
+ "> >> >=20\n",
"> >> > AFAIK with the TCONs, even when the TCON channel clock (not the bus\n",
"> >> > clock)\n",
"> >> > is disabled, register accesses still work.\n",
- "> >> \n",
+ "> >>=20\n",
"> >> You're right, I just tested that.\n",
- "> >> \n",
+ "> >>=20\n",
"> >> > I'm saying that the TCON TOP\n",
"> >> > gate is downstream from the TCON channel clock in the CCU. These are\n",
"> >> > not\n",
"> >> > related to the TCON bus clock in the CCU, which affects register\n",
"> >> > access.\n",
- "> >> > \n",
+ "> >> >=20\n",
"> >> > Did Allwinner provide any information regarding the hierarchy of the\n",
"> >> > clocks?\n",
- "> >> \n",
+ "> >>=20\n",
"> >> No reponse for now.\n",
- "> >> \n",
- "> >> > > However, if everyone feels chaining is the best way to implement it,\n",
+ "> >>=20\n",
+ "> >> > > However, if everyone feels chaining is the best way to implement i=\n",
+ "t,\n",
"> >> > > I'll\n",
"> >> > > do it.\n",
- "> >> > \n",
- "> >> > I would like to get it right and match actual hardware. My proposal is\n",
+ "> >> >=20\n",
+ "> >> > I would like to get it right and match actual hardware. My proposal =\n",
+ "is\n",
"> >> > based on my understanding from the diagrams in the user manual.\n",
- "> >> \n",
+ "> >>=20\n",
"> >> So for now, your explanation is the most reasonable. Should we go ahead\n",
"> >> and\n",
"> >> implement your idea?\n",
- "> >> \n",
+ "> >>=20\n",
"> >> Please note that H6 has TCON-TOP too, but it has only one LCD TCON and\n",
"> >> one\n",
"> >> TV TCON instead of two of each kind. That means we will have hole in\n",
"> >> indices (tcon_lcd0 is 1, tcon_tv0 is 3, which is aligned with R40) and\n",
"> >> different TCON- TOP binding (no tcon_tv1 channel clock), but setup is\n",
"> >> exactly the same.\n",
- "> > \n",
- "> > I just noticed issue with this proposal. If we have following clock chain\n",
+ "> >=20\n",
+ "> > I just noticed issue with this proposal. If we have following clock cha=\n",
+ "in\n",
"> > for HDMI, everythings is ok:\n",
- "> > \n",
+ "> >=20\n",
"> > TCON-TV0 -> TCON-TOP-TV0\n",
- "> > \n",
+ "> >=20\n",
"> > TCON TV sets TCON-TOP-TV0 clock rate, which in turn sets TCON-TV0 clock\n",
"> > and\n",
"> > everything works.\n",
- "> > \n",
+ "> >=20\n",
"> > However, when TVE will be configured, it would look like this:\n",
- "> > \n",
+ "> >=20\n",
"> > TVE0 -> TCON-TOP-TV0\n",
- "> > \n",
+ "> >=20\n",
"> > TVE driver will set TVE0 clock to 216 MHz and TCON TV would set\n",
"> > TCON-TOP-TV0 rate which in turn sets TVE0 clock to something like 13.5\n",
"> > MHz (or whatever is the right clock rate for PAL and NTSC). As you can\n",
"> > see, same clock is set to two different rates by two different drivers.\n",
- "> > \n",
- "> > It *might* still work, since encoders set clock rate after TCON (at least\n",
+ "> >=20\n",
+ "> > It *might* still work, since encoders set clock rate after TCON (at lea=\n",
+ "st\n",
"> > that is my experience for HDMI pipeline), but that is still wrong.\n",
- "> > \n",
+ "> >=20\n",
"> > To overcome above issue, I would stick to original proposal with\n",
"> > additional\n",
- "> > clock specified in TCON TV DT node. That way TCON driver would always set\n",
- "> > clock rate to TCON-TV0 clock. If TVE0 is enabled, TCON wouldn't interfere\n",
+ "> > clock specified in TCON TV DT node. That way TCON driver would always s=\n",
+ "et\n",
+ "> > clock rate to TCON-TV0 clock. If TVE0 is enabled, TCON wouldn't interfe=\n",
+ "re\n",
"> > with setting clock rate, because TCON-TV0 clock would be decoupled in\n",
"> > TCON-TOP mux.\n",
- "> > \n",
+ "> >=20\n",
"> > What do you think?\n",
- "> \n",
- "> I think this is the wrong representation, and worse, you are trying to work\n",
+ ">=20\n",
+ "> I think this is the wrong representation, and worse, you are trying to wo=\n",
+ "rk\n",
"> around software issues with it.\n",
- "> \n",
+ ">=20\n",
"> So to confirm some details, the TVE expects 216 MHz clock, and it expects\n",
"> the TCON to run and output data at 216 MHz as well. Is that correct?\n",
"\n",
- "Yes, from my understanding. 216 MHz is correct at least for PAL and NTSC, e.g. \n",
+ "Yes, from my understanding. 216 MHz is correct at least for PAL and NTSC, e=\n",
+ "=2Eg.=20\n",
"TV mode. TVE on R40 is also capable of RGB mode (VGA connector).\n",
"\n",
- "> \n",
+ ">=20\n",
"> Would any settings for the TCON differ between when HDMI or TVE is used?\n",
- "> \n",
+ ">=20\n",
"\n",
"Apart of clock, no, other settings would be the same.\n",
"\n",
@@ -333,25 +357,30 @@
"https://github.com/BPI-SINOVOIP/BPI-M2U-bsp/blob/master/linux-sunxi/drivers/\n",
"video/sunxi/disp2/tv/drv_tv.c#L24\n",
"\n",
- "216 MHz is applicable for low resolution, interlaced modes. Modes like 1080P, \n",
+ "216 MHz is applicable for low resolution, interlaced modes. Modes like 1080=\n",
+ "P,=20\n",
"1080I have expected standard timing.\n",
"\n",
- "> \n",
- "> I think these kinds of quirks should be handled in the software, instead of\n",
+ ">=20\n",
+ "> I think these kinds of quirks should be handled in the software, instead =\n",
+ "of\n",
"> being papered over.\n",
"\n",
- "Ok, that works for me too. I would just like to have such design that would \n",
+ "Ok, that works for me too. I would just like to have such design that would=\n",
+ "=20\n",
"later allow implementing TVE driver without much issues.\n",
"\n",
- "BTW, H3 TV TCON which is connected to TVE doesn't have TCON-TV channel clock \n",
- "at all, since it is controlled with TVE clock (same case as it would be here, \n",
+ "BTW, H3 TV TCON which is connected to TVE doesn't have TCON-TV channel cloc=\n",
+ "k=20\n",
+ "at all, since it is controlled with TVE clock (same case as it would be her=\n",
+ "e,=20\n",
"if TCON TOP mux is switched to TVE clock source).\n",
"\n",
- "Maybe quirk can be added that it doesn't set clock rate at all if it is \n",
+ "Maybe quirk can be added that it doesn't set clock rate at all if it is=20\n",
"connected to TVE?\n",
"\n",
"Best regards,\n",
"Jernej"
]
-d3971958807ed87b5397fffb800c693be0852750d4912e8d633c1a0df93f2aca
+49477324e45cd09dc876bd20504c01f0cf4c4fae68a61dbf067755ab15af5543
diff --git a/a/1.txt b/N3/1.txt
index a30dd7e..baad887 100644
--- a/a/1.txt
+++ b/N3/1.txt
@@ -1,23 +1,23 @@
Dne ponedeljek, 25. junij 2018 ob 05:51:41 CEST je Chen-Yu Tsai napisal(a):
-> On Mon, Jun 25, 2018 at 3:52 AM, Jernej Škrabec
+> On Mon, Jun 25, 2018 at 3:52 AM, Jernej ?krabec
>
> <jernej.skrabec@gmail.com> wrote:
-> > Dne četrtek, 21. junij 2018 ob 17:35:45 CEST je Jernej Škrabec napisal(a):
-> >> Dne četrtek, 21. junij 2018 ob 03:23:27 CEST je Chen-Yu Tsai napisal(a):
-> >> > On Thu, Jun 21, 2018 at 3:37 AM, Jernej Škrabec
+> > Dne ?etrtek, 21. junij 2018 ob 17:35:45 CEST je Jernej ?krabec napisal(a):
+> >> Dne ?etrtek, 21. junij 2018 ob 03:23:27 CEST je Chen-Yu Tsai napisal(a):
+> >> > On Thu, Jun 21, 2018 at 3:37 AM, Jernej ?krabec
> >> > <jernej.skrabec@siol.net>
> >>
> >> wrote:
> >> > > Dne sobota, 16. junij 2018 ob 07:48:38 CEST je Chen-Yu Tsai
napisal(a):
-> >> > >> On Sat, Jun 16, 2018 at 1:33 AM, Jernej Škrabec
+> >> > >> On Sat, Jun 16, 2018 at 1:33 AM, Jernej ?krabec
> >> > >> <jernej.skrabec@siol.net>
> >> > >
> >> > > wrote:
> >> > >> > Dne petek, 15. junij 2018 ob 19:13:17 CEST je Chen-Yu Tsai
> >
> > napisal(a):
-> >> > >> >> On Sat, Jun 16, 2018 at 12:41 AM, Jernej Škrabec
+> >> > >> >> On Sat, Jun 16, 2018 at 12:41 AM, Jernej ?krabec
> >> > >> >>
> >> > >> >> <jernej.skrabec@siol.net> wrote:
> >> > >> >> > Hi,
diff --git a/a/content_digest b/N3/content_digest
index 87e9461..e93df0c 100644
--- a/a/content_digest
+++ b/N3/content_digest
@@ -8,31 +8,16 @@
"ref\0CAGb2v67wVpAKk-5kSpnbnBXz7DkHToPa6bwuRBnsfHovw74HVQ\@mail.gmail.com\0"
]
[
- "From\0Jernej \305\240krabec <jernej.skrabec\@gmail.com>\0"
+ "From\0jernej.skrabec\@gmail.com (Jernej \305\240krabec)\0"
]
[
- "Subject\0Re: [linux-sunxi] Re: [PATCH v2 11/27] drm/sun4i: tcon: Add support for tcon-top gate\0"
+ "Subject\0[linux-sunxi] Re: [PATCH v2 11/27] drm/sun4i: tcon: Add support for tcon-top gate\0"
]
[
"Date\0Mon, 25 Jun 2018 09:58:57 +0200\0"
]
[
- "To\0linux-sunxi\@googlegroups.com",
- " wens\@csie.org\0"
-]
-[
- "Cc\0Maxime Ripard <maxime.ripard\@bootlin.com>",
- " Rob Herring <robh+dt\@kernel.org>",
- " David Airlie <airlied\@linux.ie>",
- " Gustavo Padovan <gustavo\@padovan.org>",
- " Maarten Lankhorst <maarten.lankhorst\@linux.intel.com>",
- " Sean Paul <seanpaul\@chromium.org>",
- " Mark Rutland <mark.rutland\@arm.com>",
- " dri-devel <dri-devel\@lists.freedesktop.org>",
- " devicetree <devicetree\@vger.kernel.org>",
- " linux-arm-kernel <linux-arm-kernel\@lists.infradead.org>",
- " linux-kernel <linux-kernel\@vger.kernel.org>",
- " linux-clk <linux-clk\@vger.kernel.org>\0"
+ "To\0linux-arm-kernel\@lists.infradead.org\0"
]
[
"\0000:1\0"
@@ -42,25 +27,25 @@
]
[
"Dne ponedeljek, 25. junij 2018 ob 05:51:41 CEST je Chen-Yu Tsai napisal(a):\n",
- "> On Mon, Jun 25, 2018 at 3:52 AM, Jernej \305\240krabec\n",
+ "> On Mon, Jun 25, 2018 at 3:52 AM, Jernej ?krabec\n",
"> \n",
"> <jernej.skrabec\@gmail.com> wrote:\n",
- "> > Dne \304\215etrtek, 21. junij 2018 ob 17:35:45 CEST je Jernej \305\240krabec napisal(a):\n",
- "> >> Dne \304\215etrtek, 21. junij 2018 ob 03:23:27 CEST je Chen-Yu Tsai napisal(a):\n",
- "> >> > On Thu, Jun 21, 2018 at 3:37 AM, Jernej \305\240krabec\n",
+ "> > Dne ?etrtek, 21. junij 2018 ob 17:35:45 CEST je Jernej ?krabec napisal(a):\n",
+ "> >> Dne ?etrtek, 21. junij 2018 ob 03:23:27 CEST je Chen-Yu Tsai napisal(a):\n",
+ "> >> > On Thu, Jun 21, 2018 at 3:37 AM, Jernej ?krabec\n",
"> >> > <jernej.skrabec\@siol.net>\n",
"> >> \n",
"> >> wrote:\n",
"> >> > > Dne sobota, 16. junij 2018 ob 07:48:38 CEST je Chen-Yu Tsai \n",
"napisal(a):\n",
- "> >> > >> On Sat, Jun 16, 2018 at 1:33 AM, Jernej \305\240krabec\n",
+ "> >> > >> On Sat, Jun 16, 2018 at 1:33 AM, Jernej ?krabec\n",
"> >> > >> <jernej.skrabec\@siol.net>\n",
"> >> > > \n",
"> >> > > wrote:\n",
"> >> > >> > Dne petek, 15. junij 2018 ob 19:13:17 CEST je Chen-Yu Tsai\n",
"> > \n",
"> > napisal(a):\n",
- "> >> > >> >> On Sat, Jun 16, 2018 at 12:41 AM, Jernej \305\240krabec\n",
+ "> >> > >> >> On Sat, Jun 16, 2018 at 12:41 AM, Jernej ?krabec\n",
"> >> > >> >> \n",
"> >> > >> >> <jernej.skrabec\@siol.net> wrote:\n",
"> >> > >> >> > Hi,\n",
@@ -354,4 +339,4 @@
"Jernej"
]
-d3971958807ed87b5397fffb800c693be0852750d4912e8d633c1a0df93f2aca
+bc658cd2e4856719f0d04fc248b73956b4fd913d7884ba8d38b9d4d28fce67b6
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.