On Monday 19 August 2013, Sebastian Hesselbarth wrote:
> On 08/17/13 21:08, Arnd Bergmann wrote:
> > On Friday 16 August 2013, Jason Cooper wrote:
>
> > You should really try to find out what driver uses this. If you have a
> > requirement
> > that VIRT == PHYS here, the most likely explanation
On 08/17/13 21:08, Arnd Bergmann wrote:
On Friday 16 August 2013, Jason Cooper wrote:
+
+#define ARMADA_1500_REG_BASE_VIRT 0xf600
+#define ARMADA_1500_REG_BASE_SIZE 0x0300
+
+static struct map_desc armada_1500_io_desc[] __initdata = {
+ {
+ .virtual
On Monday 19 August 2013, Sebastian Hesselbarth wrote:
> AFAIK, there is Armada 1500 (88de3100) used in every Google TV 2nd Gen
> devices, some older multimedia boxes also used Armada 1000 (88de3010),
> and Chromecast comprises Armada 1500-mini (88de3005).
According to the chromecast kernel
On Monday 19 August 2013, Sebastian Hesselbarth wrote:
> > Note that we should really change the common code to do both the
> > of_clk_init()
> > and the l2x0_of_init() automatically, but that needs to be done with some
> > care,
> > in order to not break any of the existing platforms. Would you
On Monday 19 August 2013, Sebastian Hesselbarth wrote:
Note that we should really change the common code to do both the
of_clk_init()
and the l2x0_of_init() automatically, but that needs to be done with some
care,
in order to not break any of the existing platforms. Would you be able
On Monday 19 August 2013, Sebastian Hesselbarth wrote:
AFAIK, there is Armada 1500 (88de3100) used in every Google TV 2nd Gen
devices, some older multimedia boxes also used Armada 1000 (88de3010),
and Chromecast comprises Armada 1500-mini (88de3005).
According to the chromecast kernel sources
On 08/17/13 21:08, Arnd Bergmann wrote:
On Friday 16 August 2013, Jason Cooper wrote:
+
+#define ARMADA_1500_REG_BASE_VIRT 0xf600
+#define ARMADA_1500_REG_BASE_SIZE 0x0300
+
+static struct map_desc armada_1500_io_desc[] __initdata = {
+ {
+ .virtual
On Monday 19 August 2013, Sebastian Hesselbarth wrote:
On 08/17/13 21:08, Arnd Bergmann wrote:
On Friday 16 August 2013, Jason Cooper wrote:
You should really try to find out what driver uses this. If you have a
requirement
that VIRT == PHYS here, the most likely explanation is that
On 08/17/2013 09:08 PM, Arnd Bergmann wrote:
On Friday 16 August 2013, Jason Cooper wrote:
+
+#define ARMADA_1500_REG_BASE_VIRT 0xf600
+#define ARMADA_1500_REG_BASE_SIZE 0x0300
+
+static struct map_desc armada_1500_io_desc[] __initdata = {
+ {
+ .virtual
On 08/17/2013 09:12 PM, Arnd Bergmann wrote:
On Friday 16 August 2013, Sebastian Hesselbarth wrote:
+config MACH_ARMADA_1500
+ bool "Marvell Armada 1500 boards"
+ select ARMADA_1500_CLK
+ select ARM_GIC
+ select CACHE_L2X0
+ select CPU_PJ4B
+ select
On 08/17/2013 09:08 PM, Arnd Bergmann wrote:
On Friday 16 August 2013, Jason Cooper wrote:
+
+#define ARMADA_1500_REG_BASE_VIRT 0xf600
+#define ARMADA_1500_REG_BASE_SIZE 0x0300
+
+static struct map_desc armada_1500_io_desc[] __initdata = {
+ {
+ .virtual
On 08/17/2013 09:12 PM, Arnd Bergmann wrote:
On Friday 16 August 2013, Sebastian Hesselbarth wrote:
+config MACH_ARMADA_1500
+ bool Marvell Armada 1500 boards
+ select ARMADA_1500_CLK
+ select ARM_GIC
+ select CACHE_L2X0
+ select CPU_PJ4B
+ select
On Saturday 17 August 2013, Arnd Bergmann wrote:
> On Friday 16 August 2013, Jason Cooper wrote:
> > > +
>
> You should really try to find out what driver uses this. If you have a
> requirement
> that VIRT == PHYS here, the most likely explanation is that some driver
> accidentally
> uses
On Friday 16 August 2013, Sebastian Hesselbarth wrote:
> +config MACH_ARMADA_1500
> + bool "Marvell Armada 1500 boards"
> + select ARMADA_1500_CLK
> + select ARM_GIC
> + select CACHE_L2X0
> + select CPU_PJ4B
> + select DW_APB_TIMER_OF
> + select
On Friday 16 August 2013, Jason Cooper wrote:
> > +
> > +#define ARMADA_1500_REG_BASE_VIRT 0xf600
> > +#define ARMADA_1500_REG_BASE_SIZE 0x0300
> > +
> > +static struct map_desc armada_1500_io_desc[] __initdata = {
> > + {
> > + .virtual= ARMADA_1500_REG_BASE_VIRT,
>
Dear Sebastian Hesselbarth,
On Fri, 16 Aug 2013 21:41:38 +0200, Sebastian Hesselbarth wrote:
> I am not so sure about the .map_io but I didn't yet fully understand
> the mapping requirement. Anyway, it is required for iomap and friends
> to work and basically remaps physical register addressed
On 08/16/2013 10:48 PM, Jason Cooper wrote:
On Fri, Aug 16, 2013 at 09:41:38PM +0200, Sebastian Hesselbarth wrote:
This adds initial setup for the Marvell Armada 1500 SoCs. The code
is fairly straight-forward, but especially _timer_and_clk_init()
can be simplified by using default arch hooks. I
On 08/16/2013 10:48 PM, Jason Cooper wrote:
On Fri, Aug 16, 2013 at 09:41:38PM +0200, Sebastian Hesselbarth wrote:
This adds initial setup for the Marvell Armada 1500 SoCs. The code
is fairly straight-forward, but especially _timer_and_clk_init()
can be simplified by using default arch hooks. I
Dear Sebastian Hesselbarth,
On Fri, 16 Aug 2013 21:41:38 +0200, Sebastian Hesselbarth wrote:
I am not so sure about the .map_io but I didn't yet fully understand
the mapping requirement. Anyway, it is required for iomap and friends
to work and basically remaps physical register addressed onto
On Friday 16 August 2013, Jason Cooper wrote:
+
+#define ARMADA_1500_REG_BASE_VIRT 0xf600
+#define ARMADA_1500_REG_BASE_SIZE 0x0300
+
+static struct map_desc armada_1500_io_desc[] __initdata = {
+ {
+ .virtual= ARMADA_1500_REG_BASE_VIRT,
+
On Friday 16 August 2013, Sebastian Hesselbarth wrote:
+config MACH_ARMADA_1500
+ bool Marvell Armada 1500 boards
+ select ARMADA_1500_CLK
+ select ARM_GIC
+ select CACHE_L2X0
+ select CPU_PJ4B
+ select DW_APB_TIMER_OF
+ select LOCAL_TIMERS if SMP
On Saturday 17 August 2013, Arnd Bergmann wrote:
On Friday 16 August 2013, Jason Cooper wrote:
+
You should really try to find out what driver uses this. If you have a
requirement
that VIRT == PHYS here, the most likely explanation is that some driver
accidentally
uses readl/writel
On Fri, Aug 16, 2013 at 09:41:38PM +0200, Sebastian Hesselbarth wrote:
> This adds initial setup for the Marvell Armada 1500 SoCs. The code
> is fairly straight-forward, but especially _timer_and_clk_init()
> can be simplified by using default arch hooks. I will have some time
> until mach-mvebu
This adds initial setup for the Marvell Armada 1500 SoCs. The code
is fairly straight-forward, but especially _timer_and_clk_init()
can be simplified by using default arch hooks. I will have some time
until mach-mvebu is prepared for other SoCs moving over, so I can
catch up with latest machine
This adds initial setup for the Marvell Armada 1500 SoCs. The code
is fairly straight-forward, but especially _timer_and_clk_init()
can be simplified by using default arch hooks. I will have some time
until mach-mvebu is prepared for other SoCs moving over, so I can
catch up with latest machine
On Fri, Aug 16, 2013 at 09:41:38PM +0200, Sebastian Hesselbarth wrote:
This adds initial setup for the Marvell Armada 1500 SoCs. The code
is fairly straight-forward, but especially _timer_and_clk_init()
can be simplified by using default arch hooks. I will have some time
until mach-mvebu is
26 matches
Mail list logo
