On 1/12/2013 2:12 AM, Maya Erez wrote:
mmc_cache_ctrl was called in runtime suspend before MMC interrupted
BKOPS in case it is still running on the card. This caused the cache
disable to timeout.
I guess even if the idle time bkops polling is not implemented, this
patch is good to have. cache co
mmc_cache_ctrl was called in runtime suspend before MMC interrupted
BKOPS in case it is still running on the card. This caused the cache
disable to timeout.
Therefore, mmc_cache_ctrl has to move to mmc_suspend where we are sure
that the card can go into suspend and there is no pending activity.
Si
On Friday 11 January 2013, Matt Porter wrote:
> We have tightly coupled the link-time dependency for
> omap_dma_filter_fn by going down the path of using
> dma_request_slave_channel_compat() as Tony suggested to avoid extra
> ifdefry.
>
> That dependency will go away naturally if all the "legacy"
Thanks, Ulf. Your help is appreciated.
> On 10 January 2013 10:22, wrote:
>> Hi Ulf,
>>
>> See below.
>>
>> Thanks,
>> Maya
>>> Hi Maya,
>>>
>>> On 24 December 2012 14:51, Maya Erez wrote:
Devices have various maintenance operations need to perform
internally.
In order to reduce
On Fri, Jan 11, 2013 at 11:40:41AM +, Arnd Bergmann wrote:
> On Friday 11 January 2013, Matt Porter wrote:
> > The approach taken is similar to how OMAP DMA is being converted to
> > DMA Engine support. With the functional EDMA private API already
> > existing in mach-davinci/dma.c, we first mo
Hi Matt,
On Friday 11 January 2013 at 06:48:39, Matt Porter wrote:
> diff --git a/arch/arm/common/edma.c b/arch/arm/common/edma.c
> index a3d189d..1951d63 100644
> --- a/arch/arm/common/edma.c
> +++ b/arch/arm/common/edma.c
> @@ -24,6 +24,13 @@
> #include
> #include
> #include
> +#include
On Fri, Jan 11, 2013 at 06:14:27PM +, Lars Poeschel wrote:
> Hi Matt,
>
> On Friday 11 January 2013 at 06:48:39, Matt Porter wrote:
>
> > diff --git a/arch/arm/common/edma.c b/arch/arm/common/edma.c
> > index a3d189d..1951d63 100644
> > --- a/arch/arm/common/edma.c
> > +++ b/arch/arm/common/e
* Matt Porter [130110 21:47]:
> Adds AM33XX MMC support for am335x-bone, am335x-evm, and
> am335x-evmsk..
This one should be queued separately by Benoit:
Acked-by: Tony Lindgren
> Signed-off-by: Matt Porter
> ---
> arch/arm/boot/dts/am335x-bone.dts |7 +++
> arch/arm/boot/dts/am335
* Matt Porter [130110 21:47]:
> The binding definition is based on the generic DMA request binding.
Acked-by: Tony Lindgren
> Signed-off-by: Matt Porter
> ---
> .../devicetree/bindings/mmc/ti-omap-hsmmc.txt | 25
> +++-
> 1 file changed, 24 insertions(+), 1 deletion(-
* Matt Porter [130110 21:47]:
> The EDMA DMAC has a hardware limitation that prevents supporting
> scatter gather lists with any number of segments. The DMA Engine
> API reports the maximum number of segments a channel can support
> via the optional dma_get_channel_caps() API. If the nr_segs
> cap
* Matt Porter [130110 21:47]:
> Convert dmaengine channel requests to use
> dma_request_slave_channel_compat(). This supports the DT case of
> platforms requiring channel selection from either the OMAP DMA or
> the EDMA engine. AM33xx only boots from DT and is the only user
> implementing EDMA so
* Matt Porter [130110 21:47]:
> Adds a dma_request_slave_channel_compat() wrapper which accepts
> both the arguments from dma_request_channel() and
> dma_request_slave_channel(). Based on whether the driver is
> instantiated via DT, the appropriate channel request call will be
> made.
>
> This al
Hi,
On Fri, Jan 11 2013, Will Newton wrote:
> I submitted this driver but will shortly no longer have access
> to hardware that uses it. The driver is quite widely used so
> there may be someone out there that feels strongly enough to
> step up and maintain it.
> ---
> MAINTAINERS |6 ++
>
I submitted this driver but will shortly no longer have access
to hardware that uses it. The driver is quite widely used so
there may be someone out there that feels strongly enough to
step up and maintain it.
---
MAINTAINERS |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --
On Fri, Jan 11, 2013 at 5:03 PM, Doug Anderson wrote:
> The "disable-wp" property is used to specify that a given SD card slot
> doesn't have a concept of write protect. This eliminates the need for
> special case code for SD slots that should never be write protected
> (like a micro SD slot or a
The next change will remove the code from the dw_mmc-exynos that added
the DW_MCI_QUIRK_NO_WRITE_PROTECT. Keep existing functionality of
having no write protect pin on smdk5250 by adding the disable-wp
property.
Signed-off-by: Doug Anderson
Acked-by: Seungwon Jeon
---
Changes in v4: None
Change
The exynos code claimed the write protect with devm_gpio_request() but
never did anything with it. That meant that anyone using a write
protect GPIO would effectively be write protected all the time.
The handling for wp-gpios belongs in the main dw_mmc driver and has
been moved there.
Signed-off
The original quirk was added in the change 'mmc: dw_mmc: add quirk to
indicate missing write protect line'. The original quirk was added at
a controller level even though each slot has its own write protect (so
the quirk should be at the slot level). A recent change (mmc: dw_mmc:
Add "disable-wp"
The "disable-wp" property is used to specify that a given SD card slot
doesn't have a concept of write protect. This eliminates the need for
special case code for SD slots that should never be write protected
(like a micro SD slot or a dev board).
The dw_mmc driver is special in needing to specif
On some SoCs (like exynos5250) you need to use an external GPIO for
write protect. Add support for wp-gpios to the core dw_mmc driver
since it could be useful across multiple SoCs.
With this change I am able to make use of the write protect for the
external SD slot on exynos5250-snow.
Signed-off
blk_rq_map_sg() function merges the physically contiguous pages to use same
scatter-gather node without checking if their page descriptors are
contiguous or not.
Now when dma_map_sg() is called on the scatter gather list, it would
take the base page pointer from each node (one by one) and iterates
On Fri, Jan 11, 2013 at 07:54:05AM +, Hebbar, Gururaja wrote:
> On Fri, Jan 11, 2013 at 11:18:41, Porter, Matt wrote:
> > The binding definition is based on the generic DMA controller
> > binding.
> >
> > Signed-off-by: Matt Porter
> > ---
> > Documentation/devicetree/bindings/dma/ti-edma.tx
On Fri, Jan 11, 2013 at 06:15:06AM +, Hebbar, Gururaja wrote:
> On Fri, Jan 11, 2013 at 11:18:37, Porter, Matt wrote:
> > Move mach-davinci/dma.c to common/edma.c so it can be used
> > by OMAP (specifically AM33xx) as well. This just moves the
> > private EDMA API and enables it to build on OMA
On 10 January 2013 10:22, wrote:
> Hi Ulf,
>
> See below.
>
> Thanks,
> Maya
>> Hi Maya,
>>
>> On 24 December 2012 14:51, Maya Erez wrote:
>>> Devices have various maintenance operations need to perform internally.
>>> In order to reduce latencies during time critical operations like read
>>> an
Hi
In sdhci_add_host function, the number of adma descriptors allocated are
128 and each descriptor consumes 8 bytes and 1 4byte is added in the end
like,
kmalloc((128 * 2 + 1) * 4, GFP_KERNEL);
In sdhci_adma_table_pre function, each node in sg-list is iterated and
in case of a misaligned nod
On Friday 11 January 2013, Matt Porter wrote:
> The approach taken is similar to how OMAP DMA is being converted to
> DMA Engine support. With the functional EDMA private API already
> existing in mach-davinci/dma.c, we first move that to an ARM common
> area so it can be shared. Adding DT and runt
Hi Maya,
I didn't see about "[PATCH v5 1/3]mmc: core: Add support for idle time BKOPS"
at mailing.
Could you check the patch set?
Best Regards,
Jaehoon Chung
On 01/11/2013 05:15 AM, Maya Erez wrote:
> Devices have various maintenance operations need to perform internally.
> In order to reduce l
On Fri, Jan 11, 2013 at 12:09:09PM +0100, Thomas Petazzoni wrote:
> Dear Russell King - ARM Linux,
>
> On Fri, 11 Jan 2013 11:02:10 +, Russell King - ARM Linux wrote:
>
> > What remains? The assumption that GPIO0 means "no GPIO" rather than
> > testing with gpio_valid() and the IRQ stuff.
>
Dear Russell King - ARM Linux,
On Fri, 11 Jan 2013 11:02:10 +, Russell King - ARM Linux wrote:
> What remains? The assumption that GPIO0 means "no GPIO" rather than
> testing with gpio_valid() and the IRQ stuff.
Patches that I have written have been merged by Jason Cooper and while
adding t
On Thu, Jan 10, 2013 at 09:29:15PM +0100, Andrew Lunn wrote:
> A NULL is a valid clk cookie, so we should not be tested with
> IS_ERR_NULL(). Replace it with IS_ERR().
>
> Signed-off-by: Andrew Lunn
> ---
> drivers/mmc/host/mvsdio.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
30 matches
Mail list logo
