[git pull] drm for v4.15 (fixes/cleanups/one small feature)

2017-11-22 Thread Dave Airlie
Hi Linus, This is just some bits and pieces for the second half of the merge window, 1. Remove the MSM dt-bindings file Rob managed to push in the previous pull. 2. Add a property/edid quirk to denote HMD devices, I had these hanging around for a few weeks and Keith had done some work on them,

[git pull] drm for v4.15 (fixes/cleanups/one small feature)

2017-11-22 Thread Dave Airlie
Hi Linus, This is just some bits and pieces for the second half of the merge window, 1. Remove the MSM dt-bindings file Rob managed to push in the previous pull. 2. Add a property/edid quirk to denote HMD devices, I had these hanging around for a few weeks and Keith had done some work on them,

Re: [git pull] drm for v4.15

2017-11-18 Thread Nicolai Hähnle
On 17.11.2017 20:18, Christian König wrote: The obvious alternative which we are working on for a few years now is to improve the input data we get from the hardware people. In other words instead of getting a flat list of registers we want the information about where and how many times a

Re: [git pull] drm for v4.15

2017-11-18 Thread Nicolai Hähnle
On 17.11.2017 20:18, Christian König wrote: The obvious alternative which we are working on for a few years now is to improve the input data we get from the hardware people. In other words instead of getting a flat list of registers we want the information about where and how many times a

Re: [git pull] drm for v4.15

2017-11-17 Thread Christian König
Am 17.11.2017 um 19:55 schrieb Linus Torvalds: On Fri, Nov 17, 2017 at 10:14 AM, Christian König wrote: Taking an example from the AMD headers why this automation is more tricky than it sounds in the first place: Look at the mmVM_CONTEXT*_PAGE_TABLE_BASE_ADDR

Re: [git pull] drm for v4.15

2017-11-17 Thread Christian König
Am 17.11.2017 um 19:55 schrieb Linus Torvalds: On Fri, Nov 17, 2017 at 10:14 AM, Christian König wrote: Taking an example from the AMD headers why this automation is more tricky than it sounds in the first place: Look at the mmVM_CONTEXT*_PAGE_TABLE_BASE_ADDR registers for example. Register

Re: [git pull] drm for v4.15

2017-11-17 Thread Linus Torvalds
On Fri, Nov 17, 2017 at 10:14 AM, Christian König wrote: > > Taking an example from the AMD headers why this automation is more tricky > than it sounds in the first place: Look at the > mmVM_CONTEXT*_PAGE_TABLE_BASE_ADDR registers for example. > > Register 0-7 are

Re: [git pull] drm for v4.15

2017-11-17 Thread Linus Torvalds
On Fri, Nov 17, 2017 at 10:14 AM, Christian König wrote: > > Taking an example from the AMD headers why this automation is more tricky > than it sounds in the first place: Look at the > mmVM_CONTEXT*_PAGE_TABLE_BASE_ADDR registers for example. > > Register 0-7 are consecutive and so could be

Re: [git pull] drm for v4.15

2017-11-17 Thread Christian König
First of all I can certainly agree with everything said so far, so just skipping to the technical problem. Am 17.11.2017 um 17:57 schrieb Linus Torvalds: People say "it's a ton of work to do it by hand". They'd be right. I'm not saying you should do it by hand. But "automation" does not

Re: [git pull] drm for v4.15

2017-11-17 Thread Christian König
First of all I can certainly agree with everything said so far, so just skipping to the technical problem. Am 17.11.2017 um 17:57 schrieb Linus Torvalds: People say "it's a ton of work to do it by hand". They'd be right. I'm not saying you should do it by hand. But "automation" does not

Re: [git pull] drm for v4.15

2017-11-17 Thread Linus Torvalds
On Fri, Nov 17, 2017 at 9:19 AM, Lukas Wunner wrote: >> and tell me that there isn't any room for making these things smarter. > > ... or deduplicate them. :-) You could even - wait for it - have _automation_ that does it. Yeah, it's easier to write a stupid sed-script or

Re: [git pull] drm for v4.15

2017-11-17 Thread Linus Torvalds
On Fri, Nov 17, 2017 at 9:19 AM, Lukas Wunner wrote: >> and tell me that there isn't any room for making these things smarter. > > ... or deduplicate them. :-) You could even - wait for it - have _automation_ that does it. Yeah, it's easier to write a stupid sed-script or whatever to generate

Re: [git pull] drm for v4.15

2017-11-17 Thread Lukas Wunner
On Fri, Nov 17, 2017 at 08:57:53AM -0800, Linus Torvalds wrote: > On Fri, Nov 17, 2017 at 4:51 AM, Nicolai Hähnle wrote: > To see the effects of this, I picked something at random from one of > those huge AMD header files. > > I swear. It was entirely at random, and the first

Re: [git pull] drm for v4.15

2017-11-17 Thread Lukas Wunner
On Fri, Nov 17, 2017 at 08:57:53AM -0800, Linus Torvalds wrote: > On Fri, Nov 17, 2017 at 4:51 AM, Nicolai Hähnle wrote: > To see the effects of this, I picked something at random from one of > those huge AMD header files. > > I swear. It was entirely at random, and the first thing I picked. Do

