On 01/24/2014 07:35 PM, Fabio Estevam wrote:
On Mon, Jan 20, 2014 at 2:48 PM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
So far so good. Now, what about this external oscillator which has its
own separate power control. My immediate thought is that this can be
specified via
Hi,
On Mon, Jan 27, 2014 at 4:43 PM, Jyri Sarha jsa...@ti.com wrote:
On 01/24/2014 07:35 PM, Fabio Estevam wrote:
On Mon, Jan 20, 2014 at 2:48 PM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
So far so good. Now, what about this external oscillator which has its
own separate
On 01/27/2014 10:54 AM, Chen-Yu Tsai wrote:
Hi,
On Mon, Jan 27, 2014 at 4:43 PM, Jyri Sarha jsa...@ti.com wrote:
On 01/24/2014 07:35 PM, Fabio Estevam wrote:
...
I have not received too much feedback to my patch yet. CCF is a bit new
territory to me, but I think having a separate stackable
On 26 January 2014 18:26, Tomasz Figa tomasz.f...@gmail.com wrote:
On 21.01.2014 19:34, Tomasz Figa wrote:
Hi,
On 20.01.2014 04:56, Olof Johansson wrote:
This patch enables support for power-on sequencing of SDIO peripherals
through DT.
In general, it's quite common that wifi modules and
On 23/01/14 16:11, Ulf Hansson wrote:
On 23 January 2014 11:10, Adrian Hunter adrian.hun...@intel.com wrote:
On 22/01/14 17:00, Ulf Hansson wrote:
If the host controller supports busy detection in HW, we expect the
MMC_CAP_WAIT_WHILE_BUSY to be set. Likewise the corresponding
On 23/01/14 16:59, Ulf Hansson wrote:
On 23 January 2014 15:29, Adrian Hunter adrian.hun...@intel.com wrote:
On 23/01/14 15:21, Ulf Hansson wrote:
On 23 January 2014 11:09, Adrian Hunter adrian.hun...@intel.com wrote:
On 22/01/14 17:00, Ulf Hansson wrote:
Hosts supporting
On 23/01/14 16:26, Ulf Hansson wrote:
On 23 January 2014 11:23, Adrian Hunter adrian.hun...@intel.com wrote:
On 22/01/14 17:00, Ulf Hansson wrote:
When sending the sleep command for host drivers supporting
MMC_CAP_WAIT_WHILE_BUSY, we need to confirm that max_busy_timeout is
big enough
Hi Ben,
On Mon, 27 Jan 2014, Ben Dooks wrote:
On Mon, Jan 27, 2014 at 04:13:56PM +0100, Guennadi Liakhovetski wrote:
Hi all,
I'm working on an MMC driver with a DMA capability. All has been working
well, until at some point I've got a bus error, when the mmc driver had
been handed
Hi all,
I'm working on an MMC driver with a DMA capability. All has been working
well, until at some point I've got a bus error, when the mmc driver had
been handed in a buffer at 0x3000 physical RAM address. The reason is,
that on Zynq arch bus masters cannot access RAM below 0x8.
On Mon, Jan 27, 2014 at 04:13:56PM +0100, Guennadi Liakhovetski wrote:
I'm working on an MMC driver with a DMA capability. All has been working
well, until at some point I've got a bus error, when the mmc driver had
been handed in a buffer at 0x3000 physical RAM address. The reason is,
that
On 01/27/2014 06:02 PM, Russell King - ARM Linux wrote:
On Mon, Jan 27, 2014 at 04:13:56PM +0100, Guennadi Liakhovetski wrote:
I'm working on an MMC driver with a DMA capability. All has been working
well, until at some point I've got a bus error, when the mmc driver had
been handed in a
On Mon, Jan 27, 2014 at 06:45:50PM +0100, Michal Simek wrote:
Why 0x4000? IRC Linux for ARM is using space for any purpose.
Russell knows this much better than I.
Probably because as the kernel is loaded at 0x8000, it will place the
swapper page table at 0x4000, thus covering from 0x4000
On 01/27/2014 06:52 PM, Russell King - ARM Linux wrote:
On Mon, Jan 27, 2014 at 06:45:50PM +0100, Michal Simek wrote:
Why 0x4000? IRC Linux for ARM is using space for any purpose.
Russell knows this much better than I.
Probably because as the kernel is loaded at 0x8000, it will place the
Hi Michal, Russell,
On Mon, 27 Jan 2014, Michal Simek wrote:
On 01/27/2014 06:52 PM, Russell King - ARM Linux wrote:
On Mon, Jan 27, 2014 at 06:45:50PM +0100, Michal Simek wrote:
Why 0x4000? IRC Linux for ARM is using space for any purpose.
Russell knows this much better than I.
On Sat, Jan 25, 2014 at 5:47 PM, Chris Ball ch...@printf.net wrote:
Hi Grant,
On Thu, Jan 23 2014, Grant Grundler wrote:
respin sent with v2 in subject line and includes the '\0' assignment
change.
Apologies again.
Thanks, no worries. Would you like me to take this now, or wait for
On 27.01.2014 11:19, Ulf Hansson wrote:
On 26 January 2014 18:26, Tomasz Figa tomasz.f...@gmail.com wrote:
On 21.01.2014 19:34, Tomasz Figa wrote:
Hi,
On 20.01.2014 04:56, Olof Johansson wrote:
This patch enables support for power-on sequencing of SDIO peripherals
through DT.
In general,
Hi,
On Tue, Jan 28 2014, Tomasz Figa wrote:
I am not sure I understand why this is needed. I think it would be
more convenient to use MMC_CAP_NONREMOVABLE instead as stated earlier.
But please elaborate, I might have missed something.
See above. I'm not quite convinced that state of MMC
Hi Chris
These patches updates code for R-Car.
Basically, these clarifies chip dependent settings
inside driver, and, removed unneeded settings from dtsi file.
These are based on latest linus/master branch
(ba635f8cd20ebc7bddf1eb8e1f4eae28a034e916)
Kuninori Morimoto (4):
mmc: SDHI: tidyup
From: Kuninori Morimoto kuninori.morimoto...@renesas.com
This patch updates r8a7779 DT data to have SoC specific settings.
Latest Renesas Chip has some SDHI channels and the WP pin
availability depends on its channel or HW implementation.
Thus, this patch disables it as default,
but we can use
From: Kuninori Morimoto kuninori.morimoto...@renesas.com
it is easy to read if sh_mobile_sdhi_of_cfg and
sh_mobile_sdhi_of_match are closer
Signed-off-by: Kuninori Morimoto kuninori.morimoto...@renesas.com
---
drivers/mmc/host/sh_mobile_sdhi.c | 26 +-
1 file changed,
From: Kuninori Morimoto kuninori.morimoto...@renesas.com
This patch updates r8a7778 DT data to have SoC specific settings.
Latest Renesas Chip has some SDHI channels and the WP pin
availability depends on its channel or HW implementation.
Thus, this patch disables it as default,
but we can use
From: Kuninori Morimoto kuninori.morimoto...@renesas.com
This patch updates r8a7790 DT data to have SoC specific settings.
Latest Renesas Chip has some SDHI channels and the WP pin
availability depends on its channel or HW implementation.
Thus, this patch disables it as default,
but we can use
22 matches
Mail list logo
