On 07/09/2015 02:12 PM, Hans Verkuil wrote:
On 07/09/2015 01:48 PM, Jan Kara wrote:
Hello,
Hans, did you have a chance to look at these patches? I have tested them
with the vivid driver but it would be good if you could run them through
your standard testing procedure as well. Andrew has
On 07/13/2015 11:04 AM, Tobias Jakobi wrote:
Hello,
Andrzej Hajda wrote:
Hi Tobias,
On 07/12/2015 06:06 PM, Tobias Jakobi wrote:
Hello Andrzej!
Just some small comments.
It seems like linux-samsung-soc wasn't put into Cc for '[PATCH RESEND
0/6] drm/exynos: HDMI related fixes' (even
Hi,
On Tuesday, June 23, 2015 09:24:40 AM Krzysztof Kozlowski wrote:
On 23.06.2015 08:46, Krzysztof Kozlowski wrote:
On 23.06.2015 00:04, Michael Turquette wrote:
Quoting Kukjin Kim (2015-06-21 18:46:26)
Krzysztof Kozlowski wrote:
On 22.06.2015 10:38, Kukjin Kim wrote:
Krzysztof
Hello,
Andrzej Hajda wrote:
Hi Tobias,
On 07/12/2015 06:06 PM, Tobias Jakobi wrote:
Hello Andrzej!
Just some small comments.
It seems like linux-samsung-soc wasn't put into Cc for '[PATCH RESEND
0/6] drm/exynos: HDMI related fixes' (even though this series was),
maybe you should also
Dear Kukjin,
These are candidates for fixes during this RC cycle.
Description below (under signed tag).
Best regards,
Krzysztof
The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
are available in the git repository at:
On Monday, July 13, 2015 08:10:21 PM Krzysztof Kozlowski wrote:
2015-07-13 20:02 GMT+09:00 Bartlomiej Zolnierkiewicz
b.zolnier...@samsung.com:
Hi,
On Tuesday, June 23, 2015 09:24:40 AM Krzysztof Kozlowski wrote:
On 23.06.2015 08:46, Krzysztof Kozlowski wrote:
On 23.06.2015 00:04,
2015-07-13 20:20 GMT+09:00 Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com:
On Monday, July 13, 2015 08:10:21 PM Krzysztof Kozlowski wrote:
2015-07-13 20:02 GMT+09:00 Bartlomiej Zolnierkiewicz
b.zolnier...@samsung.com:
Hi,
On Tuesday, June 23, 2015 09:24:40 AM Krzysztof Kozlowski
2015-07-13 20:02 GMT+09:00 Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com:
Hi,
On Tuesday, June 23, 2015 09:24:40 AM Krzysztof Kozlowski wrote:
On 23.06.2015 08:46, Krzysztof Kozlowski wrote:
On 23.06.2015 00:04, Michael Turquette wrote:
Quoting Kukjin Kim (2015-06-21 18:46:26)
Commit 84f57d9e3685 (tty: serial/samsung: fix modular build) fixed
build issues when the driver was built as a module. One of those was
that printascii is only accessible when the driver is built-in.
But there is no need to check for defined(CONFIG_DEBUG_LL) since the
SERIAL_SAMSUNG_DEBUG Kconfig
Krzysztof Kozlowski wrote:
On 13.07.2015 20:18, Javier Martinez Canillas wrote:
Commit 84f57d9e3685 (tty: serial/samsung: fix modular build) fixed
build issues when the driver was built as a module. One of those was
that printascii is only accessible when the driver is built-in.
But
Krzysztof Kozlowski wrote:
On 14.07.2015 09: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
In my opinion since its something configurable by the board and not
SoC specific it should be defined (or re-defined) on the board dts.
If one makes a 5422 board booting from A15's that patch will be
already invalid and causing the issue that it fixes.
2015-07-14 2:04 GMT-03:00 Kukjin Kim
On Mon 13-07-15 10:45:25, Hans Verkuil wrote:
On 07/09/2015 02:12 PM, Hans Verkuil wrote:
On 07/09/2015 01:48 PM, Jan Kara wrote:
Hello,
Hans, did you have a chance to look at these patches? I have tested them
with the vivid driver but it would be good if you could run them through
Hello.
On 7/13/2015 10:42 AM, Javier Martinez Canillas wrote:
The MAX77802 is a chip that contains regulators, 2 32kHz clocks,
a RTC and an I2C interface to program the individual components.
The are already DT bindings for the regulators and clocks and
these reference to a
From: Jan Kara j...@suse.cz
Convert vb2_dc_get_userptr() to use frame vector infrastructure. When we
are doing that there's no need to allocate page array and some code can
be simplified.
Acked-by: Marek Szyprowski m.szyprow...@samsung.com
Tested-by: Marek Szyprowski m.szyprow...@samsung.com
From: Jan Kara j...@suse.cz
Provide simple helper functions to map virtual address range into an
array of pfns / pages.
Acked-by: Marek Szyprowski m.szyprow...@samsung.com
Tested-by: Marek Szyprowski m.szyprow...@samsung.com
Signed-off-by: Jan Kara j...@suse.cz
---
From: Jan Kara j...@suse.cz
Convert omap_vout_uservirt_to_phys() to use get_vaddr_pfns() instead of
hand made mapping of virtual address to physical address. Also the
function leaked page reference from get_user_pages() so fix that by
properly release the reference when omap_vout_buffer_release()
From: Jan Kara j...@suse.cz
Conversion to the use of pinned pfns made some functions unused. Remove
them. Also there's no need to lock mmap_sem in __buf_prepare() anymore.
Acked-by: Marek Szyprowski m.szyprow...@samsung.com
Tested-by: Marek Szyprowski m.szyprow...@samsung.com
Signed-off-by: Jan
From: Jan Kara j...@suse.cz
Convert g2d_userptr_get_dma_addr() to pin pages using get_vaddr_frames().
This removes the knowledge about vmas and mmap_sem locking from exynos
driver. Also it fixes a problem that the function has been mapping user
provided address without holding mmap_sem.
From: Jan Kara j...@suse.cz
Acked-by: Marek Szyprowski m.szyprow...@samsung.com
Tested-by: Marek Szyprowski m.szyprow...@samsung.com
Signed-off-by: Jan Kara j...@suse.cz
---
drivers/media/v4l2-core/videobuf2-dma-sg.c | 95 +-
1 file changed, 15 insertions(+), 80
From: Jan Kara j...@suse.cz
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 start belongs to a normal vma, the function
grabs reference to each of the pages to pin
On 07/13/2015 04:55 PM, Jan Kara wrote:
From: Jan Kara j...@suse.cz
Hello,
I'm sending the seventh version of my patch series to abstract vma handling
from the various media drivers. Since the previous version there are just
minor cleanups and fixes (see detailed changelog at the end of
Hello Sergei,
On 07/13/2015 03:11 PM, Sergei Shtylyov wrote:
Hello.
On 7/13/2015 10:42 AM, Javier Martinez Canillas wrote:
The MAX77802 is a chip that contains regulators, 2 32kHz clocks,
a RTC and an I2C interface to program the individual components.
The are already DT bindings for
On Monday, July 13, 2015 01:20:41 PM Bartlomiej Zolnierkiewicz wrote:
On Monday, July 13, 2015 08:10:21 PM Krzysztof Kozlowski wrote:
2015-07-13 20:02 GMT+09:00 Bartlomiej Zolnierkiewicz
b.zolnier...@samsung.com:
Hi,
On Tuesday, June 23, 2015 09:24:40 AM Krzysztof Kozlowski
From: Jan Kara j...@suse.cz
Hello,
I'm sending the seventh version of my patch series to abstract vma handling
from the various media drivers. Since the previous version there are just
minor cleanups and fixes (see detailed changelog at the end of the email).
After this patch set drivers have
From: Jan Kara j...@suse.cz
Convert vb2_vmalloc_get_userptr() to use frame vector infrastructure.
When we are doing that there's no need to allocate page array and some
code can be simplified.
Acked-by: Marek Szyprowski m.szyprow...@samsung.com
Tested-by: Marek Szyprowski
From: Jan Kara j...@suse.cz
Currently vb2 core acquires mmap_sem just around call to
__qbuf_userptr(). However since commit f035eb4e976ef5 (videobuf2: fix
lockdep warning) it isn't necessary to acquire it so early as we no
longer have to drop queue mutex before acquiring mmap_sem. So push
On 13.07.2015 20:18, Javier Martinez Canillas wrote:
Commit 84f57d9e3685 (tty: serial/samsung: fix modular build) fixed
build issues when the driver was built as a module. One of those was
that printascii is only accessible when the driver is built-in.
But there is no need to check for
Hello!
Andrzej Hajda wrote:
On 07/13/2015 11:04 AM, Tobias Jakobi wrote:
Hello,
Andrzej Hajda wrote:
Hi Tobias,
On 07/12/2015 06:06 PM, Tobias Jakobi wrote:
Hello Andrzej!
Just some small comments.
It seems like linux-samsung-soc wasn't put into Cc for '[PATCH RESEND
0/6]
On Sun, Jul 12, 2015 at 11:43 AM, Thomas Gleixner t...@linutronix.de wrote:
On Sun, 12 Jul 2015, Rob Herring wrote:
set_irq_flags is ARM specific with custom flags which have genirq
equivalents. Convert drivers to use the genirq interfaces directly, so we
can kill off set_irq_flags. The
On Tue, Jul 07, 2015 at 04:02:53PM -0400, Joel Porquet wrote:
The IRQCHIP_DECLARE macro migrated to 'include/linux/irqchip.h', making it
globally accessible.
See commit 91e20b5040c67c51aad88cf87db4305c5bd7f79d
(irqchip: Move IRQCHIP_DECLARE macro to include/linux/irqchip.h).
This patch
On 13.07.2015 23:27, Bartlomiej Zolnierkiewicz wrote:
On Monday, July 13, 2015 01:20:41 PM Bartlomiej Zolnierkiewicz wrote:
On Monday, July 13, 2015 08:10:21 PM Krzysztof Kozlowski wrote:
2015-07-13 20:02 GMT+09:00 Bartlomiej Zolnierkiewicz
b.zolnier...@samsung.com:
Hi,
On Tuesday, June
On 14.07.2015 09: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
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-cpus.dtsi
and
Hi Tobias,
On 07/12/2015 06:06 PM, Tobias Jakobi wrote:
Hello Andrzej!
Just some small comments.
It seems like linux-samsung-soc wasn't put into Cc for '[PATCH RESEND
0/6] drm/exynos: HDMI related fixes' (even though this series was),
maybe you should also forward the other series to this
The exynos-ppmu driver is only a clock consumer and not a clock provider
but its Device Tree binding listed #clock-cells as an optional property.
Signed-off-by: Javier Martinez Canillas jav...@osg.samsung.com
---
Documentation/devicetree/bindings/devfreq/event/exynos-ppmu.txt | 1 -
1 file
The regulator-compatible property from the regulator DT binding was
deprecated. But the max77686 DT binding doc still suggest to use it
instead of the regulator node name's which is the correct approach.
Signed-off-by: Javier Martinez Canillas jav...@osg.samsung.com
---
The MAX77802 is a chip that contains regulators, 2 32kHz clocks,
a RTC and an I2C interface to program the individual components.
The are already DT bindings for the regulators and clocks and
these reference to a bindings/mfd/max77802.txt file, that didn't
exist, for the details about the PMIC.
The Maxim MAX77686 PMIC is a multi-function device with regulators,
clocks and a RTC. The DT bindings for the clocks are in a separate
file but the bindings for the regulators are inside the mfd part.
To make it consistent with the clocks portion of the binding and
because is more natural to look
Hello Lee,
This series contains some improvements for the Device Tree bindings of
the Maxim MAX77686 and MAX77802 multi-function devices.
Patch #1 changes the max77686 binding to not suggest using a deprecated
property of the regulator DT binding.
Patch #2 adds a DT binding for the mfd portion
On 13.07.2015 16:42, Javier Martinez Canillas wrote:
The regulator-compatible property from the regulator DT binding was
deprecated. But the max77686 DT binding doc still suggest to use it
instead of the regulator node name's which is the correct approach.
Signed-off-by: Javier Martinez
On 13.07.2015 16:42, Javier Martinez Canillas wrote:
The MAX77802 is a chip that contains regulators, 2 32kHz clocks,
a RTC and an I2C interface to program the individual components.
The are already DT bindings for the regulators and clocks and
these reference to a bindings/mfd/max77802.txt
On 13.07.2015 16:42, Javier Martinez Canillas wrote:
The Maxim MAX77686 PMIC is a multi-function device with regulators,
clocks and a RTC. The DT bindings for the clocks are in a separate
file but the bindings for the regulators are inside the mfd part.
To make it consistent with the clocks
Hello Krzysztof,
Thanks a lot for the feedback.
On 07/13/2015 09:53 AM, Krzysztof Kozlowski wrote:
On 13.07.2015 16:42, Javier Martinez Canillas wrote:
The MAX77802 is a chip that contains regulators, 2 32kHz clocks,
a RTC and an I2C interface to program the individual components.
The are
Hello Krzysztof,
On 07/13/2015 10:03 AM, Krzysztof Kozlowski wrote:
On 13.07.2015 16:42, Javier Martinez Canillas wrote:
The Maxim MAX77686 PMIC is a multi-function device with regulators,
clocks and a RTC. The DT bindings for the clocks are in a separate
file but the bindings for the
45 matches
Mail list logo
