On Wednesday, May 28, 2014 6:49 PM, Sachin Kamat wrote:
>
> add_pcie_port is called from probe which is annotated with __init.
> add_pcie_port calls dw_pcie_host_init which is also annotated with
> __init. Thus it makes sense to annotate add_pcie_port with __init
> to avoid the following section m
Hi Daniel,
On 05/26/2014 06:00 PM, Daniel Kurtz wrote:
Hi YoungJun,
I am not famiilar with i80. Reading through this patch, it looks like
it works something like below for a page flip...
-> page_flip ioctl
exynos_drm_crtc_page_flip()
exynos_drm_crtc_mode_set_commit()
exynos_plane_mode
Hi, Sonny.
On 05/29/2014 09:35 AM, Sonny Rao wrote:
> This patch changes the fifo reset code to follow the reset procedure
> outlined in the documentation of Synopsys Mobile storage host databook.
>
> Signed-off-by: Sonny Rao
> Signed-off-by: Yuvaraj Kumar C D
> ---
> v2: Add Generic DMA suppor
On 28 May 2014 14:32, Daniel Lezcano wrote:
> On 05/28/2014 06:35 AM, Kukjin Kim wrote:
>>
>> Chander Kashyap wrote:
>>>
>>>
>>> On 26 May 2014 15:59, Tomasz Figa wrote:
Hi Chander,
On 16.05.2014 10:03, Chander Kashyap wrote:
>
> Exynos5420 is a big-little Soc from Sam
This patch changes the fifo reset code to follow the reset procedure
outlined in the documentation of Synopsys Mobile storage host databook.
Signed-off-by: Sonny Rao
Signed-off-by: Yuvaraj Kumar C D
---
v2: Add Generic DMA support
per the documentation, move interrupt clear before wait
m
We originally tried using this driver on ChromiumOS and never got it
to work reliably. IIRC the issue was that if the hub had already been
initialized by firmware, the USB stack might enumerate it before the
usb3503 driver is probed and then the later reset will silently
disrupt that connection. (I
Kukjin,
On Wed, May 21, 2014 at 11:34 AM, Chirantan Ekbote
wrote:
> On Wed, May 21, 2014 at 9:20 AM, Tomasz Figa wrote:
>> On 21.05.2014 15:24, Kukjin Kim wrote:
>>
>>> BTW, since
>>> exynos5260, exynos5420 and exynos5800 doesn't support arch timer, we
>>> have been using MCT on exynos5 SoCs.
>>
Tomasz,
On Thu, May 15, 2014 at 3:44 PM, Doug Anderson wrote:
> Tomasz,
>
> On Thu, May 15, 2014 at 3:13 PM, Tomasz Figa wrote:
>>> NOTE: if for some reason we need to keep the MCT around, we're
>>> definitely going to need to account for the fact that tweaking it
>>> affects the arch timer. ..
Kukjin,
Sorry for the delay in responding--this thread started just as I was
walking out the door for vacation...
On Wed, May 21, 2014 at 5:47 AM, Kukjin Kim wrote:
> Chirantan Ekbote wrote:
>>
>> >>> Anyway, I'm by no means opposed to switching to arch timers. They
>> >>> provide a well designe
ping!
On 26 May 2014 21:23, Santosh Shukla wrote:
> From: santosh shukla
>
> Add non-global symbol .LLl2x0_regs_phys to avoid build break in thumb2 mode.
>
> IIUC, arm assembler fail to load value of "global" variable
> l2xo_regs_phys for thum2 mode and wrapping it in non-global symbol like
> .L
Hi Inki,
On 05/27/2014 02:42 PM, Inki Dae wrote:
> This patch makes sure that exynos drm framework handles deferred
> probe case correctly.
>
> Sub drivers could be probed before resources, clock, regulator,
> phy or panel, are ready for them so we should make sure that exynos
> drm core waits unt
Hi Tomasz,
On 28 May 2014 16:32, Tomasz Figa wrote:
> Hi Sachin,
>
> On 28.05.2014 10:01, Sachin Kamat wrote:
>> On 21 May 2014 17:28, Sachin Kamat wrote:
>>> Local symbols are made static.
>>>
>>> Signed-off-by: Sachin Kamat
>>> ---
>>> drivers/clk/samsung/clk-exynos5420.c | 10 +-
>
On 28.05.2014 13:04, Arnd Bergmann wrote:
> On Wednesday 28 May 2014 19:41:41 Kukjin Kim wrote:
>> Hi all,
>>
>> I'm wondering who need to support following SoCs/boards in mainline.
>>
>> * S5P64X0/SMDK6440 and SMDK6450
>> * S5PC100/SMDKC100
>>
>> If nobody is using them, how about to remove them f
Hello,
On 2014-05-28 12:41, Kukjin Kim wrote:
I'm wondering who need to support following SoCs/boards in mainline.
* S5P64X0/SMDK6440 and SMDK6450
* S5PC100/SMDKC100
If nobody is using them, how about to remove them from mainline?
I'm okay with removing S5PC100.
Best regards
--
Marek Szypro
On Wednesday 28 May 2014 19:41:41 Kukjin Kim wrote:
> Hi all,
>
> I'm wondering who need to support following SoCs/boards in mainline.
>
> * S5P64X0/SMDK6440 and SMDK6450
> * S5PC100/SMDKC100
>
> If nobody is using them, how about to remove them from mainline?
I talked about this with Tomasz Fi
Hi Sachin,
On 28.05.2014 10:01, Sachin Kamat wrote:
> On 21 May 2014 17:28, Sachin Kamat wrote:
>> Local symbols are made static.
>>
>> Signed-off-by: Sachin Kamat
>> ---
>> drivers/clk/samsung/clk-exynos5420.c | 10 +-
>> 1 file changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --g
Hi all,
I'm wondering who need to support following SoCs/boards in mainline.
* S5P64X0/SMDK6440 and SMDK6450
* S5PC100/SMDKC100
If nobody is using them, how about to remove them from mainline?
Thanks,
Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the
The config enables already Samsung's PMIC-s MFD driver and regulators
(S2MPS11 and S5M8767). Enable also drivers for rest of these PMIC-s
features: clock and RTC.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/configs/exynos_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/a
add_pcie_port is called from probe which is annotated with __init.
add_pcie_port calls dw_pcie_host_init which is also annotated with
__init. Thus it makes sense to annotate add_pcie_port with __init
to avoid the following section mismatch warning:
WARNING: drivers/pci/built-in.o(.text.unlikely+0x
On 05/16/2014 10:03 AM, Chander Kashyap wrote:
Add support to select generic big-little cpuidle driver for Samsung Exynos
series SoC's. This is required for Exynos big-llittle SoC's eg, Exynos5420.
Signed-off-by: Chander Kashyap
Signed-off-by: Chander Kashyap
Acked-by: Daniel Lezcano
---
On 05/28/2014 06:35 AM, Kukjin Kim wrote:
Chander Kashyap wrote:
On 26 May 2014 15:59, Tomasz Figa wrote:
Hi Chander,
On 16.05.2014 10:03, Chander Kashyap wrote:
Exynos5420 is a big-little Soc from Samsung. It has 4 A15 and 4 A7
cores.
This patchset adds cpuidle support for Exynos5420 So
The config enables already Samsung's PMIC-s MFD driver and regulators
(S2MPS11 and S5M8767). Enable also drivers for rest of these PMIC-s
features: clock and RTC.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/configs/multi_v7_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch
On 05/16/2014 10:03 AM, Chander Kashyap wrote:
This driver will be used by many big.Little Soc's. As of now it does
string matching of hardcoded compatible string to init the driver. This
comparison list will keep on growing with addition of new SoC's.
Hence add of_device_id structure to collect
On 21 May 2014 17:28, Sachin Kamat wrote:
> Local symbols are made static.
>
> Signed-off-by: Sachin Kamat
> ---
> drivers/clk/samsung/clk-exynos5420.c | 10 +-
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/clk/samsung/clk-exynos5420.c
> b/drivers/clk/sams
Hi Inki,
There is no problem with the DSI panels, so there is nothing to fix.
DSI receives notifications about panel presence via mipi dsi bus,
so it can attach/detach it to/from drm using connector's hotplug mechansim.
Deferring DSI in unnecessary.
Regards
Andrzej
On 05/27/2014 02:42 PM, Inki
Quoting Sachin Kamat (2014-05-25 21:16:28)
> Fixes the following warning:
> WARNING: drivers/built-in.o(.text.unlikely+0x2c50): Section mismatch in
> reference from the function exynos4_clk_sleep_init() to the (unknown
> reference) .init.data:(unknown)
>The function exynos4_clk_sleep_init() r
Quoting Kukjin Kim (2014-05-27 21:49:49)
> Mike Turquette wrote:
> >
> > Quoting Tarek Dakhran (2014-05-25 20:23:32)
> > > The EXYNOS5410 clocks are statically listed and registered
> > > using the Samsung specific common clock helper functions.
> > >
> > > Signed-off-by: Tarek Dakhran
> > > Sign
27 matches
Mail list logo
