Dear Chris Ball,
On Sat, 29 Mar 2014 16:19:20 +, Chris Ball wrote:
> On Sat, Mar 29 2014, Thomas Petazzoni wrote:
> > The below patch was originally sent on February, 18th. On February
> > 25th, I sent a reply to get some news. Then, again on March, 20th, I
> > sent again a reply to get some
Hi Thomas,
On Sat, Mar 29 2014, Thomas Petazzoni wrote:
> The below patch was originally sent on February, 18th. On February
> 25th, I sent a reply to get some news. Then, again on March, 20th, I
> sent again a reply to get some news. I have never heard back from you
> about this patch since a mon
Dear Chris Ball,
The below patch was originally sent on February, 18th. On February
25th, I sent a reply to get some news. Then, again on March, 20th, I
sent again a reply to get some news. I have never heard back from you
about this patch since a month and a half. The patch is fairly simple,
and
Hello Chris,
The patch below has been sent more than a month ago, and despite a ping
on February, 25th, I haven't received any feedback.
Would it be possible to get it merged, or at least get some review
comments so that some progress can be made? Or would you accept if this
patch was pushed thro
Hello Chris,
Do you think it would be possible to have the below patch merged for
3.15 ?
It would allow us to enable SDHCI support in the new Marvell Armada 38x
SOCs. The patch is fairly simple I believe, just adding an additional
compatible string to the driver, and adding a little bit of logic
Dear Arnd Bergmann,
On Tue, 18 Feb 2014 20:43:04 +0100, Arnd Bergmann wrote:
> > There are two completely different mechanisms:
> >
> > * The CPU -> { memory, device } windows. These windows are managed by
> >the mvebu-mbus driver, as they are configured using global
> >registers, owned
On Tuesday 18 February 2014 20:26:16 Thomas Petazzoni wrote:
> On Tue, 18 Feb 2014 19:02:47 +0100, Arnd Bergmann wrote:
>
> > > In order to achieve this, the sdhci-pxav3 driver is extended with an
> > > additional compatible string "marvell,armada-380-sdhci". When this
> > > compatible string is u
Dear Arnd Bergmann,
On Tue, 18 Feb 2014 19:02:47 +0100, Arnd Bergmann wrote:
> > In order to achieve this, the sdhci-pxav3 driver is extended with an
> > additional compatible string "marvell,armada-380-sdhci". When this
> > compatible string is used, the MBus windows are initialized in a way
> >
On Tuesday 18 February 2014 16:08:29 Thomas Petazzoni wrote:
> From: Marcin Wojtas
>
> The SDHCI unit used on the Armada 380 and 385 Marvell SoC is similar
> to the PXAv3 unit. The only difference is that on Armada 38x, the
> PXAv3 unit accesses memory through MBus windows which must be
> configu
From: Marcin Wojtas
The SDHCI unit used on the Armada 380 and 385 Marvell SoC is similar
to the PXAv3 unit. The only difference is that on Armada 38x, the
PXAv3 unit accesses memory through MBus windows which must be
configured prior to using the device. Without this, DMA would not
work.
In orde
10 matches
Mail list logo