Re: [git pull] drm for v4.15

2017-11-17 Thread Linus Torvalds
On Fri, Nov 17, 2017 at 4:51 AM, Nicolai Hähnle wrote: > > This raises the question of how people feel about putting the source > database into the kernel (most likely as XML in our case) and > auto-generating the headers from there instead. I suspect that at least in some

Re: [git pull] drm for v4.15

2017-11-17 Thread Linus Torvalds
On Fri, Nov 17, 2017 at 4:51 AM, Nicolai Hähnle wrote: > > This raises the question of how people feel about putting the source > database into the kernel (most likely as XML in our case) and > auto-generating the headers from there instead. I suspect that at least in some cases, the "source"

Re: [git pull] drm for v4.15

2017-11-17 Thread Nicolai Hähnle
On 16.11.2017 21:57, Dave Airlie wrote: On 16 November 2017 at 14:59, Linus Torvalds wrote: On Wed, Nov 15, 2017 at 6:34 PM, Dave Airlie wrote: There is some code touched on sound/soc, but I think the sound tree should have the same commits

Re: [git pull] drm for v4.15

2017-11-17 Thread Nicolai Hähnle
On 16.11.2017 21:57, Dave Airlie wrote: On 16 November 2017 at 14:59, Linus Torvalds wrote: On Wed, Nov 15, 2017 at 6:34 PM, Dave Airlie wrote: There is some code touched on sound/soc, but I think the sound tree should have the same commits from the same base,so this may luck different if

Re: [git pull] drm for v4.15

2017-11-16 Thread Linus Torvalds
On Thu, Nov 16, 2017 at 12:57 PM, Dave Airlie wrote: > > This sounds more like a Monty Python sketch than a serious question. It's a serious question when the files start appearing in random places where they don't belong. There's a place for automatically generated files.

Re: [git pull] drm for v4.15

2017-11-16 Thread Linus Torvalds
On Thu, Nov 16, 2017 at 12:57 PM, Dave Airlie wrote: > > This sounds more like a Monty Python sketch than a serious question. It's a serious question when the files start appearing in random places where they don't belong. There's a place for automatically generated files. But that "there is a

Re: [git pull] drm for v4.15

2017-11-16 Thread Dave Airlie
On 16 November 2017 at 14:59, Linus Torvalds wrote: > On Wed, Nov 15, 2017 at 6:34 PM, Dave Airlie wrote: >> >> There is some code touched on sound/soc, but I think the sound tree >> should have the same commits from the same base,so this may

Re: [git pull] drm for v4.15

2017-11-16 Thread Dave Airlie
On 16 November 2017 at 14:59, Linus Torvalds wrote: > On Wed, Nov 15, 2017 at 6:34 PM, Dave Airlie wrote: >> >> There is some code touched on sound/soc, but I think the sound tree >> should have the same commits from the same base,so this may luck different >> if you pulled it as I generated my

Re: [git pull] drm for v4.15

2017-11-16 Thread Michel Dänzer
On 16/11/17 05:59 AM, Linus Torvalds wrote: > > There's something odd about drm people. You guys like these completely > insane generated header files, and you seem to be populating the whole > tree with this odd and diseased notion of "generated header files are > cool". > > Is somebody getting

Re: [git pull] drm for v4.15

2017-11-16 Thread Michel Dänzer
On 16/11/17 05:59 AM, Linus Torvalds wrote: > > There's something odd about drm people. You guys like these completely > insane generated header files, and you seem to be populating the whole > tree with this odd and diseased notion of "generated header files are > cool". > > Is somebody getting

Re: [git pull] drm for v4.15

2017-11-16 Thread Rob Clark
On Wed, Nov 15, 2017 at 11:59 PM, Linus Torvalds wrote: > On Wed, Nov 15, 2017 at 6:34 PM, Dave Airlie wrote: >> >> There is some code touched on sound/soc, but I think the sound tree >> should have the same commits from the same base,so this may

Re: [git pull] drm for v4.15

2017-11-16 Thread Rob Clark
On Wed, Nov 15, 2017 at 11:59 PM, Linus Torvalds wrote: > On Wed, Nov 15, 2017 at 6:34 PM, Dave Airlie wrote: >> >> There is some code touched on sound/soc, but I think the sound tree >> should have the same commits from the same base,so this may luck different >> if you pulled it as I generated

Re: [git pull] drm for v4.15

2017-11-15 Thread Linus Torvalds
On Wed, Nov 15, 2017 at 6:34 PM, Dave Airlie wrote: > > There is some code touched on sound/soc, but I think the sound tree > should have the same commits from the same base,so this may luck different > if you pulled it as I generated my pull request a couple of days ago. >

Re: [git pull] drm for v4.15

2017-11-15 Thread Linus Torvalds
On Wed, Nov 15, 2017 at 6:34 PM, Dave Airlie wrote: > > There is some code touched on sound/soc, but I think the sound tree > should have the same commits from the same base,so this may luck different > if you pulled it as I generated my pull request a couple of days ago. > Otherwise > the