public inbox for linux-samsung-soc@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Gamari <ben@smart-cactus.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
	Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	Krzysztof Kozlowski <k.kozlowski.k@gmail.com>
Cc: linux-samsung-soc@vger.kernel.org,
	Joonyoung Shim <jy0922.shim@samsung.com>,
	Seung-Woo Kim <sw0312.kim@samsung.com>,
	Inki Dae <inki.dae@samsung.com>, Kukjin Kim <kgene@kernel.org>,
	Javier Martinez Canillas <javier@dowhile0.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Exynos 5410 support (was [PATCH 6/6] ARM: dts: exynos5420: add sysmmu nodes)
Date: Mon, 01 Jun 2015 15:12:24 -0400	[thread overview]
Message-ID: <556CAE98.1080906@smart-cactus.org> (raw)
In-Reply-To: <1433153450-3680-7-git-send-email-m.szyprowski@samsung.com>

On 06/01/2015 06:10 AM, Marek Szyprowski wrote:
> This patch adds System MMU nodes to all defined devices that are specific
> to Exynos5420/5800/5422 series.

Apologies in advance if Thunderbird mangles this message; my usual mail 
configuration has suffered an unfortunate run-in with a mug of tea.

As someone who has devoted a few weekends trying to make the mainline 
kernel usable on an Odroid XU2, I can't help but notice that nearly 
every patchset that has hit this list recently excludes the Exynos 541x 
devices, including series which appear to go out of their way to support 
older devices. I would attribute this to the lack of publicly accessible 
documentation, but many of these patches are coming from Samsung 
employees.  Worse, the few patches that have been submitted for the 5410 
have languished in queue-purgatory. What is going on with support for 
this silicon?

These devices really aren't that old but if Samsung insists that they 
aren't worth putting engineering time towards then perhaps they could at 
least release documentation? The Hardkernel folks are on the record[2] 
as saying there was a document under review. Perhaps this document could 
be quickly trimmed into a disclosable state? Even a quick-and-dirty 
documentation release would help my efforts substantially.

Cheers,

- Ben


