Hi,
On Mon, Jun 1, 2015 at 9:24 AM, Krzysztof Kozlowski
k.kozlow...@samsung.com wrote:
On 31.05.2015 23:34, Chanho Park wrote:
The odroid-xu3 board which is based on exynos5422 not exynos5800 is
booted from cortex-a7 core unlike exynos5800. The odroid-xu3's cpu order
is quite strange. cpu0
One should not do any assumptions on the stare of the fimd hardware
during driver initialization, so to properly reset fimd before enabling
IOMMU, one should ensure that all power domains and clocks are really
enabled. This patch adds calls to power on/off in the
fimd_clear_channel() function to
This patch adds code, which detach sub-device nodes from default iommu
domain if such has been configured. This lets Exynos DRM driver to properly
attach sub-devices to its own, common for all sub-devices domain.
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
Tested-by: Javier Martinez
On 06/01/2015 02:40 PM, Jan Kara wrote:
On Thu 28-05-15 16:24:02, Andrew Morton wrote:
On Wed, 13 May 2015 15:08:08 +0200 Jan Kara j...@suse.cz wrote:
Provide new function get_vaddr_frames(). This function maps virtual
addresses from given start and fills given array with page frame numbers
W dniu 01.06.2015 o 19:10, Marek Szyprowski pisze:
Hello,
Main changes for Exynos SYSMMU (IOMMU) driver has been finally scheduled
for merging - see
https://git.kernel.org/cgit/linux/kernel/git/joro/iommu.git/commit/?h=next
In meantime there have been quite a lot of changes related to
The odroid-xu3 board which is based on exynos5422 not exynos5800 is
booted from cortex-a7 core unlike exynos5800. The odroid-xu3's cpu order
is quite strange. cpu0 and cpu5-7 are cortex-a7 cores and cpu1-4 are
cortex-a15 cores. To correct this mis-odering, I added exynos5422.dtsi
and reversing cpu
Hi,
On Friday 29 May 2015 08:34 PM, Felipe Balbi wrote:
Hi,
On Fri, May 29, 2015 at 05:04:38PM +0530, Kishon Vijay Abraham I wrote:
Hi Felipe,
On Wednesday 27 May 2015 12:09 AM, Felipe Balbi wrote:
On Tue, May 26, 2015 at 11:37:17AM -0700, Arun Ramamurthy wrote:
Hi
On 15-05-26 07:19 AM,
On Thu 28-05-15 16:24:02, Andrew Morton wrote:
On Wed, 13 May 2015 15:08:08 +0200 Jan Kara j...@suse.cz wrote:
Provide new function get_vaddr_frames(). This function maps virtual
addresses from given start and fills given array with page frame numbers of
the corresponding pages. If given
Yeah, completely agree with Linus on the visibility problem and that's
exactly the reason why we don't include stdint.h in the kernel header
and expect userspace to define the ISO types somewhere.
But using the types from include/linux/types.h and especially
including it into the uapi headers
On Mon, Jun 01, 2015 at 11:08:21AM +0200, Christian König wrote:
Yeah, completely agree with Linus on the visibility problem and that's
exactly the reason why we don't include stdint.h in the kernel header and
expect userspace to define the ISO types somewhere.
But using the types from
This patch adds System MMU nodes to all defined devices that are specific
to Exynos5250 series.
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
Acked-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
arch/arm/boot/dts/exynos5250.dtsi | 250 ++
1
This patch adds System MMU nodes to the devices that are specific to
Exynos3250 series.
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
Acked-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
arch/arm/boot/dts/exynos3250.dtsi | 33 +
1 file changed, 33
Hello,
Main changes for Exynos SYSMMU (IOMMU) driver has been finally scheduled
for merging - see
https://git.kernel.org/cgit/linux/kernel/git/joro/iommu.git/commit/?h=next
In meantime there have been quite a lot of changes related to Exynos DTS
files queued for merging and my patches don't apply
This patch adds System MMU nodes that are specific to Exynos4210/4x12 series.
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
Acked-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
arch/arm/boot/dts/exynos4.dtsi| 118 ++
SYSMMU devices are registered very early in arch_initcall, so ensure
that they can get access to power domains by registering power domain
driver from earlier initcall. This change requires dropping usage of the
platform device associated with each power domain and replacing clock
calls with
This patch adds System MMU nodes to all defined devices that are specific
to Exynos4415 series.
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
Acked-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
arch/arm/boot/dts/exynos4415.dtsi | 11 +++
1 file changed, 11 insertions(+)
This patch adds System MMU nodes to all defined devices that are specific
to Exynos5420/5800/5422 series.
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
Acked-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
arch/arm/boot/dts/exynos5420.dtsi | 183
On Mon, Jun 1, 2015 at 11:08 AM, Christian König
christian.koe...@amd.com wrote:
Yeah, completely agree with Linus on the visibility problem and that's
exactly the reason why we don't include stdint.h in the kernel header and
expect userspace to define the ISO types somewhere.
But using the
On 30.05.2015 18:46, Russell King - ARM Linux wrote:
On Sat, May 30, 2015 at 05:37:57PM +0200, Mikko Rapeli wrote:
Fixes userspace compilation error:
drm/exynos_drm.h:30:2: error: unknown type name ‘uint64_t’
Signed-off-by: Mikko Rapeli mikko.rap...@iki.fi
This is another thing which we need
On 01.06.2015 11:38, Russell King - ARM Linux wrote:
On Mon, Jun 01, 2015 at 11:08:21AM +0200, Christian König wrote:
Yeah, completely agree with Linus on the visibility problem and that's
exactly the reason why we don't include stdint.h in the kernel header and
expect userspace to define the
On Mon, Jun 01, 2015 at 10:20:10AM +0200, Christian König wrote:
Using types that differs on 32-bit and 64-bit machines for a kernel
interface is indeed a rather bad idea. This not only includes longs, but
pointers as well.
[cut standard stdint.h types argument which we've heard before]
You
On Mon, Jun 01, 2015 at 10:20:10AM +0200, Christian König wrote:
Additional to that linux/types.h is not part of the uapi as far as
I know, so including it in a header which is part of the uapi should
be forbidden.
linux/types.h is part of uapi. See usr/include after 'make headers_install'.
Hello,
as pointed out in [1] before, this gives me an kernel oops during boot.
With best wishes,
Tobias
[1] http://www.spinics.net/lists/linux-samsung-soc/msg44736.html
On 2015-06-01 17:04, Gustavo Padovan wrote:
From: Joonyoung Shim jy0922.s...@samsung.com
Handle changes by removing copy
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
PageFlips now use the atomic helper to work through the atomic modesetting
API. Async page flips are not supported yet.
v2: Add .atomic_begin() step to handle the vblank part we removed from
exynos page_flip code.
Signed-off-by: Gustavo
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Now that no one is using the functions exported by exynos_drm_plane due
to the atomic conversion we can make remove some of the them or make them
static.
v2: remove unused exynos_drm_crtc
v3: fix checkpatch error (reported by Joonyoung)
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Now that phase 1 and 2 are complete we can switch the update/disable_plane
callbacks to their atomic version.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
Reviewed-by: Joonyoung Shim jy0922.s...@samsung.com
Tested-by: Tobias
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Now that phase 1 and 2 are complete switch .set_config helper to
use the atomic one.
v2: also remove .prepare() callback
v3: remove .mode_set() and .mode_set_base() and encoder's
.prepare() callbacks
Signed-off-by: Gustavo Padovan
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
exynos needs to update planes with the crtc enabled (mainly for the FIMD
case) so this specific atomic commit changes the order of
drm_atomic_helper_commit_modeset_enables() and
drm_atomic_helper_commit_planes() to commit planes after we
From: Joonyoung Shim jy0922.s...@samsung.com
The exynos_update_plane function needs 16.16 fixed point source data.
Signed-off-by: Joonyoung Shim jy0922.s...@samsung.com
Reviewed-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 7 ---
1 file
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Use drm_atomic_set_fb_for_plane() in the legacy page_flip path to keep
track of the framebuffer pointer and reference.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
Reviewed-by: Joonyoung Shim jy0922.s...@samsung.com
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
The new atomic infrastructure needs the .mode_set_nofb() callback to
update CRTC timings before setting any plane.
v2: remove WARN_ON(!crtc-state) from mode_set_nofb
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
Reviewed-by:
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
This is a preparation commit to move exynos_drm_crtc_disable() together
with the future exynos_drm_crtc_enable() that will come from the split of
exynos_drm_crtc_dpms() callback.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
The atomic helper to disable planes also uses the optional
.atomic_disable() helper. The unique operation it does is calling
.win_disable()
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
Reviewed-by: Joonyoung Shim
From: Joonyoung Shim jy0922.s...@samsung.com
Handle changes by removing copy from adjusted_mode to mode as using
adjusted_mode of crtc_state.
Signed-off-by: Joonyoung Shim jy0922.s...@samsung.com
---
drivers/gpu/drm/exynos/exynos7_drm_decon.c | 4 ++--
drivers/gpu/drm/exynos/exynos_drm_fimd.c
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Hi,
Here goes the full support for atomic modesetting on exynos. I've
split the patches in the various phases of atomic support.
v2: fixes comments by Joonyoung
- remove unused var in patch 09
- use -disable instead of
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
The planes are already disabled by the drm_atomic_helper_commit() code
so we don't need to disable the in these two places.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
Reviewed-by: Joonyoung Shim jy0922.s...@samsung.com
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
To follow more closely the new atomic API we split the dpms()
helper into the enable() and disable() helper to get exactly the
same semantics.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
On Monday 01 June 2015 09:56:57 Krzysztof Kozlowski wrote:
Fix for Exynos3250 RTC wake-up interrupts after converting PMU
wakeup to stacked domains. This allows waking up the device from
suspend to RAM using S3C RTC driver (the RTC on SoC).
The patch should be applied some time ago,
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Run dpms operations through the atomic intefaces. This basically removes
the .dpms() callback from econders and crtcs and use .disable() and
.enable() to turn the crtc on and off.
v2: Address comments by Joonyoung:
- make hdmi code
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Set CRTC, planes and connectors to use the default implementations from
the atomic helper library. The helpers will work to keep track of state
for each DRM object.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
Reviewed-by:
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Rip out the check from exynos_update_plane() and create
exynos_check_plane() for the check phase enabling use to use
the atomic helpers to call our check and update phases when updating
planes.
Update all users of exynos_update_plane()
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Everything starts disabled so we don't really need to disable anything.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
Reviewed-by: Joonyoung Shim jy0922.s...@samsung.com
Tested-by: Tobias Jakobi tjak...@math.uni-bielefeld.de
On Mon, Jun 01, 2015 at 06:22:41PM +0530, Kishon Vijay Abraham I wrote:
Hi,
On Friday 29 May 2015 08:34 PM, Felipe Balbi wrote:
Hi,
On Fri, May 29, 2015 at 05:04:38PM +0530, Kishon Vijay Abraham I wrote:
Hi Felipe,
On Wednesday 27 May 2015 12:09 AM, Felipe Balbi wrote:
On Tue, May 26,
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.
On Monday 01 June 2015 09:09:00 Tina Ruchandani wrote:
@@ -1518,10 +1519,11 @@ static int ipp_send_event(struct exynos_drm_ippdrv
*ippdrv,
e = list_first_entry(c_node-event_list,
struct drm_exynos_ipp_send_event, base.link);
- do_gettimeofday(now);
-
On Monday 01 June 2015 08:36:18 Tina Ruchandani wrote:
- do_gettimeofday(now);
+ getnstimeofday64(now);
e-event.tv_sec = now.tv_sec;
- e-event.tv_usec = now.tv_usec;
+ e-event.tv_usec = (now.tv_nsec / NSEC_PER_USEC);
e-event.cmdlist_no = cmdlist_no;
2015-06-02 4:12 GMT+09:00 Ben Gamari b...@smart-cactus.org:
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.
(...)
Worse, the few patches
that have been submitted for the 5410 have
On 01.06.2015 21:24, Chanho Park wrote:
The odroid-xu3 board which is based on exynos5422 not exynos5800 is
booted from cortex-a7 core unlike exynos5800. The odroid-xu3's cpu order
is quite strange. cpu0 and cpu5-7 are cortex-a7 cores and cpu1-4 are
cortex-a15 cores. To correct this
On 06/02/2015 12:09 AM, Tobias Jakobi wrote:
Hello,
as pointed out in [1] before, this gives me an kernel oops during boot.
With best wishes,
Tobias
[1] http://www.spinics.net/lists/linux-samsung-soc/msg44736.html
Yeah, this patch should go after switched by drm_helper_crtc_mode_set,
Chanho == Chanho Park parkc...@gmail.com writes:
Chanho The odroid-xu3 board which is based on exynos5422 not
Chanho exynos5800 is booted from cortex-a7 core unlike
Chanho exynos5800. The odroid-xu3's cpu order is quite strange. cpu0
Chanho and cpu5-7 are cortex-a7 cores and cpu1-4 are
Krzysztof Kozlowski wrote:
Dear Kukjin,
Quite big set of changes, mostly refactor.
You can find them also on the lists with my reviewed-by.
Thanks for your gentle reminder and gathering.
I'm sorting them out and it should be fine tonight in my tree...
If any differences with yours, I'll
51 matches
Mail list logo
