Hi Grant,
I observe the following boot failure with today's (next-20140220) linux-next
tree on Exynos based boards with the default exynos_defconfig.
Uncompressing Linux... done, booting the kernel.
[0.00] Booting Linux on physical CPU 0x900
[0.00] Linux version 3.14.0-rc3-next
On Tue, Feb 18, 2014 at 12:06 PM, John Stultz john.stu...@linaro.org wrote:
On Tue, Feb 18, 2014 at 12:00 PM, Olof Johansson o...@lixom.net wrote:
On Tue, Feb 18, 2014 at 11:52 AM, John Stultz john.stu...@linaro.org wrote:
On Tue, Feb 18, 2014 at 10:13 AM, Arnd Bergmann a...@arndb.de wrote:
On
On Thu, Feb 20, 2014 at 02:09:08PM +0530, Sachin Kamat wrote:
Hi Grant,
I observe the following boot failure with today's (next-20140220) linux-next
tree on Exynos based boards with the default exynos_defconfig.
Does this help?
diff --git a/drivers/of/base.c b/drivers/of/base.c
index
Hi Kevin,
On 20 February 2014 15:42, Kevin Hao haoke...@gmail.com wrote:
On Thu, Feb 20, 2014 at 02:09:08PM +0530, Sachin Kamat wrote:
Hi Grant,
I observe the following boot failure with today's (next-20140220) linux-next
tree on Exynos based boards with the default exynos_defconfig.
Does
On Thu, Feb 20, 2014 at 03:57:07PM +0530, Sachin Kamat wrote:
Hi Kevin,
On 20 February 2014 15:42, Kevin Hao haoke...@gmail.com wrote:
On Thu, Feb 20, 2014 at 02:09:08PM +0530, Sachin Kamat wrote:
Hi Grant,
I observe the following boot failure with today's (next-20140220)
linux-next
the following boot failure with today's (next-20140220)
linux-next
tree on Exynos based boards with the default exynos_defconfig.
Does this help?
The below patch works for me. Thanks for the fix.
Thanks Sachin.
Hi Grant,
I assume you would fold this change into the original patch
On Thu, Feb 20, 2014 at 09:03:30AM +, Olof Johansson wrote:
So, after giving this some more thought (and getting my hands dirty in
some of this code), I think I'm going to change my mind on this. For
mobile platforms I think it might make sense to bring over the
toplevel platform Kconfig
On Thu, Feb 20, 2014 at 8:39 AM, Sachin Kamat sachin.ka...@linaro.org wrote:
Hi Grant,
I observe the following boot failure with today's (next-20140220) linux-next
tree on Exynos based boards with the default exynos_defconfig.
Ugh, nested locking. that is not good. Kevin's patch looks correct
On Thu, 20 Feb 2014 18:12:40 +0800, Kevin Hao haoke...@gmail.com wrote:
On Thu, Feb 20, 2014 at 02:09:08PM +0530, Sachin Kamat wrote:
Hi Grant,
I observe the following boot failure with today's (next-20140220) linux-next
tree on Exynos based boards with the default exynos_defconfig
On Thursday 20 February 2014 11:22:48 Catalin Marinas wrote:
I'm fine with this. Do we still need something for ARMv8 server
platforms like ARCH_ARM_SBSA? The only advantage would be to make it
easier for mobile targeted kernel builds to disable server features but
I'm not sure there are so
[adding DT ML and DT maintainers on Cc for some discussion]
On 20.02.2014 05:14, Sachin Kamat wrote:
Hi Tomasz,
On 19 February 2014 18:15, Tomasz Figa t.f...@samsung.com wrote:
Hi Sachin,
[adding linux-arm-kernel ML to CC list]
On 19.02.2014 12:34, Sachin Kamat wrote:
To avoid modifying
On Thursday 20 February 2014, Tomasz Figa wrote:
On 20.02.2014 05:14, Sachin Kamat wrote:
Hi Tomasz,
On 19 February 2014 18:15, Tomasz Figa t.f...@samsung.com wrote:
Hi Sachin,
[adding linux-arm-kernel ML to CC list]
On 19.02.2014 12:34, Sachin Kamat wrote:
To avoid
On Thu, Feb 20, 2014 at 3:22 AM, Catalin Marinas
catalin.mari...@arm.com wrote:
On Thu, Feb 20, 2014 at 09:03:30AM +, Olof Johansson wrote:
So, after giving this some more thought (and getting my hands dirty in
some of this code), I think I'm going to change my mind on this. For
mobile
On 20.02.2014 18:00, Arnd Bergmann wrote:
On Thursday 20 February 2014, Tomasz Figa wrote:
On 20.02.2014 05:14, Sachin Kamat wrote:
Hi Tomasz,
On 19 February 2014 18:15, Tomasz Figa t.f...@samsung.com wrote:
Hi Sachin,
[adding linux-arm-kernel ML to CC list]
On 19.02.2014 12:34, Sachin
On Thursday 20 February 2014 18:34:23 Tomasz Figa wrote:
On 20.02.2014 18:00, Arnd Bergmann wrote:
Of course nothing stops you from retaining more specific compatible
strings. In fact, this is probably the most appropriate solution,
because in future you might find out that certain SoCs
On 19/02/14 18:47, Mark Rutland wrote:
On Tue, Feb 18, 2014 at 03:43:11PM +, Sylwester Nawrocki wrote:
On 22/12/13 22:27, Sylwester Nawrocki wrote:
This patch adds DT binding documentation for the Samsung S5K6A3(YX)
raw image sensor.
Signed-off-by: Sylwester Nawrocki
On Thu, Feb 20, 2014 at 05:09:59PM +, Olof Johansson wrote:
On Thu, Feb 20, 2014 at 3:22 AM, Catalin Marinas
Two additional points:
1. Single arm64 defconfig file covering everything
2. Modules rather than built-in by default where possible (especially
for server platforms)
Hi Chris,
On 07.02.2014 10:58, Tomasz Figa wrote:
Hi Chris,
On 11.01.2014 22:39, Tomasz Figa wrote:
On platforms prior to Exynos the SDHCI block used internal clock
divider controlled by SELFREQ field of CLKCON register to divide base
clock selected from several external clocks fed to the
This series adds devicetree support for the front and rear camera of
the Exynos4412 SoC Trats2 board. It converts related drivers to use
the v4l2-async API. The SoC output clocks are provided to external image
image sensors through the common clock API.
I'd appreciate a DT binding maintainer
This patch adds binding documentation for the Samsung S5K6A3(YX)
raw image sensor.
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
Acked-by: Mark Rutland mark.rutl...@arm.com
---
Changes since v3:
-none.
Changes since v2:
- rephrased
This patch enables the rear facing camera (s5c73m3) on TRATS2 board
by adding the I2C0 bus controller, s5c73m3 sensor, MIPI CSI-2 receiver
and the sensor's voltage regulator supply nodes.
Signed-off-by: Andrzej Hajda a.ha...@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
This series adds devicetree support for the front and rear camera of
the Exynos4412 SoC Trats2 board. It converts related drivers to use
the v4l2-async API. The SoC output clocks are provided to external image
image sensors through the common clock API.
I'd appreciate a DT binding maintainer
This patch documents following updates of the Exynos4 SoC camera subsystem
devicetree binding:
- addition of #clock-cells property to 'camera' node - the #clock-cells
property is needed when the sensor sub-devices use clock provided by
the camera host interface;
- addition of an optional
This patch removes the common fimc-is-sensor driver for image sensors
that are normally controlled by the FIMC-IS firmware. The FIMC-IS
driver now contains only a table of properties specific to each sensor.
The sensor properties required for the ISP's firmware are parsed from
device tree and
Remove unused /camera/clock-controller node and required clock properties
to the camera node. This is required for a clock provider that will be
referenced by image sensor devices.
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
This adds DT binding documentation for Samsung S5C73M3 camera sensor
with an embedded ISP.
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
Changes since v3:
- DT binding documentation separated into this patch;
Changes since v2:
-
This patch adds the V4L2 asynchronous subdev registration and
device tree support. Common clock API is used to control the
sensor master clock from within the subdev.
Signed-off-by: Andrzej Hajda a.ha...@samsung.com
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Acked-by: Kyungmin Park
This patch adds subdev driver for Samsung S5K6A3 raw image sensor.
As it is intended at the moment to be used only with the Exynos
FIMC-IS (camera ISP) subsystem it is pretty minimal subdev driver.
It doesn't do any I2C communication since the sensor is controlled
by the ISP and its own firmware.
This patch adds clock provider so the the SCLK_CAM0/1 output clocks
can be accessed by image sensor devices through the clk API.
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
Changes since v3:
- use clock-output-names DT property
Add support for registering external sensor subdevs using v4l2-async
API. The async API is used only for sensor subdevs and only for DT
platforms.
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
Hi Grant,
On Thu, 2014-02-20 at 11:29AM +, Grant Likely wrote:
On Thu, Feb 20, 2014 at 8:39 AM, Sachin Kamat sachin.ka...@linaro.org wrote:
Hi Grant,
I observe the following boot failure with today's (next-20140220) linux-next
tree on Exynos based boards with the default
On 20 February 2014 23:18, Arnd Bergmann a...@arndb.de wrote:
On Thursday 20 February 2014 18:34:23 Tomasz Figa wrote:
On 20.02.2014 18:00, Arnd Bergmann wrote:
Of course nothing stops you from retaining more specific compatible
strings. In fact, this is probably the most appropriate
32 matches
Mail list logo
