On 03-12-15, 12:21, Ben Gamari wrote:
> Do you mean something along these lines? [1]
Yeah.
--
viresh
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On 03-12-15, 11:05, Sudeep Holla wrote:
> The main difference is that we get the OPPs from the firmware rather
> than DT. We may just need to abstract that part and we should be able to
> use it. I will have a look at it and get back to you will more details.
> It has been a while since I looked
Viresh Kumar writes:
> On 03-12-15, 11:26, Ben Gamari wrote:
>> Viresh Kumar writes:
>> > But, before I start reviewing this series, I have few comments.
>> > - We weren't able to use cpufreq-dt driver for big LITTLE platforms
>> > earlier, as
On 03/12/15 06:05, Viresh Kumar wrote:
[...]
@Sudeep: What would it take you to use cpufreq-dt for ARM's platforms
?
The main difference is that we get the OPPs from the firmware rather
than DT. We may just need to abstract that part and we should be able to
use it. I will have a look at
This patch fixes wrong return type when dt binding of bridge device
failed.
If a board has a bridge device then of_graph_get_remote_port_parent
function shouldn't be NULL. So this patch will return a proper error
type so that the deferred probe isn't triggered.
Changelog v2:
- return -EINVAL if
Viresh Kumar writes:
> Hi Ben,
Hi Viresh,
> On 02-12-15, 22:19, Ben Gamari wrote:
>>
>> This patch series adds cpufreq support for the Exynos 5800, 5420, and 5422
>> SOCs. In particular, it adds support for operating-points-v2 bindings to the
>> arm-big-little cpufreq
Krzysztof Kozlowski writes:
> On 03.12.2015 06:19, Ben Gamari wrote:
>> From: Thomas Abraham
>>
>> With the addition of the new Samsung specific cpu-clock type, the
>> arm clock can be represented as a cpu-clock type. Add the CPU clock
>>
This patch updates a ports node binding for panel.
With this, dp node can have a ports node which describes
a remote endpoint node that can be connected to panel or bridge
node.
Signed-off-by: Inki Dae
---
.../bindings/display/exynos/exynos_dp.txt | 28
This patch series considers a port node outbound for panel device node,
including dt binding for it. And also it fixes a wrong error type.
P.s.,
I already posted relevant patch series[1] before but missed dt binding.
So please, ignore the patch series - I couldn't search the patch series
on
This patch adds of_graph dt binding support for panel device
and also keeps the backward compatibility.
i.e.,
The dts file for Exynos5800 based peach pi board
has a panel property so we need to keep the backward compatibility.
Changelog v3:
- bind only one of two nodes outbound - panel or
On 03-12-15, 11:26, Ben Gamari wrote:
> Viresh Kumar writes:
> > But, before I start reviewing this series, I have few comments.
> > - We weren't able to use cpufreq-dt driver for big LITTLE platforms
> > earlier, as it never had multi cluster support and we wanted
> >
Hello Inki,
On 12/03/2015 06:30 AM, Inki Dae wrote:
> This patch updates a ports node binding for panel.
>
> With this, dp node can have a ports node which describes
> a remote endpoint node that can be connected to panel or bridge
> node.
>
> Signed-off-by: Inki Dae
>
On Wed, 2015-12-02 at 22:19 +0100, Ben Gamari wrote:
> The frequency units are very confusing in this area as OPPs use Hz
> whereas cpufreq uses kHz. Be explicit about this in variable naming.
>
> Cc: Javier Martinez Canillas
> Signed-off-by: Ben Gamari
Hello Inki,
On 12/03/2015 02:45 AM, Inki Dae wrote:
> This patch makes it to return -EINVAL instead of -ENXIO
> when getting a port or endpoint node failed.
>
> Signed-off-by: Inki Dae
> ---
> drivers/gpu/drm/exynos/exynos_drm_dsi.c | 4 ++--
> 1 file changed, 2
Hello Inki,
On 12/02/2015 11:11 PM, Inki Dae wrote:
> Hi Javier,
>
> 2015년 12월 03일 00:04에 Javier Martinez Canillas 이(가) 쓴 글:
>> Hello Inki,
>>
>> On 12/02/2015 08:57 AM, Inki Dae wrote:
>>> This patch adds of_graph dt binding support for panel device
>>> and also keeps the backward
Hello Inki,
I found that v2 of this patch is alredy in your exynos-drm for-next branch so
so I had to revert it in linux-next to apply this one to test. You shouldn't
push patches that were still not reviewed (specially the ones that weren't
tested like this one) to your branch that gets pulled
On Wed, Dec 2, 2015 at 5:57 AM, Inki Dae wrote:
> This patch adds of_graph dt binding support for panel device
> and also keeps the backward compatibility.
>
> i.e.,
> The dts file for Exynos5800 based peach pi board
> has a panel property so we need to keep the backward
On Thu, Dec 03, 2015 at 06:30:10PM +0900, Inki Dae wrote:
> This patch updates a ports node binding for panel.
>
> With this, dp node can have a ports node which describes
> a remote endpoint node that can be connected to panel or bridge
> node.
>
> Signed-off-by: Inki Dae
The regulator/s5m8767-regulator.txt duplicates some of the information
about bindings with old mfd/s2mps11.txt. Now common part exists entirely
in mfd/samsung,sec-core.txt so:
- add company prefix to file name (regulator/samsung,s5m8767.txt),
- remove duplicated information,
- reorganize the
Hi,
The patchset tries to bring some order to the chaotic bindings for family
of Samsung PMIC devices: S2MPS/S2MPA/S5M.
Beside of renaming and removal of common parts I also tried to make
a consistent style used in the files. The bindings itself were not
modified.
The patchset should be
Bindings for Samsung S2M and S5M family PMICs are in mess. They are
spread over different files and subdirectories in a non-consistent way.
The devices and respective drivers for them share a lot in common so
everything could be organized in a more readable way.
Reorganize the S2MPS11/13/14/15
On 03.12.2015 19:30, Ben Gamari wrote:
> Krzysztof Kozlowski writes:
>
>> On 03.12.2015 06:19, Ben Gamari wrote:
>>> From: Thomas Abraham
>>>
>>> With the addition of the new Samsung specific cpu-clock type, the
>>> arm clock can be represented as
22 matches
Mail list logo