Hi Dirk,
On Thu, Jul 21, 2016 at 07:20:30AM +0200, Dirk Behme wrote:
> Hi Simon,
>
> On 21.07.2016 01:51, Simon Horman wrote:
> >On Wed, Jun 29, 2016 at 10:15:27AM +0200, Dirk Behme wrote:
> >>Hi Simon,
> >
> >...
> >
> >>Hmm, could you kindly help me to remember what's the recent status of your
Hi Simon,
On 21.07.2016 01:51, Simon Horman wrote:
On Wed, Jun 29, 2016 at 10:15:27AM +0200, Dirk Behme wrote:
Hi Simon,
...
Hmm, could you kindly help me to remember what's the recent status of your
discussion above regarding a hierarchical structure of the RCar3 device
trees?
Hi Dirk,
On Wed, Jun 29, 2016 at 10:15:27AM +0200, Dirk Behme wrote:
> Hi Simon,
...
> Hmm, could you kindly help me to remember what's the recent status of your
> discussion above regarding a hierarchical structure of the RCar3 device
> trees?
Hi Dirk,
>From my point of view the most promising avenue a
Hi Simon,
On 27.05.2016 09:32, Dirk Behme wrote:
Hi Simon,
On 27.05.2016 02:42, Simon Horman wrote:
On Thu, May 26, 2016 at 09:14:16AM +0200, Dirk Behme wrote:
Hi Simon,
On 26.05.2016 04:28, Simon Horman wrote:
Hi Dirk,
On Wed, May 25, 2016 at 07:10:26AM +0200, Dirk Behme wrote:
Hi Simon,
Hi Simon,
On 27.05.2016 02:42, Simon Horman wrote:
On Thu, May 26, 2016 at 09:14:16AM +0200, Dirk Behme wrote:
Hi Simon,
On 26.05.2016 04:28, Simon Horman wrote:
Hi Dirk,
On Wed, May 25, 2016 at 07:10:26AM +0200, Dirk Behme wrote:
Hi Simon,
On 25.05.2016 02:48, Simon Horman wrote:
Hi Dirk
On Fri, May 27, 2016 at 2:42 AM, Simon Horman wrote:
> Probably there are some central aspects of cpus that are shared
> between the r8a7795 and r8a7796. And I think that your patch captures
> that. But I also think that there will be non-shared aspects and
> perhaps the complexity of spli
On Thu, May 26, 2016 at 09:14:16AM +0200, Dirk Behme wrote:
> Hi Simon,
>
> On 26.05.2016 04:28, Simon Horman wrote:
> >Hi Dirk,
> >
> >On Wed, May 25, 2016 at 07:10:26AM +0200, Dirk Behme wrote:
> >>Hi Simon,
> >>
> >>On 25.05.2016 02:48, Simon Horman wrote:
> >>>Hi Dirk,
> >>>
> >>>On Tue, May 2
Hi Geert,
On 26.05.2016 10:05, Geert Uytterhoeven wrote:
Hi Dirk,
On Thu, May 26, 2016 at 9:32 AM, Dirk Behme wrote:
On 26.05.2016 09:03, Geert Uytterhoeven wrote:
On Wed, May 25, 2016 at 9:32 AM, Dirk Behme
wrote:
P.S.: This also results in the question why we need similar
r8a7795-cpg-mss
Hi Dirk,
On Thu, May 26, 2016 at 9:32 AM, Dirk Behme wrote:
> On 26.05.2016 09:03, Geert Uytterhoeven wrote:
>> On Wed, May 25, 2016 at 9:32 AM, Dirk Behme
>> wrote:
>>> P.S.: This also results in the question why we need similar
>>> r8a7795-cpg-mssr.h and r8a7796-cpg-mssr.h with just different
On 26.05.2016 09:03, Geert Uytterhoeven wrote:
Hi Dirk,
On Wed, May 25, 2016 at 9:32 AM, Dirk Behme wrote:
P.S.: This also results in the question why we need similar
r8a7795-cpg-mssr.h and r8a7796-cpg-mssr.h with just different "numbers" for
the same clocks. Can't we use the same numbers on a
Hi Simon,
On 26.05.2016 04:28, Simon Horman wrote:
Hi Dirk,
On Wed, May 25, 2016 at 07:10:26AM +0200, Dirk Behme wrote:
Hi Simon,
On 25.05.2016 02:48, Simon Horman wrote:
Hi Dirk,
On Tue, May 24, 2016 at 07:30:17AM +0200, Dirk Behme wrote:
Hi Simon,
[...]
With Renesas R-Car3 we will ge
Hi Dirk,
On Wed, May 25, 2016 at 9:32 AM, Dirk Behme wrote:
> P.S.: This also results in the question why we need similar
> r8a7795-cpg-mssr.h and r8a7796-cpg-mssr.h with just different "numbers" for
> the same clocks. Can't we use the same numbers on all SoCs, with just having
> wholes in the li
On Wed, May 25, 2016 at 09:38:23AM +0200, Dirk Behme wrote:
> On 24.05.2016 03:54, Simon Horman wrote:
> >Basic support for the Gen 3 R-Car M3-W SoC.
> >
> >Based on work for the r8a7795 and r8a7796 SoCs by
> >Takeshi Kihara, Dirk Behme and Geert Uytterhoeven.
> >
> >Signed-off-by: Simon Horman
>
Hi Dirk,
On Wed, May 25, 2016 at 07:10:26AM +0200, Dirk Behme wrote:
> Hi Simon,
>
> On 25.05.2016 02:48, Simon Horman wrote:
> >Hi Dirk,
> >
> >On Tue, May 24, 2016 at 07:30:17AM +0200, Dirk Behme wrote:
> >>Hi Simon,
> >
> >[...]
> >
> >>With Renesas R-Car3 we will get a whole family of SoCs. I
On 24.05.2016 03:54, Simon Horman wrote:
Basic support for the Gen 3 R-Car M3-W SoC.
Based on work for the r8a7795 and r8a7796 SoCs by
Takeshi Kihara, Dirk Behme and Geert Uytterhoeven.
Signed-off-by: Simon Horman
Reviewed-by: Geert Uytterhoeven
---
v3
* As suggested by Geert Uytterhoeven:
On 25.05.2016 07:10, Dirk Behme wrote:
Hi Simon,
On 25.05.2016 02:48, Simon Horman wrote:
Hi Dirk,
On Tue, May 24, 2016 at 07:30:17AM +0200, Dirk Behme wrote:
Hi Simon,
[...]
With Renesas R-Car3 we will get a whole family of SoCs. I.e. different
computing power (e.g. different number of C
Hi Simon,
On 25.05.2016 02:48, Simon Horman wrote:
Hi Dirk,
On Tue, May 24, 2016 at 07:30:17AM +0200, Dirk Behme wrote:
Hi Simon,
[...]
With Renesas R-Car3 we will get a whole family of SoCs. I.e. different
computing power (e.g. different number of Cores) with more or less similar
peripher
Hi Dirk,
On Tue, May 24, 2016 at 07:30:17AM +0200, Dirk Behme wrote:
> Hi Simon,
[...]
> With Renesas R-Car3 we will get a whole family of SoCs. I.e. different
> computing power (e.g. different number of Cores) with more or less similar
> peripherals.
>
> I would think that we want to reflect t
Hi Simon,
On 24.05.2016 03:54, Simon Horman wrote:
Basic support for the Gen 3 R-Car M3-W SoC.
Based on work for the r8a7795 and r8a7796 SoCs by
Takeshi Kihara, Dirk Behme and Geert Uytterhoeven.
Signed-off-by: Simon Horman
Reviewed-by: Geert Uytterhoeven
---
v3
* As suggested by Geert Uytte
Basic support for the Gen 3 R-Car M3-W SoC.
Based on work for the r8a7795 and r8a7796 SoCs by
Takeshi Kihara, Dirk Behme and Geert Uytterhoeven.
Signed-off-by: Simon Horman
Reviewed-by: Geert Uytterhoeven
---
v3
* As suggested by Geert Uytterhoeven:
- Drop 0x from unit address of gic
* As sug
20 matches
Mail list logo
