sunxi-kms driver

[David Lanzendörfer]

Hi
I'm right now building a KMS driver using the HDMI interface as primary
connector:
http://git.o2s.ch/?p=linux-next.git;a=shortlog;h=refs/heads/20150327
/*
git clone http://git.o2s.ch/git/linux-next.git
git checkout 20150327
*/

I could use some help with the clocks driver.

Cheers
David

[Dmitriy B.]

2015-04-10 23:04 GMT+03:00 David Lanzendörfer <david.lan...@o2s.ch>:

Hi
I'm right now building a KMS driver using the HDMI interface as primary
connector

Nice,

Are you doing this while working at Allwinner?

Whats the status of the driver and are you planning to make it to mainline? (though, looking at code, that will take time - there are disp/osal leftovers all over the place).

Also copyright like this looks weird:

" * Copyright (C) 2015-2020 Allwinner Technology Co., Ltd."

Living in the future? :)

Best Regards,

Dmitriy Beykun

[Priit Laes]

On Fri, 2015-04-10 at 22:04 +0200, David Lanzendörfer wrote:
> Hi
> I'm right now building a KMS driver using the HDMI interface as
> primary
> connector:
> http://git.o2s.ch/?p=linux-next.git;a=shortlog;h=refs/heads/20150327
> /*
> git clone http://git.o2s.ch/git/linux-next.git
> git checkout 20150327
> */

Are you aware of tree this:
https://github.com/bbrezillon/linux-sunxi/tree/sunxi-drm-next

[David Lanzendörfer]

Hi

>Nice,
>Are you doing this while working at Allwinner?

I still haven't got this office at Allwinner since this one manager is afraid I
might run off after a month or so.
I'm writing a letter right now together with a girl from Anhui (also Guangdong
province) in good Chinese which will declare that I do not intend to leave
China for at least 5 years.
You should really all apply for a job there too.
The climate is awesome, the food is the best of the world and their equipment
is awesome! ^^

>Whats the status of the driver and are you planning to make it to mainline?
>(though, looking at code, that will take time - there are disp/osal leftovers
>all over the place).

Yes. I know. I'm cleaning up the code right now

>Also copyright like this looks weird:
>" * Copyright (C) 2015-2020 Allwinner Technology Co., Ltd."
>Living in the future? :)

I'm granting all the copyright to my newly written code to Allwinner so no...
It's 2015 and the copyright goes 5 years... Am I wrong? ^^'

Cheers

[Stefan Monnier]

>> Also copyright like this looks weird:
>> " * Copyright (C) 2015-2020 Allwinner Technology Co., Ltd."
>> Living in the future? :)
> I'm granting all the copyright to my newly written code to Allwinner so no...
> It's 2015 and the copyright goes 5 years... Am I wrong? ^^'

Yes, you're wrong: the copyright statement is about when the copyright
starts, basically, so it can't be in the future. The duration of the
copyright is then defined based on this information combined with the
law (which is not 5 years, but more like 75 years, or maybe even "75
years after the death of the author", and has changed over the time,
with the tendency being to extend copyright towards infinity, since
those decisions are mostly taken by people who have personal financial
incentives to extend the coverage as much as they can get away with (or
are close to people who have such)).


Stefan

[jons...@gmail.com]

You need to insert the copyright notice as a way of saying you own the
code in the file. After you claim ownership you can choose a license
to release your work under. The important part of kernel development
is placing the GPL notice at the top of each kernel source file (copy
it from another kernel file). The copyright notice is just a statement
saying you have the right to license the code under the GPL. Once you
license under the GPL, the GPL allows many more uses of the code than
simple copyright does.

Some projects require copyright assignment, but the kernel does not.
The main reason for copyright assignment is in case the license needs
to be changed later. For example Mozilla was originally released under
the MPL. The Mozilla organization was forced to track down and get
written permission from every copyright holder when they reissued
Mozilla under the LGPL. Some of these authors could not be located
which required chunks of Mozilla to be rewritten. Now Mozilla gets
copyright right assignment from each author in order to allow them to
change the license again if necessary.

The kernel has long passed having any ability to track down all of the
copyright holders since some of them are dead. It will be GPLv2
forever because there is no way to change it. If you want to
contribute your code to mainline it has to have at the minimum: a
copyright statement and the GPLv2 license. If you want you can also
include the MIT license in addition to the GPLv2. Including the MIT
license allows the code the be shared with BSD.

> --
> 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...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



--
Jon Smirl
jons...@gmail.com

[David Lanzendörfer]

Hi
I've added a clock driver for the special plls now:
http://git.o2s.ch/?p=linux-next.git;a=commit;h=17173fad5fb7ddc8154444e1a84002c090bf5106
Now I need some driver for the clocks at 0x01C20000,
specifically at offset 0x0150 and offset 0x0174

Would the best names for each of this clock be?

Cheers
David

[Henrik Nordström]

Something based on their function?

0x0150 HDMI_CLK_REG
normal clock gating + PLL selector + divisor. Looks like a normal clock
output for HDMI block?

0x0174 HDMI1_CTRL_REG
no idea what the function this has. Is it even a clock? All the
documentation I have access to only says "HDMI1 System Control
Register".

Regards
Henrik

[David Lanzendörfer]

Hi

> Something based on their function?
>
> 0x0150 HDMI_CLK_REG
> normal clock gating + PLL selector + divisor. Looks like a normal clock
> output for HDMI block?

This is the actual clock control within the HDMI module. yes.

> 0x0174 HDMI1_CTRL_REG
> no idea what the function this has. Is it even a clock? All the
> documentation I have access to only says "HDMI1 System Control
> Register".

That's an additional part of the controller.
They just tinkered the IP blocks control bus into the SoC-design tool wherever
there was space within the address range.
That just happens when 50 people just change a whole IP block in the middle of
the design stage ^^'

Cheers
David