All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Figa <tomasz.figa@gmail.com>
To: "Andreas Färber" <afaerber@suse.de>,
	"Doug Anderson" <dianders@chromium.org>,
	"Javier Martinez Canillas" <javier.martinez@collabora.co.uk>
Cc: linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Stephan van Schaik <stephan@synkhronix.com>,
	Vincent Palatin <vpalatin@chromium.org>,
	Tomasz Figa <t.figa@samsung.com>
Subject: Re: [PATCH v6 00/10] ARM: dts: exynos: Prepare Spring
Date: Sat, 02 Aug 2014 15:13:51 +0200	[thread overview]
Message-ID: <53DCE40F.10809@gmail.com> (raw)
In-Reply-To: <53DCBC84.8080600@suse.de>

On 02.08.2014 12:25, Andreas Färber wrote:

[snip]

> One thing I've wondered is whether we should put status = "disabled" on
> the dp node with some comment, since it's known not to work as is (but
> better having the data here than leaving it out, I believe).

Does the DP node itself need more data to work or just some external
things are missing? If the former then probably status = "disabled"
should be set, otherwise "okay" is fine if provided data are enough to
probe the Exynos DP driver.

> 
> Of course if either of you has input on the discussions on the drm
> bridge/panel series V6 [1] for how to enable non-simplefb display and
> iommus, that would be valuable.

Support for Exynos IOMMU is being worked on right now and patches adding
DT support from Marek Szyprowski should show up on the lists in very
near future. However I think you don't strictly need IOMMU to get
non-simplefb display, as CMA can be used to allocate contiguous memory.

> 
> [1] http://www.spinics.net/lists/linux-samsung-soc/msg35274.html
> 

[snip]

> For the touchpad it seems DT support has landed in the input tree as
> "atmel,maxtouch". Backporting just that patch does not make it work
> though. (Tried the rejected pinctrl approach to be on the safe side.)
> https://code.google.com/p/chromium/issues/detail?id=371114
> https://patchwork.kernel.org/patch/3976801/

Looking at what we already have in mainline and the discussion in
Chromium issue tracker, current driver should be already in shape to
handle the Chromebooks. Apparently it even supports recovery from
bootloader mode without the need to parse bootloader address from DT (it
somehow calculates possible addresses from main address).

Best regards,
Tomasz

WARNING: multiple messages have this Message-ID (diff)
From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 00/10] ARM: dts: exynos: Prepare Spring
Date: Sat, 02 Aug 2014 15:13:51 +0200	[thread overview]
Message-ID: <53DCE40F.10809@gmail.com> (raw)
In-Reply-To: <53DCBC84.8080600@suse.de>

On 02.08.2014 12:25, Andreas F?rber wrote:

[snip]

> One thing I've wondered is whether we should put status = "disabled" on
> the dp node with some comment, since it's known not to work as is (but
> better having the data here than leaving it out, I believe).

Does the DP node itself need more data to work or just some external
things are missing? If the former then probably status = "disabled"
should be set, otherwise "okay" is fine if provided data are enough to
probe the Exynos DP driver.

> 
> Of course if either of you has input on the discussions on the drm
> bridge/panel series V6 [1] for how to enable non-simplefb display and
> iommus, that would be valuable.

Support for Exynos IOMMU is being worked on right now and patches adding
DT support from Marek Szyprowski should show up on the lists in very
near future. However I think you don't strictly need IOMMU to get
non-simplefb display, as CMA can be used to allocate contiguous memory.

> 
> [1] http://www.spinics.net/lists/linux-samsung-soc/msg35274.html
> 

[snip]

> For the touchpad it seems DT support has landed in the input tree as
> "atmel,maxtouch". Backporting just that patch does not make it work
> though. (Tried the rejected pinctrl approach to be on the safe side.)
> https://code.google.com/p/chromium/issues/detail?id=371114
> https://patchwork.kernel.org/patch/3976801/

Looking at what we already have in mainline and the discussion in
Chromium issue tracker, current driver should be already in shape to
handle the Chromebooks. Apparently it even supports recovery from
bootloader mode without the need to parse bootloader address from DT (it
somehow calculates possible addresses from main address).

Best regards,
Tomasz

  reply	other threads:[~2014-08-02 13:13 UTC|newest]

