All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Kyungmin Park <kyungmin.park@samsung.com>,
	Kukjin Kim <kgene.kim@samsung.com>,
	linux-samsung-soc@vger.kernel.org,
	Joonyoung Shim <jy0922.shim@samsung.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCHv2 0/3] Add support for DRM display subsystem
Date: Thu, 10 May 2012 13:48:20 +0000	[thread overview]
Message-ID: <201205101348.20870.arnd@arndb.de> (raw)
In-Reply-To: <CAH9JG2V_9RVPvEHodDD422r=o4QxHcrMO-YXv2KUGYeys=ZjqA@mail.gmail.com>

On Thursday 10 May 2012, Kyungmin Park wrote:
> > And I won't apply new feature for non-dt board file from now on. I think,
> > we
> > need to support DT in mach-exynos/ instead of non-DT and DT together, so
> > please consider to move on dt supporting for Samsung mobile boards.
> >
> 
> Probably you misunderstand Arnd word.
> 
> "From the statements made so far, I can see no clear policy that we can
> apply to everyone. My take on this is that for any work I spend on
> multiplatform kernel, I concentrate on the DT-based board files and
> get them to work together first, but leave it up to the individual
> subarch maintainers whether they want to add other board files into
> the mix."
> 
> It doesn't mean add new feature to non-DT board. don't add new board file.

This is a completely separate discussion, the problem at hand doesn't
have anything to do with building a kernel for multiple mach-*
directories combined that I was referring to in the text you quote.

> In this case, DRM is not yet ready to support DT.
> 
> Okay, you can just drop this patches. but please note that this
> patches are posted at Mar 13 before you decide.

I think it's a good idea to make new features DT-only because this
way we don't get any regressions and everyone who want to use
the new feature will be able to test the DT support on his board.

This of course requires that basic DT support is available for the
systems in question so we don't regress when moving away from the
old board files. My impression is that we're getting close to that
point on exynos thanks to Thomas' work on this. AFAICT we don't
have a DT binding for screen timings yet, so you will still have
to use auxdata for that or put the timings into the driver.

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/3] Add support for DRM display subsystem
Date: Thu, 10 May 2012 13:48:20 +0000	[thread overview]
Message-ID: <201205101348.20870.arnd@arndb.de> (raw)
In-Reply-To: <CAH9JG2V_9RVPvEHodDD422r=o4QxHcrMO-YXv2KUGYeys=ZjqA@mail.gmail.com>

On Thursday 10 May 2012, Kyungmin Park wrote:
> > And I won't apply new feature for non-dt board file from now on. I think,
> > we
> > need to support DT in mach-exynos/ instead of non-DT and DT together, so
> > please consider to move on dt supporting for Samsung mobile boards.
> >
> 
> Probably you misunderstand Arnd word.
> 
> "From the statements made so far, I can see no clear policy that we can
> apply to everyone. My take on this is that for any work I spend on
> multiplatform kernel, I concentrate on the DT-based board files and
> get them to work together first, but leave it up to the individual
> subarch maintainers whether they want to add other board files into
> the mix."
> 
> It doesn't mean add new feature to non-DT board. don't add new board file.

This is a completely separate discussion, the problem at hand doesn't
have anything to do with building a kernel for multiple mach-*
directories combined that I was referring to in the text you quote.

> In this case, DRM is not yet ready to support DT.
> 
> Okay, you can just drop this patches. but please note that this
> patches are posted at Mar 13 before you decide.

I think it's a good idea to make new features DT-only because this
way we don't get any regressions and everyone who want to use
the new feature will be able to test the DT support on his board.

This of course requires that basic DT support is available for the
systems in question so we don't regress when moving away from the
old board files. My impression is that we're getting close to that
point on exynos thanks to Thomas' work on this. AFAICT we don't
have a DT binding for screen timings yet, so you will still have
to use auxdata for that or put the timings into the driver.

	Arnd

  reply	other threads:[~2012-05-10 13:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 10:39 [PATCHv2 0/3] Add support for DRM display subsystem Marek Szyprowski
2012-03-13 10:39 ` Marek Szyprowski
2012-03-13 10:39 ` [PATCHv2 1/3] ARM: Exynos: add platform device for core DRM subsystem Marek Szyprowski
2012-03-13 10:39   ` Marek Szyprowski
2012-03-13 10:39 ` [PATCHv2 2/3] ARM: Exynos: Add DRM core device support for Universal C210 board Marek Szyprowski
2012-03-13 10:39   ` Marek Szyprowski
2012-03-13 10:39 ` [PATCHv2 3/3] ARM: Exynos: Add DRM core support for NURI board Marek Szyprowski
2012-03-13 10:39   ` Marek Szyprowski
2012-05-10  9:36 ` [PATCHv2 0/3] Add support for DRM display subsystem Kukjin Kim
2012-05-10  9:36   ` Kukjin Kim
2012-05-10  9:53   ` Kyungmin Park
2012-05-10  9:53     ` Kyungmin Park
2012-05-10 13:48     ` Arnd Bergmann [this message]
2012-05-10 13:48       ` Arnd Bergmann
2012-05-10 14:46       ` Kyungmin Park
2012-05-10 14:46         ` Kyungmin Park
2012-05-10 15:00         ` Sachin Kamat
2012-05-10 15:00           ` Sachin Kamat
2012-05-11 10:37         ` Kukjin Kim
2012-05-11 10:37           ` Kukjin Kim
2012-05-10 11:18   ` Marek Szyprowski
2012-05-10 11:18     ` Marek Szyprowski
2012-05-10 18:16   ` Sylwester Nawrocki
2012-05-10 18:16     ` Sylwester Nawrocki
2012-05-12 23:54 ` Kukjin Kim
2012-05-12 23:54   ` Kukjin Kim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201205101348.20870.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=jy0922.shim@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.