[1] https://github.com/bgamari/linux/commits/odroid-3.19
[2] http://forum.odroid.com/viewtopic.php?f=65&t=1932#p20457

  reply	other threads:[~2015-06-01 19:12 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 13:20 [PATCH v7 00/25] Exynos SYSMMU (IOMMU) integration with DT and DMA-mapping subsystem Marek Szyprowski
2015-05-19 13:20 ` [PATCH v7 01/25] drm/exynos: iommu: detach from default dma-mapping domain on init Marek Szyprowski
2015-05-19 13:20 ` [PATCH v7 02/25] drm/exynos: fimd: ensure proper hw state in fimd_clear_channel() Marek Szyprowski
2015-05-19 13:20 ` [PATCH v7 03/25] iommu: Init iommu-groups support earlier, in core_initcall Marek Szyprowski
     [not found]   ` <1432041645-11172-4-git-send-email-m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-05-23 16:23     ` Laurent Pinchart
2015-05-25  7:28       ` Marek Szyprowski
2015-05-29  8:33       ` Joerg Roedel
2015-05-19 13:20 ` [PATCH v7 04/25] iommu/exynos: Don't read version register on every tlb operation Marek Szyprowski
2015-05-19 13:20 ` [PATCH v7 05/25] iommu/exynos: Remove unused functions Marek Szyprowski
2015-05-19 13:20 ` [PATCH v7 06/25] iommu/exynos: Remove useless members from exynos_iommu_owner structure Marek Szyprowski
2015-05-19 13:20 ` [PATCH v7 07/25] iommu/exynos: Refactor function parameters to simplify code Marek Szyprowski
2015-05-19 13:20 ` [PATCH v7 08/25] iommu/exynos: Rename variables to reflect their purpose Marek Szyprowski
2015-05-19 13:20 ` [PATCH v7 09/25] iommu/exynos: Use struct exynos_iommu_domain in internal structures Marek Szyprowski
2015-05-19 13:20 ` [PATCH v7 10/25] iommu/exynos: Remove excessive includes and sort others alphabetically Marek Szyprowski
2015-05-19 13:20 ` [PATCH v7 11/25] iommu/exynos: Document internal structures Marek Szyprowski
2015-05-19 13:20 ` [PATCH v7 12/25] iommu/exynos: Add/remove callbacks should fail if no iommu is available Marek Szyprowski
2015-05-19 13:20 ` [PATCH v7 13/25] iommu/exynos: Add support for binding more than one sysmmu to master device Marek Szyprowski
2015-05-19 13:20 ` [PATCH v7 14/25] iommu/exynos: Add support for runtime_pm Marek Szyprowski
2015-05-19 13:20 ` [PATCH v7 15/25] iommu/exynos: Add system suspend/resume support Marek Szyprowski
2015-05-19 13:20 ` [PATCH v7 16/25] iommu/exynos: Init from dt-specific callback instead of initcall Marek Szyprowski
2015-05-19 13:20 ` [PATCH v7 17/25] iommu/exynos: Add callback for initializing devices from device tree Marek Szyprowski
2015-05-19 13:20 ` [PATCH v7 18/25] ARM: Exynos: pm_domains: register power domain driver from core_initcall Marek Szyprowski
2015-05-20  0:51   ` Krzysztof Kozlowski
     [not found] ` <1432041645-11172-1-git-send-email-m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-05-19 13:20   ` [PATCH v7 19/25] ARM: dts: exynos4: add sysmmu nodes Marek Szyprowski
2015-05-29  8:52   ` [PATCH v7 00/25] Exynos SYSMMU (IOMMU) integration with DT and DMA-mapping subsystem Joerg Roedel
2015-05-19 13:20 ` [PATCH v7 20/25] ARM: dts: exynos3250: add sysmmu nodes Marek Szyprowski
2015-05-19 13:20 ` [PATCH v7 21/25] ARM: dts: exynos4415: " Marek Szyprowski
2015-05-19 13:20 ` [PATCH v7 22/25] ARM: dts: exynos5250: " Marek Szyprowski
2015-05-19 13:20 ` [PATCH v7 23/25] ARM: dts: exynos5420: " Marek Szyprowski
2015-05-19 13:20 ` [PATCH v7 24/25] ARM: DMA-mapping: add support for creating reserved mappings in iova space Marek Szyprowski
2015-05-19 13:20 ` [PATCH v7 25/25] ARM: dts: exynos: add iommu reserved regions for bootloader's splash screen Marek Szyprowski
2015-05-20  7:31 ` [PATCH v7 00/25] Exynos SYSMMU (IOMMU) integration with DT and DMA-mapping subsystem Javier Martinez Canillas
2015-05-23  3:56   ` [PATCH v7 00/25] Exynos SYSMMU (IOMMU) integration with DT andDMA-mapping subsystem Kukjin Kim
2015-05-28 23:54     ` Krzysztof Kozlowski
2015-06-01 10:10 ` [PATCH 0/6] Exynos SYSMMU (IOMMU) dts and arch updates Marek Szyprowski
2015-06-01 10:10   ` [PATCH 1/6] ARM: Exynos: pm_domains: register power domain driver from core_initcall Marek Szyprowski
2015-06-01 10:10   ` [PATCH 2/6] ARM: dts: exynos4: add sysmmu nodes Marek Szyprowski
2015-06-01 10:10   ` [PATCH 3/6] ARM: dts: exynos3250: " Marek Szyprowski
2015-06-01 10:10   ` [PATCH 4/6] ARM: dts: exynos4415: " Marek Szyprowski
2015-06-01 10:10   ` [PATCH 5/6] ARM: dts: exynos5250: " Marek Szyprowski
2015-06-01 10:10   ` [PATCH 6/6] ARM: dts: exynos5420: " Marek Szyprowski
2015-06-01 19:12     ` Ben Gamari [this message]
2015-06-01 23:51       ` Exynos 5410 support (was [PATCH 6/6] ARM: dts: exynos5420: add sysmmu nodes) Krzysztof Kozłowski
2015-06-02  8:13         ` Ben Gamari
2015-06-02  8:26           ` Krzysztof Kozłowski
2015-06-04 19:28       ` Ben Gamari
2015-06-01 11:34   ` [PATCH 0/6] Exynos SYSMMU (IOMMU) dts and arch updates Krzysztof Kozlowski
2015-06-03 23:11     ` Kukjin Kim
2015-06-04  3:51       ` Krzysztof Kozlowski
2015-06-04  6:10         ` Krzysztof Kozlowski

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=556CAE98.1080906@smart-cactus.org \
    --to=ben@smart-cactus.org \
    --cc=inki.dae@samsung.com \
    --cc=javier@dowhile0.org \
    --cc=jy0922.shim@samsung.com \
    --cc=k.kozlowski.k@gmail.com \
    --cc=k.kozlowski@samsung.com \
    --cc=kgene@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=sw0312.kim@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox