From: Jin Guojun <hidden> Date: 2016-08-04 02:18:18
mmc: dw_mmc-k3: Hisilicon Hikey have no tuning function in
dw_mmc-k3.c,so we must do the tuning function stub when we init UHS card.
V1:add .prepare_command in dw_mmc.c
V2:delete .prepare_command, add err = 0 in dw_mci_execute_tuning
V3:delete err = 0 in dw_mci_execute_tuning,add .execute_tuning in
dw_mmc-k3.c
V4:add "linux-mmc at vger.kernel.org", patch version, Changelog, etc..
Signed-off-by: Jin Guojun <redacted>
---
drivers/mmc/host/dw_mmc-k3.c | 6 ++++++
1 file changed, 6 insertions(+)
Hi,maintainers
Pls help to review code,this is the newest patch after your advise
Thx
On 2016/8/4 10:16, Jin Guojun wrote:
quoted hunk
mmc: dw_mmc-k3: Hisilicon Hikey have no tuning function in
dw_mmc-k3.c,so we must do the tuning function stub when we init UHS card.
V1:add .prepare_command in dw_mmc.c
V2:delete .prepare_command, add err = 0 in dw_mci_execute_tuning
V3:delete err = 0 in dw_mci_execute_tuning,add .execute_tuning in
dw_mmc-k3.c
V4:add "linux-mmc at vger.kernel.org", patch version, Changelog, etc..
Signed-off-by: Jin Guojun <redacted>
---
drivers/mmc/host/dw_mmc-k3.c | 6 ++++++
1 file changed, 6 insertions(+)
From: Shawn Lin <shawn.lin@rock-chips.com> Date: 2016-08-08 09:10:46
Hi guy,
On 2016/8/8 15:10, Jinguojun wrote:
Hi,maintainers
Pls help to review code,this is the newest patch after your advise
Please give Jaehoon more time to review your patch before sending a
ping or resending one(~2 weeks), as it's only four days(weekend
included) since v4 was done....IMHO, it's quite bold...
Thx
On 2016/8/4 10:16, Jin Guojun wrote:
quoted
mmc: dw_mmc-k3: Hisilicon Hikey have no tuning function in
dw_mmc-k3.c,so we must do the tuning function stub when we init UHS card.
Hrmmm.... remove "mmc: dw_mmc-k3:" from the meat of commit msg?
And you do nothing for dw_mci_hi6220_execute_tuning, why?
Could you elaborate more..
quoted
V1:add .prepare_command in dw_mmc.c
V2:delete .prepare_command, add err = 0 in dw_mci_execute_tuning
V3:delete err = 0 in dw_mci_execute_tuning,add .execute_tuning in
dw_mmc-k3.c
V4:add "linux-mmc at vger.kernel.org", patch version, Changelog, etc..
The changelog is totally wrong, namely it should not be listed in the
commit msg...
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi,maintainers
Pls help to review code,this is the newest patch after your advise
Subject..
s/UHS-SD/UHS-I/
quoted
Please give Jaehoon more time to review your patch before sending a
ping or resending one(~2 weeks), as it's only four days(weekend
included) since v4 was done....IMHO, it's quite bold...
quoted
Thx
On 2016/8/4 10:16, Jin Guojun wrote:
quoted
mmc: dw_mmc-k3: Hisilicon Hikey have no tuning function in
dw_mmc-k3.c,so we must do the tuning function stub when we init UHS card.
Hrmmm.... remove "mmc: dw_mmc-k3:" from the meat of commit msg?
And you do nothing for dw_mci_hi6220_execute_tuning, why?
Could you elaborate more..
quoted
quoted
V1:add .prepare_command in dw_mmc.c
V2:delete .prepare_command, add err = 0 in dw_mci_execute_tuning
V3:delete err = 0 in dw_mci_execute_tuning,add .execute_tuning in
dw_mmc-k3.c
V4:add "linux-mmc at vger.kernel.org", patch version, Changelog, etc..
The changelog is totally wrong, namely it should not be listed in the
commit msg...
All of UHS-I cards didn't need to do tuning sequence on your SoC? it's strange.
I think we can fix more exactly in dw_mmc.c
As i know, some UHS cards don't need to send the tuning sequence.
(If i know wrong, let me know plz.)
But just skipping execute_tuning..I think it's not correct.
Best Regards,
Jaehoon Chung
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi,maintainers
Pls help to review code,this is the newest patch after your advise
Subject..
s/UHS-SD/UHS-I/
quoted
quoted
Please give Jaehoon more time to review your patch before sending a
ping or resending one(~2 weeks), as it's only four days(weekend
included) since v4 was done....IMHO, it's quite bold...
quoted
Thx
I apologize for my rudeness.
quoted
quoted
On 2016/8/4 10:16, Jin Guojun wrote:
quoted
mmc: dw_mmc-k3: Hisilicon Hikey have no tuning function in
dw_mmc-k3.c,so we must do the tuning function stub when we init UHS card.
Hrmmm.... remove "mmc: dw_mmc-k3:" from the meat of commit msg?
And you do nothing for dw_mci_hi6220_execute_tuning, why?
Could you elaborate more..
OK I'll remove the mmc: dw_mmc-k3:,Then Hikey can't support SDR104,so we only support SDR12 SDR25 SD50,and we do not need to do tuning for these modes.
quoted
quoted
quoted
V1:add .prepare_command in dw_mmc.c
V2:delete .prepare_command, add err = 0 in dw_mci_execute_tuning
V3:delete err = 0 in dw_mci_execute_tuning,add .execute_tuning in
dw_mmc-k3.c
V4:add "linux-mmc at vger.kernel.org", patch version, Changelog, etc..
The changelog is totally wrong, namely it should not be listed in the
commit msg...
All of UHS-I cards didn't need to do tuning sequence on your SoC? it's strange.
I think we can fix more exactly in dw_mmc.c
As i know, some UHS cards don't need to send the tuning sequence.
(If i know wrong, let me know plz.)
But just skipping execute_tuning..I think it's not correct.
Best Regards,
Jaehoon Chung
We cant support SDR104 currently.We only turn on SDR12 SDR25 SDR50.
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi,maintainers
Pls help to review code,this is the newest patch after your advise
Subject..
s/UHS-SD/UHS-I/
quoted
quoted
Please give Jaehoon more time to review your patch before sending a
ping or resending one(~2 weeks), as it's only four days(weekend
included) since v4 was done....IMHO, it's quite bold...
quoted
Thx
I apologize for my rudeness.
Don't mind. Feel free to tell me anytime! :)
quoted
quoted
quoted
On 2016/8/4 10:16, Jin Guojun wrote:
quoted
mmc: dw_mmc-k3: Hisilicon Hikey have no tuning function in
dw_mmc-k3.c,so we must do the tuning function stub when we init UHS card.
Hrmmm.... remove "mmc: dw_mmc-k3:" from the meat of commit msg?
And you do nothing for dw_mci_hi6220_execute_tuning, why?
Could you elaborate more..
OK I'll remove the mmc: dw_mmc-k3:,Then Hikey can't support SDR104,so we only support SDR12 SDR25 SD50,and we do not need to do tuning for these modes.
quoted
quoted
quoted
quoted
V1:add .prepare_command in dw_mmc.c
V2:delete .prepare_command, add err = 0 in dw_mci_execute_tuning
V3:delete err = 0 in dw_mci_execute_tuning,add .execute_tuning in
dw_mmc-k3.c
V4:add "linux-mmc at vger.kernel.org", patch version, Changelog, etc..
The changelog is totally wrong, namely it should not be listed in the
commit msg...
All of UHS-I cards didn't need to do tuning sequence on your SoC? it's strange.
I think we can fix more exactly in dw_mmc.c
As i know, some UHS cards don't need to send the tuning sequence.
(If i know wrong, let me know plz.)
But just skipping execute_tuning..I think it's not correct.
Best Regards,
Jaehoon Chung
We cant support SDR104 currently.We only turn on SDR12 SDR25 SDR50.
I will send the patch for execute_tuning in dwmmc.c within this week.
After that, could you check that patch? I will add your email to CC. How about?
I think it's better than using the dummy function. :)
Best Regards,
Jaehoon Chung
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
.
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi,maintainers
Pls help to review code,this is the newest patch after your advise
Subject..
s/UHS-SD/UHS-I/
quoted
quoted
Please give Jaehoon more time to review your patch before sending a
ping or resending one(~2 weeks), as it's only four days(weekend
included) since v4 was done....IMHO, it's quite bold...
quoted
Thx
I apologize for my rudeness.
Don't mind. Feel free to tell me anytime! :)
quoted
quoted
quoted
quoted
On 2016/8/4 10:16, Jin Guojun wrote:
quoted
mmc: dw_mmc-k3: Hisilicon Hikey have no tuning function in
dw_mmc-k3.c,so we must do the tuning function stub when we init UHS card.
Hrmmm.... remove "mmc: dw_mmc-k3:" from the meat of commit msg?
And you do nothing for dw_mci_hi6220_execute_tuning, why?
Could you elaborate more..
OK I'll remove the mmc: dw_mmc-k3:,Then Hikey can't support SDR104,so we only support SDR12 SDR25 SD50,and we do not need to do tuning for these modes.
quoted
quoted
quoted
quoted
V1:add .prepare_command in dw_mmc.c
V2:delete .prepare_command, add err = 0 in dw_mci_execute_tuning
V3:delete err = 0 in dw_mci_execute_tuning,add .execute_tuning in
dw_mmc-k3.c
V4:add "linux-mmc at vger.kernel.org", patch version, Changelog, etc..
The changelog is totally wrong, namely it should not be listed in the
commit msg...
All of UHS-I cards didn't need to do tuning sequence on your SoC? it's strange.
I think we can fix more exactly in dw_mmc.c
As i know, some UHS cards don't need to send the tuning sequence.
(If i know wrong, let me know plz.)
But just skipping execute_tuning..I think it's not correct.
Best Regards,
Jaehoon Chung
We cant support SDR104 currently.We only turn on SDR12 SDR25 SDR50.
I will send the patch for execute_tuning in dwmmc.c within this week.
After that, could you check that patch? I will add your email to CC. How about?
I think it's better than using the dummy function. :)
Best Regards,
Jaehoon Chung
OK when you finish the patch,pls give me the modefy
thx
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
.
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html