<kuba2k2>
tested on a T113 with a single-link 1024x768 LVDS panel (I don't have any dual-link hardware, but I assume it won't work without some changes)
hexdump01 has quit []
hexdump0815 has joined #linux-sunxi
dsimic is now known as Guest9644
dsimic has joined #linux-sunxi
Guest9644 has quit [Ping timeout: 480 seconds]
chewitt has quit [Quit: Zzz..]
evgeny_boger1 has joined #linux-sunxi
evgeny_boger has quit [Remote host closed the connection]
ungeskriptet has joined #linux-sunxi
kuba2k2 has quit [Ping timeout: 480 seconds]
apritzel has quit [Quit: Leaving]
apritzel has joined #linux-sunxi
aperezdc has quit [Remote host closed the connection]
aperezdc has joined #linux-sunxi
<apritzel>
kuba2k2: are you going to upstream that? Otherwise it's not worth too much, especially not without your Signed-of-by: line, so that others can pick it up
<loki666>
jernej: thanks for reviewing the patches ... could the GPU PLL reparenting be merged without the PPU (which, currently panic on disable... I'll dig that issue) ?
<loki666>
for the USB OTG issue, I'll address your coments... with a proper patch (that compiles) and cover. I posted this to have a feedback on "I'm a going in the right direction"
<apritzel>
loki666: I am preparing a new H6/H616 PPU series as we speak, which would cover the GPU. We can then discuss the hang issue on the list
<apritzel>
my theory is that it's some sequence of clock gates/reset/power-supply/power-domain that is not right, though this might be hard to fix properly
ftg has joined #linux-sunxi
<loki666>
looking at the allwinner mali support code, it seems to disable the GPU0 clk and do assert the reset control before gating the PPU
<loki666>
and in the reverse order when ungating, so, ungate, deassert, enable clk
<Jookia>
what does it mean when someone says they prefer another patch? is it just a random response?
<Jookia>
does it mean they're purposely not reviewing it because they like another patch better?
Robot_ has quit [Ping timeout: 480 seconds]
<apritzel>
loki666: problem is that this is "Mali generic" code, so we need to put it in there, and answer questions of why this hasn't been a problem before ...
<apritzel>
Jookia: but jernej gave a rationale, didn't he?
<Jookia>
a rationale for ... what?
<Jookia>
just sending a random comment to me?
<apritzel>
"... since it also has thermal zones." ?
<Jookia>
yeah, but i didn't ask what patch they prefer, it's just unsolicited opion :\
<Jookia>
opinion*
<apritzel>
unsolicited? what are you talking about? he is the maintainer, and you sent a patch for review?
<Jookia>
yeah, review would be good. not this
<Jookia>
or is that what sometimes happens? maintainers just say things that aren't useful to the submitter?
<apritzel>
I don't get you, sorry. He is the maintainer, saying: "you posted a patch which is a subset of something that has been posted a few days ago, and which was more complete" is a completely valid response
<Jookia>
i guess. it just isn't useful or actionable that's all
<Jookia>
they might as well have not replied at all
<loki666>
apritzel: this sequence is not Mali generic, it's Allwinner specific glue code for Mali kernel driver
jkm_ has joined #linux-sunxi
<apritzel>
Jookia: ??? I think he did the right thing: expressed his valid and opinion and gave a reason. Technically you were too late anyway (as you figured yourself), so your patch is now somewhat obsolete
<Jookia>
apritzel: why would it be obsolete?
<apritzel>
if you don't like it, reply, also others might object as well
<apritzel>
because that other patch, posted earlier, already covers that
<apritzel>
you said it yourself earlier ...
<Jookia>
yes, but the other patch is going to require more work and can't be merged as-is
<Jookia>
the other patch does two things at once and the second part of thermal zones is likely going to include a lot more discussion
<apritzel>
well, if you think that's important, then reply. But we have like two or three more weeks left, so waiting for a v2 of this patch is a valid approach, I'd say
<apritzel>
not sure why you are so upset about it - it isn't even your patch ;-)
<Jookia>
i'm not upset just confused
<Jookia>
someone replied to me with some information they want me to know, and as far as i can tell the information isn't useful, unless i'm missing some subtext here
<Jookia>
being told that someone prefers another patch is fine, i just don't see why they'd tell me?
<Jookia>
unless they wanted me to do something based on that information, but they don't tell me what that is
<Jookia>
or they're doing something based on that information and i have to infer what it is
<apritzel>
he told you *and the rest of the list* that he would prefer to not take your patch
<Jookia>
ah, that's the subtext
<Jookia>
ok thank you
<apritzel>
which is nice of him, instead of just ignoring your patch
jkm has quit [Ping timeout: 480 seconds]
<Jookia>
yes
<apritzel>
I wanted to reply already, and his email gives me this opportunity
<apritzel>
loki666: but we don't have any such glue code in mainline, do we? That's what I meant with this becoming tricky ...
evgeny_boger1 has quit []
evgeny_boger has joined #linux-sunxi
evgeny_boger has quit [Ping timeout: 480 seconds]
ftg has quit [Read error: Connection reset by peer]