Thread overview: 98+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-02  0:52 [PATCH v6 00/10] ARM: dts: exynos: Prepare Spring Andreas Färber
2014-08-02  0:52 ` Andreas Färber
2014-08-02  0:52 ` [PATCH v6 01/10] ARM: dts: Fix MMC pinctrl for exynos5250-snow Andreas Färber
2014-08-02  0:52   ` Andreas Färber
2014-08-02  0:52   ` Andreas Färber
2014-08-02  0:52 ` [PATCH v6 02/10] ARM: dts: Fold exynos5250-cros-common into exynos5250-snow Andreas Färber
2014-08-02  0:52   ` Andreas Färber
2014-08-02  0:52   ` Andreas Färber
2014-08-02  0:52 ` [PATCH v6 03/10] ARM: dts: Prepare node labels for exynos5250 Andreas Färber
2014-08-02  0:52   ` Andreas Färber
2014-08-02  0:52   ` Andreas Färber
2014-08-02  4:48   ` Doug Anderson
2014-08-02  4:48     ` Doug Anderson
2014-08-02  4:48     ` Doug Anderson
2014-08-02 12:19   ` Tomasz Figa
2014-08-02 12:19     ` Tomasz Figa
2014-08-02 13:00     ` Andreas Färber
2014-08-02 13:00       ` Andreas Färber
2014-08-02 13:00       ` Andreas Färber
2014-08-20 13:06       ` Andreas Färber
2014-08-20 13:06         ` Andreas Färber
2014-08-20 13:02     ` [PATCH v7] " Andreas Färber
2014-08-20 13:02       ` Andreas Färber
2014-08-20 13:02       ` Andreas Färber
2014-08-22 10:49       ` Kukjin Kim
2014-08-22 10:49         ` Kukjin Kim
2014-08-22 11:37         ` Andreas Färber
2014-08-22 11:37           ` Andreas Färber
2014-08-22 16:14         ` Doug Anderson
2014-08-22 16:14           ` Doug Anderson
2014-08-02  0:52 ` [PATCH v6 04/10] ARM: dts: Clean up exynos5250-snow Andreas Färber
2014-08-02  0:52   ` Andreas Färber
2014-08-02  0:52   ` Andreas Färber
2014-08-02  4:54   ` Doug Anderson
2014-08-02  4:54     ` Doug Anderson
2014-08-02  4:54     ` Doug Anderson
2014-08-02 12:21   ` Tomasz Figa
2014-08-02 12:21     ` Tomasz Figa
2014-08-02 12:56     ` Tomasz Figa
2014-08-02 12:56       ` Tomasz Figa
2014-08-02 13:08       ` Andreas Färber
2014-08-02 13:08         ` Andreas Färber
2014-08-02 13:09         ` Tomasz Figa
2014-08-02 13:09           ` Tomasz Figa
2014-08-02  0:52 ` [PATCH v6 05/10] ARM: dts: Fill in bootargs for exynos5250-snow Andreas Färber
2014-08-02  0:52   ` Andreas Färber
2014-08-02  0:52   ` Andreas Färber
2014-08-02  2:17   ` Javier Martinez Canillas
2014-08-02  2:17     ` Javier Martinez Canillas
2014-08-02  0:52 ` [PATCH v6 06/10] ARM: dts: Clean up exynos5250-smdk5250 Andreas Färber
2014-08-02  0:52   ` Andreas Färber
2014-08-02  0:52   ` Andreas Färber
2014-08-02 12:57   ` Tomasz Figa
2014-08-02 12:57     ` Tomasz Figa
2014-08-02  0:52 ` [PATCH v6 07/10] ARM: dts: Clean up exynos5250-arndale Andreas Färber
2014-08-02  0:52   ` Andreas Färber
2014-08-02  0:52   ` Andreas Färber
2014-08-02 13:02   ` Tomasz Figa
2014-08-02 13:02     ` Tomasz Figa
2014-08-02 13:02     ` Tomasz Figa
2014-08-02 13:10     ` Andreas Färber
2014-08-02 13:10       ` Andreas Färber
2014-08-02  0:52 ` [PATCH v6 08/10] ARM: dts: Fix apparent GPIO typo in exynos5250-arndale Andreas Färber
2014-08-02  0:52   ` Andreas Färber
2014-08-02  0:52   ` Andreas Färber
2014-08-02  0:52 ` [PATCH v6 09/10] ARM: dts: Simplify USB3503 on exynos5250-arndale Andreas Färber
2014-08-02  0:52   ` Andreas Färber
2014-08-02  0:52   ` Andreas Färber
2014-08-02  0:52 ` [PATCH v6 10/10] ARM: dts: Add exynos5250-spring device tree Andreas Färber
2014-08-02  0:52   ` Andreas Färber
2014-08-02  0:52   ` Andreas Färber
2014-08-02 13:18   ` Tomasz Figa
2014-08-02 13:18     ` Tomasz Figa
2014-08-04 15:22   ` Doug Anderson
2014-08-04 15:22     ` Doug Anderson
2014-08-04 15:22     ` Doug Anderson
2014-08-04 17:31     ` Javier Martinez Canillas
2014-08-04 17:31       ` Javier Martinez Canillas
2014-08-04 17:31       ` Javier Martinez Canillas
2014-08-20 12:50     ` Andreas Färber
2014-08-20 12:50       ` Andreas Färber
2014-08-20 12:50       ` Andreas Färber
2014-08-02  2:34 ` [PATCH v6 00/10] ARM: dts: exynos: Prepare Spring Javier Martinez Canillas
2014-08-02  2:34   ` Javier Martinez Canillas
2014-08-02  4:57   ` Doug Anderson
2014-08-02  4:57     ` Doug Anderson
2014-08-02 10:25     ` Andreas Färber
2014-08-02 10:25       ` Andreas Färber
2014-08-02 13:13       ` Tomasz Figa [this message]
2014-08-02 13:13         ` Tomasz Figa
2014-08-02 16:05         ` Andreas Färber
2014-08-02 16:05           ` Andreas Färber
2014-08-04 15:42       ` Doug Anderson
2014-08-04 15:42         ` Doug Anderson
2014-08-04 17:43         ` Javier Martinez Canillas
2014-08-04 17:43           ` Javier Martinez Canillas
2014-08-07  8:40         ` Javier Martinez Canillas
2014-08-07  8:40           ` Javier Martinez Canillas

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=53DCE40F.10809@gmail.com \
    --to=tomasz.figa@gmail.com \
    --cc=afaerber@suse.de \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=javier.martinez@collabora.co.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=stephan@synkhronix.com \
    --cc=t.figa@samsung.com \
    --cc=vpalatin@chromium.org \
    /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.