On Wednesday, January 30, 2013 8:59 PM, Vikas Sajjan wrote
>
> Adds FIMD DT support to Origen quad board
>
> Signed-off-by: Vikas Sajjan
> ---
> arch/arm/boot/dts/exynos4412-origen.dts | 22 ++
> 1 file changed, 22 insertions(+)
>
> diff --git a/arch/arm/boot/dts/exynos44
Hi Balbi,
On Fri, Feb 1, 2013 at 11:52 AM, Vivek Gautam wrote:
> Hi Kishon,
>
>
> On Fri, Feb 1, 2013 at 10:51 AM, kishon wrote:
>> Hi,
>>
>>
>> On Thursday 31 January 2013 09:08 PM, Felipe Balbi wrote:
>>>
>>> On Thu, Jan 31, 2013 at 09:00:37PM +0530, Vivek Gautam wrote:
Hi Felipe,
>
Hi Kishon,
On Fri, Feb 1, 2013 at 10:51 AM, kishon wrote:
> Hi,
>
>
> On Thursday 31 January 2013 09:08 PM, Felipe Balbi wrote:
>>
>> On Thu, Jan 31, 2013 at 09:00:37PM +0530, Vivek Gautam wrote:
>>>
>>> Hi Felipe,
>>>
>>>
>>> On Thu, Jan 31, 2013 at 8:55 PM, Felipe Balbi wrote:
Hi,
>
For the six local power blocks - MFC, DISP1, GSC, MAU, G3D and ISP
the respective CMU_RESET, CMU_SYSCLK and CMU_CLKSTOP registers need
to be low initially for normal mode on Exynos5250.
Also fix the corresponding AFTR and LPA configurations.
Signed-off-by: Abhilash Kesavan
---
arch/arm/mach-exyn
Hi,
On Thursday 31 January 2013 09:08 PM, Felipe Balbi wrote:
On Thu, Jan 31, 2013 at 09:00:37PM +0530, Vivek Gautam wrote:
Hi Felipe,
On Thu, Jan 31, 2013 at 8:55 PM, Felipe Balbi wrote:
Hi,
On Thu, Jan 31, 2013 at 08:53:27PM +0530, Vivek Gautam wrote:
Moreover, SoCs having multiple dwc3
On Fri, Feb 1, 2013 at 3:55 AM, Kukjin Kim wrote:
> Rahul Sharma wrote:
>
> [...]
>
>> + hdmi {
>> + compatible = "samsung,exynos4-hdmi14";
>> >>>
>> >>>
>> >>>
>> >>> What "-hdmi14" signifies here ? And to which Exynos4 SoC revisions
> this
>> >>> compatible property
On 31 January 2013 21:42, Viresh Kumar wrote:
> On 31 January 2013 21:37, Tomasz Figa wrote:
>> Hmm. Now as I think of it, there might be another confusing aspect:
>>
>> Could you explain what "sw coordination" and "any coordination" mean?
>> I mean specifically cpufreq_policy.cpus and cpufreq_po
Rafael J. Wysocki wrote:
>
> On Friday, January 25, 2013 10:26:41 AM Kukjin Kim wrote:
> > Sachin Kamat wrote:
> > >
> > > 'ret' is undefined when the function returns from the first
> > > 'if' condition. Without this patch we get the following warning:
> > >
> > > drivers/cpufreq/exynos-cpufreq.c
This patch is for just moving plat-s3c24xx/*.c into mach-s3c24xx/, so
that we could remove plat-s3c24xx directory. But since the PLAT_S3C24XX
is used in drivers, the statement is not deleted and it will be sorted
out next time.
Cc: Ben Dooks
Cc: Russell King
Signed-off-by: Kukjin Kim
---
arch/
This patch adds node for GMAC for exynos5440
EXYNOS5440 SoC supported by GMAC driver.
Signed-off-by: Byungho An
---
arch/arm/boot/dts/exynos5440.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5440.dtsi
b/arch/arm/boot/dts/exynos5440.dtsi
index 1e
Byungho An wrote:
>
>
> This patch adds node for GMAC for exynos5440
> EXYNOS5440 SoC supported by GMAC driver.
>
> Signed-off-by: Byungho An
> ---
> arch/arm/boot/dts/exynos5440.dtsi | 11 +++
> 1 file changed, 11 insertions(+)
>
> diff --git a/arch/arm/boot/dts/exynos5440.dtsi
> b
Tomasz Figa wrote:
>
> Hi Vivek,
[...]
> > + usb@1212 {
> > + compatible = "samsung,exynos4210-ohci";
> > + reg = <0x1212 0x100>;
> > + interrupts = <0 71 0>;
>
> For Samsung platforms we decided per board enabling of nodes and so this
> node should also
Rahul Sharma wrote:
[...]
> + hdmi {
> + compatible = "samsung,exynos4-hdmi14";
> >>>
> >>>
> >>>
> >>> What "-hdmi14" signifies here ? And to which Exynos4 SoC revisions
this
> >>> compatible property is supposed to apply ?
> >>>
> >>
> >> -hdmi14 signifies 1.4 comp
On Thu, Jan 31, 2013 at 1:56 AM, Rahul Sharma wrote:
> On Thu, Jan 31, 2013 at 3:10 AM, Amit Daniel Kachhap
> wrote:
>> This device tree support is added for PMIC block of S5m8767 multi
>> function driver. The usage detail is added in the device tree
>> documentation section. This change is teste
On 31 January 2013 21:37, Tomasz Figa wrote:
> Hmm. Now as I think of it, there might be another confusing aspect:
>
> Could you explain what "sw coordination" and "any coordination" mean?
> I mean specifically cpufreq_policy.cpus and cpufreq_policy.related_cpus
> masks.
Check this out:
https://
On Thursday 31 of January 2013 20:46:10 Viresh Kumar wrote:
> On 31 January 2013 20:34, Tomasz Figa wrote:
> > Well, the fact that it isn't used at the moment doesn't mean that it
> > shouldn't be set correctly. The field is present in the structure and
> > has a set of defined values - one of whi
On Thu, Jan 31, 2013 at 09:00:37PM +0530, Vivek Gautam wrote:
> Hi Felipe,
>
>
> On Thu, Jan 31, 2013 at 8:55 PM, Felipe Balbi wrote:
> > Hi,
> >
> > On Thu, Jan 31, 2013 at 08:53:27PM +0530, Vivek Gautam wrote:
> >> >> Moreover, SoCs having multiple dwc3 controllers will have multiple
> >> >> P
Hi Felipe,
On Thu, Jan 31, 2013 at 8:55 PM, Felipe Balbi wrote:
> Hi,
>
> On Thu, Jan 31, 2013 at 08:53:27PM +0530, Vivek Gautam wrote:
>> >> Moreover, SoCs having multiple dwc3 controllers will have multiple
>> >> PHYs, which eventually be added using usb_add_phy_dev(), and not
>> >> using usb_
Hi,
On Thu, Jan 31, 2013 at 08:53:27PM +0530, Vivek Gautam wrote:
> >> Moreover, SoCs having multiple dwc3 controllers will have multiple
> >> PHYs, which eventually be added using usb_add_phy_dev(), and not
> >> using usb_add_phy(). So each dwc3 controller won't be able to
> >> get PHYs by simply
Hi Kishon,
On Thu, Jan 31, 2013 at 5:04 PM, kishon wrote:
> Hi,
>
Thanks for your quick help.
>
> On Thursday 31 January 2013 04:50 PM, Vivek Gautam wrote:
>>
>> With device tree support in place for dwc3-core layer,
>> it gets PHY from "synopsis-dwc3" node.
>> Some controllers may not have se
On 31 January 2013 20:34, Tomasz Figa wrote:
> Well, the fact that it isn't used at the moment doesn't mean that it
> shouldn't be set correctly. The field is present in the structure and has
> a set of defined values - one of which should be selected. For example,
> I can imagine some governor ta
On Thursday 31 of January 2013 20:22:50 Viresh Kumar wrote:
> On 31 January 2013 20:15, Tomasz Figa wrote:
> > On Thursday 31 of January 2013 09:50:37 Viresh Kumar wrote:
> >> > + policy->shared_type = CPUFREQ_SHARED_TYPE_ANY;
> >>
> >> I couldn't understand the use of this change.
On 31 January 2013 20:15, Tomasz Figa wrote:
> On Thursday 31 of January 2013 09:50:37 Viresh Kumar wrote:
>> > + policy->shared_type = CPUFREQ_SHARED_TYPE_ANY;
>> I couldn't understand the use of this change. Can you please explain ?
>
> All cores on Exynos SoCs share the same cloc
Hi Viresh,
On Thursday 31 of January 2013 09:50:37 Viresh Kumar wrote:
> On Tue, Nov 13, 2012 at 2:56 PM, Tomasz Figa wrote:
> > On Exynos SoCs all cores share the same frequency setting, so changing
> > frequency of one core will affect rest of cores.
> >
> > This patch modifies the exynos-cpuf
On Wed, Jan 30, 2013 at 11:15 AM, Sachin Kamat wrote:
> On 30 January 2013 15:18, Linus Walleij wrote:
>> On Wed, Jan 30, 2013 at 5:08 AM, Kukjin Kim wrote:
>>> Sachin Kamat wrote:
>> This patch is required along with the
>> patch "gpio: samsung: fix pinctrl condition for exynos a
Hi,
On Thursday 31 January 2013 04:50 PM, Vivek Gautam wrote:
With device tree support in place for dwc3-core layer,
it gets PHY from "synopsis-dwc3" node.
Some controllers may not have separate memory maps and interrupts
for dwc3 core and platform glue layers. In such case only glue
layer's nod
With device tree support in place for dwc3-core layer,
it gets PHY from "synopsis-dwc3" node.
Some controllers may not have separate memory maps and interrupts
for dwc3 core and platform glue layers. In such case only glue
layer's node will exist.
Moreover, SoCs having multiple dwc3 controllers wil
On Thu, Jan 31, 2013 at 3:10 AM, Amit Daniel Kachhap
wrote:
> This device tree support is added for PMIC block of S5m8767 multi
> function driver. The usage detail is added in the device tree
> documentation section. This change is tested on exynos5250 based
> arndale platform by regulator voltage
On Wed, Jan 30, 2013 at 1:54 AM, Sylwester Nawrocki
wrote:
> Hi,
>
>
> On 01/28/2013 07:44 AM, Rahul Sharma wrote:
+
+ mixer: mixer {
+ compatible = "samsung,exynos4-mixer";
>>>
>>>
>>>
>>> I'm afraid this compatible property it too generic. Is the video mix
Thanks Mr. Dae,
I will include DT binding documentation in Arch side patches.
I am following the mentioned thread.
regards,
Rahul Sharma.
On Wed, Jan 30, 2013 at 12:07 PM, Inki Dae wrote:
> Hi Rahul,
>
> Could you add descriptions to dt document file? For this, you can
> refer to the below link
Thanks Sylwester,
On Wed, Jan 30, 2013 at 2:12 AM, Sylwester Nawrocki
wrote:
> Hi Rahul,
>
>
> On 01/28/2013 07:19 AM, Rahul Sharma wrote:
--- a/arch/arm/boot/dts/exynos4.dtsi
+++ b/arch/arm/boot/dts/exynos4.dtsi
@@ -289,4 +289,11 @@
interrupts =<
31 matches
Mail list logo
