On pią, 2015-01-23 at 17:24 +0100, Bartlomiej Zolnierkiewicz wrote:
> Commit c2dd114d2486 ("ARM: EXYNOS: fix register setup for AFTR mode
> code") added S5P_CENTRAL_SEQ_OPTION register setup fix for all
> Exynos SoCs to AFTR mode code-path. It turned out that for coupled
> cpuidle AFTR mode on Exy
This patch add PPMU (Platform Performance Monitoring Unit) dt node for Exynos4
(Exynos4210/4212/4412) SoC. PPMU dt node is used to monitor the utilization of
each IP.
The Exynos4210/Exynos4212/Exynos4412 SoC includes following PPMUs:
- PPMU_DMC0 0x106A_
- PPMU_DMC1 0x106B_
- PPMU
This patch add PPMU dt node to Exynos3250-base Rinato/Monk board. The PPMU node
is used to get the utilization of DMC0/DMC1/LEFTBUS/RIGHTBUS Block.
Cc: Kukjin Kim
Signed-off-by: Chanwoo Choi
Acked-by: Kyungmin Park
---
arch/arm/boot/dts/exynos3250-monk.dts | 40 ++
This patch add dt node for PPMU_{DMC0|DMC1|LEFTBUS|RIGHTBUS} for
exynos4412-trats2 board. Each PPMU dt node includes one event of 'PPMU Count3'.
Cc: Kukjin Kim
Cc: Myungjoo Ham
Cc: Kyungmin Park
Signed-off-by: Chanwoo Choi
Acked-by: MyungJoo Ham
---
arch/arm/boot/dts/exynos4412-trats2.dts |
This patch add PPMU (Platform Performance Monitoring Unit) dt node
to estimate the utilization of each IP in Exynos SoC throught DEVFREQ Event
subsystem.
This patch adds following PPMU dt nodes:
- PPMU_DMC0 0x106a
- PPMU_DMC1 0x106b
- PPMU_RIGHTBUS 0x112A
- PPMU_LEFTBUS 0x116A
This patch add new devfreq_event class for devfreq_event device which provide
raw data (e.g., memory bus utilization/GPU utilization). This raw data from
devfreq_event data would be used for the governor of devfreq subsystem.
- devfreq_event device : Provide raw data for governor of existing devfre
This patch adds the documentation for Exynos PPMU (Platform Performance
Monitoring Unit) devfreq-event driver.
Cc: MyungJoo Ham
Cc: Kyungmin Park
Signed-off-by: Chanwoo Choi
Acked-by: MyungJoo Ham
---
.../bindings/devfreq/event/exynos-ppmu.txt | 110 +
1 file chang
This patch adds exynos-ppmu devfreq-event driver to get performance data
of each IP for Samsung Exynos SoC. These event from Exynos PPMU provide
useful information about the behavior of the SoC that you can use when
analyzing system performance, and made visible and can be counted using
logic in ea
This patchset add new devfreq_event class to provide raw data to determine
current utilization of device which is used for devfreq governor.
The following description explains the feature of two kind of devfreq class:
- devfreq class (existing)
: devfreq consumer device use raw data from devfreq
Am 26.01.2015 um 03:37 schrieb Ming Lei:
> diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> index 8c6b7c16..ddb4351 100644
> --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> +++ b/drivers/net/ethernet/stmicro/stmmac/stm
Signed-off-by: Ming Lei
---
drivers/net/ethernet/stmicro/stmmac/stmmac_main.c |5 -
.../net/ethernet/stmicro/stmmac/stmmac_platform.c | 10 ++
2 files changed, 14 insertions(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
b/drivers/net/ethern
The previous dts property isn't standard way for fixed phy
support, and switch to the fixed-link DT binding.
Signed-off-by: Ming Lei
---
arch/arm/boot/dts/exynos5440-sd5v1.dts |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/exynos5440-sd5v1.dts
b/a
Hi,
These two patches adds fixed phy support using the fixed-link DT binding
for stmmac.
v1:
- bypassing check on phy id for fixed phy (patch 2/2)
Thanks,
Ming Lei
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majord...@vger.
Dear Kukjin and Myungjoo,
On 01/26/2015 11:06 AM, MyungJoo Ham wrote:
>>
>> Chanwoo Choi wrote:
>>>
>> Hi,
>>
>
> []
>
>>>
>>> --
>>
>> Looks good to me.
>>
>> Myungjoo, shall I take DT changes in this series into Samsung tree?
>>
>> 4/7 ARM: dts: Add PPMU dt node for Exynos3250 SoC
>> 5/7 A
>
> Chanwoo Choi wrote:
> >
> Hi,
>
[]
> >
> > --
>
> Looks good to me.
>
> Myungjoo, shall I take DT changes in this series into Samsung tree?
>
> 4/7 ARM: dts: Add PPMU dt node for Exynos3250 SoC
> 5/7 ARM: dts: Add PPMU dt node for Exynos4 SoCs
> 6/7 ARM: dts: exynos: Add PPMU node f
Hi,
On 01/24/2015 12:59 AM, Javier Martinez Canillas wrote:
> Hello Sjoerd,
>
> On Fri, Jan 23, 2015 at 4:47 PM, Sjoerd Simons
> wrote:
>>>
>>> If this pin is used by the Odroid XU3 board, shouldn't be defined in
>>> the exynos5422-odroidxu3.dts instead?
>>
>> It's not just used by the XU3 thoug
Dear Tobias,
Thanks for fixing it.
Signed-off-by: Hyungwon Hwang
On Fri, 16 Jan 2015 23:57:33 +0100
Tobias Jakobi wrote:
> From: Hyungwon Hwang
>
> The ioctl DRM_EXYNOS_GEM_MAP_OFFSET and DRM_EXYNOS_GEM_MMAP are
> removed from the linux kernel. This patch modifies libdrm and libkms
> to use
On Sun, 25 Jan 2015 19:31:14 +0530
Viresh Kumar wrote:
> On 23 January 2015 at 19:27, Lukasz Majewski
> wrote:
> > Please pay a note about following problem:
> >
> > Previously we got: cpu0: cpu@0 for all Exynos devices.
> >
> > Now, however, cpu numbering has changed (due to GIC rework).
> > Fo
On Sun, 25 Jan 2015 12:46:21 -0400
Eduardo Valentin wrote:
> On Sun, Jan 25, 2015 at 07:31:14PM +0530, Viresh Kumar wrote:
> > On 23 January 2015 at 19:27, Lukasz Majewski
> > wrote:
> > > Please pay a note about following problem:
> > >
> > > Previously we got: cpu0: cpu@0 for all Exynos device
On Sun, Jan 25, 2015 at 07:31:14PM +0530, Viresh Kumar wrote:
> On 23 January 2015 at 19:27, Lukasz Majewski wrote:
> > Please pay a note about following problem:
> >
> > Previously we got: cpu0: cpu@0 for all Exynos devices.
> >
> > Now, however, cpu numbering has changed (due to GIC rework).
> >
Hi Marek,
Thank you for the patch.
On Friday 23 January 2015 16:51:21 Marek Szyprowski wrote:
> The driver doesn't need to do anything important in device add/remove
> callbacks, because initialization will be done from device-tree specific
> callbacks added later. IOMMU groups created by current
Hi,
On Fri, Jan 23, 2015 at 12:11:22PM +0100, Marek Szyprowski wrote:
> Frankly, I analyzed this case once again and I came to conclusion
> that there is no need to make a separate reset driver for Odroid
> boards. There is nothing special, specific to whole board about
> this gpio. It is rather a
On 23 January 2015 at 19:27, Lukasz Majewski wrote:
> Please pay a note about following problem:
>
> Previously we got: cpu0: cpu@0 for all Exynos devices.
>
> Now, however, cpu numbering has changed (due to GIC rework).
> For example:
>
> Exynos4412:
> cpus {
> cpu0: cpu@A
23 matches
Mail list logo
