Tomasz Figa wrote:
All other platforms have this condition checked inside their own Kconfig
files, so for consistency this patch makes it this way for mach-s3c64xx
as well.
Signed-off-by: Tomasz Figa tomasz.f...@gmail.com
---
arch/arm/Kconfig | 2 --
Jungseok Lee wrote:
On Monday, September 30, 2013 12:04 PM, Sachin Kamat wrote:
On 30 September 2013 07:02, Jungseok Lee jays@samsung.com wrote:
+ /* turn off all power domains */
+ addr = of_iomap(np, 0) + 0x14;
+ __raw_writel(0x1, addr);
Actually my
Rahul Sharma wrote:
On 29 August 2013 19:05, Tomasz Figa t.f...@samsung.com wrote:
Hi Rahul,
On Thursday 29 of August 2013 19:22:51 Rahul Sharma wrote:
It adds Device tree nodes and clocks information for HDMI subsystem
for exynos5420 and exynos5250 SoCs. It adds pinctrl node for hdmi
This patch series adds a simple driver for the Samsung Exynos SoC
series DP transmitter PHY, using the generic PHY framework [1].
Previously the DP PHY used an internal DT node to control the PHY
power enable bit.
This PATCH v8 follows:
* PATCH v7, sent on August, 26th 2013
* PATCH v6, sent on
Add a PHY provider driver for the Samsung Exynos SoC Display Port PHY.
Signed-off-by: Jingoo Han jg1@samsung.com
Reviewed-by: Tomasz Figa t.f...@samsung.com
Cc: Sylwester Nawrocki s.nawro...@samsung.com
Acked-by: Felipe Balbi ba...@ti.com
---
.../devicetree/bindings/phy/samsung-phy.txt
Use the generic PHY API to control the DP PHY.
Signed-off-by: Jingoo Han jg1@samsung.com
Reviewed-by: Tomasz Figa t.f...@samsung.com
---
Documentation/devicetree/bindings/video/exynos_dp.txt | 17 +
drivers/video/exynos/exynos_dp_core.c | 16
Exynos Display Port can be used only for Exynos SoCs. In addition,
non-DT for EXYNOS SoCs is not supported from v3.11; thus, there is
no need to support non-DT for Exynos Display Port.
The 'include/video/exynos_dp.h' file has been used for non-DT
support and the content of file
Hi Mark Brown,
Please do let me know if you have any comments on this patch.
Regards,
Rajeshwari Shinde.
On Wed, Sep 25, 2013 at 4:59 PM, Rajeshwari Birje
rajeshwari.bi...@gmail.com wrote:
Hi Tomasz
Sorry for the previous mail with incomplete comments, sent the same by
mistake.
On Wed,
Hi Shaik,
I have a few questions regarding the selection part...
On 09/12/2013 03:09 PM, Shaik Ameer Basha wrote:
This patch adds the Makefile and memory to memory (m2m) interface
functionality for the SCALER driver.
Signed-off-by: Shaik Ameer Basha shaik.am...@samsung.com
---
diff --git a/Documentation/devicetree/bindings/media/samsung-s5k5baf.txt
b/Documentation/devicetree/bindings/media/samsung-s5k5baf.txt
new file mode 100644
index 000..7704a1e
--- /dev/null
+++ b/Documentation/devicetree/bindings/media/samsung-s5k5baf.txt
@@ -0,0 +1,58 @@
On 30 September 2013 12:55, Kukjin Kim kg...@kernel.org wrote:
I think current patch looks good to me, and in this case I don't have any
idea why we should macro for just one time usage.
It is not the question of one time usage, it is just to make the code
more readable.
--
With warm
On Monday 30 of September 2013 13:56:39 Sachin Kamat wrote:
On 30 September 2013 12:55, Kukjin Kim kg...@kernel.org wrote:
I think current patch looks good to me, and in this case I don't have
any idea why we should macro for just one time usage.
It is not the question of one time usage,
Hi Hans,
Thanks for pointing it out.
On Mon, Sep 30, 2013 at 1:38 PM, Hans Verkuil hverk...@xs4all.nl wrote:
Hi Shaik,
I have a few questions regarding the selection part...
On 09/12/2013 03:09 PM, Shaik Ameer Basha wrote:
This patch adds the Makefile and memory to memory (m2m) interface
On Mon, Sep 30, 2013 at 01:20:42AM +0200, Tomasz Figa wrote:
Mark will probably know better, but AFAIK there is no API for slave mode
SPI available in Linux kernel. Please correct me if I'm wrong.
That's correct.
The code mentioned in the post from your link was some internal vendor
code,
On 09/13/2013 02:56 PM, Sylwester Nawrocki wrote:
This patch adds ioctl helpers to the V4L2 mem-to-mem API, so we
can avoid several ioctl handlers in the mem-to-mem video node
drivers that are simply a pass-through to the v4l2_m2m_* calls.
These helpers will only be useful for drivers that use
On 09/13/2013 02:56 PM, Sylwester Nawrocki wrote:
Simplify the FIMC mem-to-mem driver by using the m2m ioctl and vb2 helpers.
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Signed-off-by: Kyugmin Park kyungmin.p...@samsung.com
Acked-by: Hans Verkuil hans.verk...@cisco.com
Regards,
On 09/13/2013 02:56 PM, Sylwester Nawrocki wrote:
Simplify the driver by using the m2m ioctl and vb2 helpers.
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Signed-off-by: Kyugmin Park kyungmin.p...@samsung.com
---
drivers/media/platform/mx2_emmaprp.c | 108
On 09/13/2013 02:56 PM, Sylwester Nawrocki wrote:
Simplify the driver by using the m2m ioctl and vb2 helpers.
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Signed-off-by: Kyugmin Park kyungmin.p...@samsung.com
Acked-by: Hans Verkuil hans.verk...@cisco.com
Regards,
Hans
On 09/13/2013 02:56 PM, Sylwester Nawrocki wrote:
Simplify the driver by using the m2m ioctl and vb2 helpers.
TODO: Add setting of default initial format.
So this patch can't be applied yet.
Other than that it looks good, but I won't ack it since it introduces a
regression
as long as the
Sachin Kamat wrote:
This has been done for Arndale board vide commit aa3edb65
(ARM: dts: Put Arndale fixed voltage regulators on a simple-bus).
Replicate here for consistency and correctness.
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
---
Based on Kukjin's for-next branch.
On 09/13/2013 02:56 PM, Sylwester Nawrocki wrote:
Simplify the driver by using the m2m ioctl and vb2 helpers.
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Signed-off-by: Kyugmin Park kyungmin.p...@samsung.com
Acked-by: Hans Verkuil hans.verk...@cisco.com
Regards,
Hans
On 09/13/2013 02:56 PM, Sylwester Nawrocki wrote:
Simplify the driver by using the m2m ioctl and vb2 helpers.
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Signed-off-by: Kyugmin Park kyungmin.p...@samsung.com
Acked-by: Hans Verkuil hans.verk...@cisco.com
Regards,
Hans
On 09/30/2013 11:32 AM, Shaik Ameer Basha wrote:
Hi Hans,
Thanks for pointing it out.
On Mon, Sep 30, 2013 at 1:38 PM, Hans Verkuil hverk...@xs4all.nl wrote:
Hi Shaik,
I have a few questions regarding the selection part...
On 09/12/2013 03:09 PM, Shaik Ameer Basha wrote:
This patch
Mike Turquette wrote:
Quoting Sylwester Nawrocki (2013-09-16 07:33:45)
On 09/12/2013 12:50 PM, Kukjin Kim wrote:
Well...I'm not sure changing to use macro is better or not at this
moment...
I think it is. ;) It's really less error prone to have symbolic names
instead
of the plain
Hi Hans,
On Mon, Sep 30, 2013 at 4:02 PM, Hans Verkuil hverk...@xs4all.nl wrote:
On 09/30/2013 11:32 AM, Shaik Ameer Basha wrote:
Hi Hans,
Thanks for pointing it out.
On Mon, Sep 30, 2013 at 1:38 PM, Hans Verkuil hverk...@xs4all.nl wrote:
Hi Shaik,
I have a few questions regarding the
On 30 August 2013 12:29, Rahul Sharma rahul.sha...@samsung.com wrote:
Exynos hdmiphy operations and configs are kept inside
the hdmi driver. Hdmiphy related code is tightly coupled
with hdmi IP driver.
This patche moves hdmiphy related code to hdmiphy driver.
It will help in cleanly
On Tue, Sep 24, 2013 at 1:38 PM, Lukasz Majewski l.majew...@samsung.com wrote:
The commit 4de0bdaa9677d11406c9becb70c60887c957e1f0
(thermal: exynos: Add support for instance based register/unregister)
broke check for presence of therm_dev at global thermal zone in
exynos_report_trigger().
On Mon, Sep 30, 2013 at 4:18 PM, Shaik Ameer Basha
shaik.sams...@gmail.com wrote:
Hi Hans,
On Mon, Sep 30, 2013 at 4:02 PM, Hans Verkuil hverk...@xs4all.nl wrote:
On 09/30/2013 11:32 AM, Shaik Ameer Basha wrote:
Hi Hans,
Thanks for pointing it out.
On Mon, Sep 30, 2013 at 1:38 PM, Hans
On Tue, Sep 24, 2013 at 1:38 PM, Lukasz Majewski l.majew...@samsung.com wrote:
Up till now Exynos5250 and Exynos4412 had the same definitions for TMU
data. Following commit changes that, by introducing separate
exynos4412_default_tmu_data structure.
Since Exynos4412 was chronologically first,
Hi,
On Tue, Sep 24, 2013 at 1:38 PM, Lukasz Majewski l.majew...@samsung.com wrote:
The commit d0a0ce3e77c795258d47f9163e92d5031d0c5221 (thermal: exynos: Add
missing definations and code cleanup) has removed setting of test MUX address
value at TMU configuration setting.
This field is not
On Tue, Sep 24, 2013 at 1:38 PM, Lukasz Majewski l.majew...@samsung.com wrote:
The TMU data definition is now separated to Exynos4412 and Exynos5250.
Now SOC_ARCH_EXYNOS only refers to Exynos5250. Hence the name
SOC_ARCH_EXYNOS has been changed to SOC_ARCH_EXYNOS5250.
Signed-off-by: Lukasz
On 09/19/2013 11:44 PM, Russell King wrote:
Replace the following sequence:
dma_set_mask(dev, mask);
dma_set_coherent_mask(dev, mask);
with a call to the new helper dma_set_mask_and_coherent().
Signed-off-by: Russell King rmk+ker...@arm.linux.org.uk
Acked-by: Hans Verkuil
On 09/30/2013 12:48 PM, Shaik Ameer Basha wrote:
Hi Hans,
On Mon, Sep 30, 2013 at 4:02 PM, Hans Verkuil hverk...@xs4all.nl wrote:
On 09/30/2013 11:32 AM, Shaik Ameer Basha wrote:
Hi Hans,
Thanks for pointing it out.
On Mon, Sep 30, 2013 at 1:38 PM, Hans Verkuil hverk...@xs4all.nl
On 09/27/2013 12:59 PM, Arun Kumar K wrote:
This patch adds the crucial hardware pipeline control for the
fimc-is driver. All the subdev nodes will call this pipeline
interfaces to reach the hardware. Responsibilities of this module
involves configuring and maintaining the hardware pipeline
On Mon, Sep 30, 2013 at 01:32:43PM +0530, Rajeshwari Birje wrote:
Please do let me know if you have any comments on this patch.
Don't top post. You need to follow Tomasz's advice and send the patch
to me (using the above address from get_maintainer.pl) after addressing
the issues he
Platform devices in the Linux kernel are usually managed by the DT
interface. This patch forms the base to support these kind of devices
with VFIO.
Signed-off-by: Antonios Motakis a.mota...@virtualopensystems.com
---
drivers/vfio/Kconfig | 11 +++
drivers/vfio/Makefile| 1 +
This is a workaround to make the VFIO_IOMMU_TYPE1 driver usable with
platform devices instead of PCI. A future permanent fix should support
both. This is required in order to use the Exynos SMMU, or ARM SMMU
driver with VFIO.
Signed-off-by: Antonios Motakis a.mota...@virtualopensystems.com
---
Signed-off-by: Antonios Motakis a.mota...@virtualopensystems.com
---
drivers/vfio/vfio_platform.c | 44
1 file changed, 44 insertions(+)
diff --git a/drivers/vfio/vfio_platform.c b/drivers/vfio/vfio_platform.c
index a0abcfa..6364316 100644
---
Update Documentation/vfio.txt with information regarding the device tree
based platform devices support.
What is still missing in this RFC series, is information on how to bind
the driver to platform devices, as there is currently for PCI. This will
be added when proper VFIO driver binding is
VFIO returns a file descriptor which we can use to manipulate the memory
regions of the device. Since some memory regions we cannot mmap due to
security concerns, we also allow to read and write to this file descriptor
directly.
Signed-off-by: Antonios Motakis a.mota...@virtualopensystems.com
---
A VFIO userspace driver will start by opening the VFIO device
that corresponds to an IOMMU group, and will use the ioctl interface
to get the basic device info, such as number of memory regions and
interrupts, and their properties.
This patch implements the IOCTLs:
- VFIO_DEVICE_GET_INFO
-
This is a preview of the base work, towards VFIO support on ARM platforms
with an IOMMU. It forms a base on to which to implement the functionality
necessary to enable using device tree devices on ARM (and other platforms
based on device trees) with VFIO.
This patch series has been subjected to
-Original Message-
From: iommu-boun...@lists.linux-foundation.org [mailto:iommu-
boun...@lists.linux-foundation.org] On Behalf Of Antonios Motakis
Sent: Monday, September 30, 2013 8:59 PM
To: kvm...@lists.cs.columbia.edu; alex.william...@redhat.com
Cc:
-Original Message-
From: iommu-boun...@lists.linux-foundation.org [mailto:iommu-
boun...@lists.linux-foundation.org] On Behalf Of Antonios Motakis
Sent: Monday, September 30, 2013 8:59 PM
To: kvm...@lists.cs.columbia.edu; alex.william...@redhat.com
Cc:
Tomasz,
On Sat, Sep 28, 2013 at 6:49 PM, Tomasz Figa tomasz.f...@gmail.com wrote:
On Fri, Sep 27, 2013 at 11:14 AM, Tomasz Figa tomasz.f...@gmail.com
wrote:
So isn't the register in the PMU there to save power in the case that
the watchdog timer isn't being used? How is the PMU driver to
Doug,
On Monday 30 of September 2013 09:54:33 Doug Anderson wrote:
Tomasz,
On Sat, Sep 28, 2013 at 6:49 PM, Tomasz Figa tomasz.f...@gmail.com wrote:
On Fri, Sep 27, 2013 at 11:14 AM, Tomasz Figa tomasz.f...@gmail.com
wrote:
So isn't the register in the PMU there to save power in the
On Mon, 2013-09-30 at 17:28 +0200, Antonios Motakis wrote:
The VFIO documentation is slightly out of date. This minor correction
replaces references to VFIO_IOMMU_X86 with the correct reference to
VFIO_IOMMU_TYPE1
Signed-off-by: Antonios Motakis a.mota...@virtualopensystems.com
---
On Mon, 2013-09-30 at 17:28 +0200, Antonios Motakis wrote:
This is a workaround to make the VFIO_IOMMU_TYPE1 driver usable with
platform devices instead of PCI. A future permanent fix should support
both. This is required in order to use the Exynos SMMU, or ARM SMMU
driver with VFIO.
On Mon, 2013-09-30 at 17:28 +0200, Antonios Motakis wrote:
A VFIO userspace driver will start by opening the VFIO device
that corresponds to an IOMMU group, and will use the ioctl interface
to get the basic device info, such as number of memory regions and
interrupts, and their properties.
On Mon, 2013-09-30 at 17:28 +0200, Antonios Motakis wrote:
This is a preview of the base work, towards VFIO support on ARM platforms
with an IOMMU. It forms a base on to which to implement the functionality
necessary to enable using device tree devices on ARM (and other platforms
based on
On Mon, 2013-09-30 at 17:28 +0200, Antonios Motakis wrote:
Platform devices in the Linux kernel are usually managed by the DT
interface. This patch forms the base to support these kind of devices
with VFIO.
Signed-off-by: Antonios Motakis a.mota...@virtualopensystems.com
---
On Sunday, September 29, 2013 11:29 AM, Wei Yongjun wrote:
From: Wei Yongjun yongjun_...@trendmicro.com.cn
Add the missing clk_disable_unprepare() before return
from exynos_pcie_probe() in the error handling case.
Signed-off-by: Wei Yongjun yongjun_...@trendmicro.com.cn
Acked-by: Jingoo
From: Sachin Kamat sachin.ka...@linaro.org
Updated I2C nodes for HDMI-DDC and HDMI-PHY for Arndale board.
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
---
arch/arm/boot/dts/exynos5250-arndale.dts | 20 +++-
1 file
-Original Message-
From: Sylwester Nawrocki [mailto:sylvester.nawro...@gmail.com]
Sent: Monday, September 30, 2013 7:09 AM
To: Inki Dae
Cc: Rahul Sharma; devicet...@vger.kernel.org; linux-samsung-soc;
sw0312.kim; sunil joshi; dri-devel; kgene.kim; Shirish S; Sylwester
Nawrocki;
-Original Message-
From: linux-samsung-soc-ow...@vger.kernel.org [mailto:linux-samsung-soc-
ow...@vger.kernel.org] On Behalf Of Tomasz Figa
Sent: Monday, September 30, 2013 8:13 AM
To: Sylwester Nawrocki
Cc: Inki Dae; Rahul Sharma; devicet...@vger.kernel.org; linux-samsung-soc;
Hi,
On Sunday 29 September 2013 12:57 AM, Sylwester Nawrocki wrote:
Add PHY provider node for the MIPI CSIS and MIPI DSIM PHYs.
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
Acked-by: Felipe Balbi ba...@ti.com
Can this
56 matches
Mail list logo
