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
---
Changes in v3:
- New for this version of the patch
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
Seungwon,
On Wed, Nov 28, 2012 at 11:46 PM, Seungwon Jeon wrote:
> Hi Doug,
>
> On Thursday, November 29, 2012, Doug Anderson wrote:
>> Seungwon,
>>
>> Thanks for the review. See below for comments. If you'd like me to
>> respin then please let me know. Otherwise I look forward to your ack.
>
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
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
Hi Chris:
May I ask that whether drivers/mmc has a plan to support SDIO 4.0? If
does, what is the schedule?
Thank you
wwang
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/
A-003500: False ADMA Error might be reported when ADMA is used for
multiple block read command with Stop at Block Gap. If PROCTL[SABGREQ]
is set when the particular block's data is received by the System side
logic before entire block(with CRC) data is received by the SD side
logic, and also if
Acked-by: Jaehoon Chung
2012/11/27 James Hogan :
> On 27/11/12 08:01, Seungwon Jeon wrote:
>> This is minor change.
>>
>> Acked-by: Seungwon Jeon
>>
>> Thanks,
>> Seungwon Jeon
>
> Looks good to me too.
> Acked-by: James Hogan
>
>>
>> On Thursday, November 08, 2012, Jaehoon Chung wrote:
>>> ct
2012/11/28 Seungwon Jeon :
> On Wednesday, November 28, 2012, Jaehoon Chung wrote:
>> On 11/27/2012 05:02 PM, Seungwon Jeon wrote:
>> > On Thursday, November 08, 2012, Jaehoon Chung
>> > wrote:
>> >> Before disabling clock, need to check whether card is busy on not.
>> >>
>> >> Signed-off-by: Jae
2012/11/29 Seungwon Jeon :
> Hi James,
>
> On Wednesday, November 28, 2012, James Hogan wrote:
>> Hi,
>>
>> On 28/11/12 10:26, Seungwon Jeon wrote:
>> > Even though HLE interrupt is enabled, there is no touch.
>> > This patch clears HLE interrupt which is not unhandled.
>>
>> It's not entirely clea
Hi Maya,
Thank you a lot for working idle time BKOPS.
I tested with this patch. It's working fine.(Suspend/resume is also working
well.)
Test controller is sdhci controller.
When i tested the performance with iozone, i didn't find that performance is
decreased.
Well, as Chris is mentioned, do
On 28 November 2012 18:12, Russell King - ARM Linux
wrote:
> On Wed, Nov 28, 2012 at 05:55:13PM +0100, Per Forlin wrote:
>> I have tried to work out an if-statement to check this properly. Here
>> is my conclusion,
>> This only works if sg len is 1 (in the SDIO case)
>>
>> if (WRITE)
>> align =
12 matches
Mail list logo