Hi Lee,
On 22/09/15 21:34, Lee Jones wrote:
On Mon, 21 Sep 2015, Emilio López wrote:
Some EC implementations include a small nvram space used to store
verified boot context data. This boolean property lets us indicate
whether this space is available or not on a specific EC implementation.
The sysmmu_fimd1_1 should bind the clock CLK_SMMU_FIMD1M1, not the clock
CLK_SMMU_FIMD1M0. CLK_SMMU_FIMD1M0 is a clock for the sysmmu_fimd1_0.
Signed-off-by: Joonyoung Shim
Cc: # v4.2
---
arch/arm/boot/dts/exynos5420.dtsi | 2 +-
1 file changed,
Hello Joonyoung,
On 09/23/2015 08:48 AM, Joonyoung Shim wrote:
> The sysmmu_fimd1_1 should bind the clock CLK_SMMU_FIMD1M1, not the clock
> CLK_SMMU_FIMD1M0. CLK_SMMU_FIMD1M0 is a clock for the sysmmu_fimd1_0.
>
Can you please mention in the commit message if this patch is solving an
issue on a
The sysmmu_fimd1_1 should bind the clock CLK_SMMU_FIMD1M1, not the clock
CLK_SMMU_FIMD1M0. CLK_SMMU_FIMD1M0 is a clock for the sysmmu_fimd1_0.
This wrong clock binding causes the problem that is blocked in iommu_map
function when IOMMU is enabled and exynos-drm driver tries to allocate
buffer via
Hello,
On 2015-09-23 09:41, Joonyoung Shim wrote:
The sysmmu_fimd1_1 should bind the clock CLK_SMMU_FIMD1M1, not the clock
CLK_SMMU_FIMD1M0. CLK_SMMU_FIMD1M0 is a clock for the sysmmu_fimd1_0.
This wrong clock binding causes the problem that is blocked in iommu_map
function when IOMMU is
Hello Tobias,
On 09/21/2015 07:58 PM, Tobias Jakobi wrote:
> The pinctrl settings in i2c_0 and i2c_1 are already provided
> through the exynos4 dtsi.
>
> Signed-off-by: Tobias Jakobi
> ---
Reviewed-by: Javier Martinez Canillas
Best
Hello Tobias,
On 09/21/2015 07:59 PM, Tobias Jakobi wrote:
> Use 'ldoN_reg: LDON' syntax and drop the deprecated
> 'regulator-compatible' property.
>
> Signed-off-by: Tobias Jakobi
> ---
Reviewed-by: Javier Martinez Canillas
Best