All of lore.kernel.org
 help / color / mirror / Atom feed
From: "yong.mao@mediatek.com" <yong.mao@mediatek.com>
To: Mattijs Korpershoek <mkorpershoek@baylibre.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Fabien Parent <fparent@baylibre.com>,
	"moderated list:ARM/Mediatek SoC support"
	<linux-mediatek@lists.infradead.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Chaotian Jing <chaotian.jing@mediatek.com>
Subject: Re: [PATCH] mmc: host: mtk-sd: enable recheck_sdio_irq for MT8516 SoC
Date: Wed, 28 Oct 2020 15:21:22 +0800	[thread overview]
Message-ID: <1603869682.6198.23.camel@mhfsdcap03> (raw)
In-Reply-To: <87wnzbg7on.fsf@baylibre.com>

On Tue, 2020-10-27 at 13:44 +0100, Mattijs Korpershoek wrote:
> Hi Ulf,
> 
> Ulf Hansson <ulf.hansson@linaro.org> writes:
> 
> > + Yong Mao, Chaotian Jing
> >
> > On Fri, 23 Oct 2020 at 14:29, Fabien Parent <fparent@baylibre.com> wrote:
> >>
> >> MT8516 SoC suffers from sometimes losing SDIO IRQs, this makes SDIO
> >> devices sometimes unstable. Make use of the new property
> >> recheck_sdio_irq to fix the SDIO stability issues on MT8516.
> >>
> >> Signed-off-by: Fabien Parent <fparent@baylibre.com>
> >
> > Maybe this is a common problem, thus I am thinking that potentially we
> > should enable the workaround for all variants?
> Not sure if this is of any help, but: we use the btmtksdio driver on a
> MT8183 soc with an Android kernel based on upstream.
> 
> With that kernel, we did not to apply this work-around in order to
> have a stable bluetooth experience (pairing with a remote controller)
> 
> However, on the MT8516 SoC, it's impossible for us to use btmtksdio
> without Fabien's fix.
> 
Yes. For mt8516 SoC,recheck_sdio_irq should be set to true for avoiding
SDIO dat1 irq lost issue. But for mt8183 SoC, it does not need recheck 
sdio irq mechanism.

> >
> > I have looped in Yong Mao (who invented the workaround) and Chaotian
> > Jing, to see if they can advise us how to proceed.
> >
> > In any case, I think we should add a stable tag and a fixes tag.
> >
> > Kind regards
> > Uffe

Hi Ulf,
Sorry. On the patch "mmc:mediatek:fix SDIO irq issue", I only consider
fixing the issue on mt8173 SoC.But for the whole MTK upstream SoC,
mt8183, mt2712, mt6779 and mt8192 does not need this mechanism,
but the other upstream Soc such as mt8135, mt8173, mt2701, mt7622, 
mt8516 and mt7620 need this recheck mechanism. And all future SoC of our
company does not need this mechanism.
If it's convenient for you, please help me to revise it.
Or I will submit a new patch to correct the value of setting.
Thanks.
> >
> >> ---
> >>  drivers/mmc/host/mtk-sd.c | 2 +-
> >>  1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/mmc/host/mtk-sd.c b/drivers/mmc/host/mtk-sd.c
> >> index a704745e5882..3dc102eefe49 100644
> >> --- a/drivers/mmc/host/mtk-sd.c
> >> +++ b/drivers/mmc/host/mtk-sd.c
> >> @@ -524,7 +524,7 @@ static const struct mtk_mmc_compatible mt7622_compat = {
> >>
> >>  static const struct mtk_mmc_compatible mt8516_compat = {
> >>         .clk_div_bits = 12,
> >> -       .recheck_sdio_irq = false,
> >> +       .recheck_sdio_irq = true,
> >>         .hs400_tune = false,
> >>         .pad_tune_reg = MSDC_PAD_TUNE0,
> >>         .async_fifo = true,
> >> --
> >> 2.28.0
> >>
> >
> > _______________________________________________
> > Linux-mediatek mailing list
> > Linux-mediatek@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-mediatek

_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: "yong.mao@mediatek.com" <yong.mao@mediatek.com>
To: Mattijs Korpershoek <mkorpershoek@baylibre.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Fabien Parent <fparent@baylibre.com>,
	"moderated list:ARM/Mediatek SoC support"
	<linux-mediatek@lists.infradead.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Chaotian Jing <chaotian.jing@mediatek.com>
Subject: Re: [PATCH] mmc: host: mtk-sd: enable recheck_sdio_irq for MT8516 SoC
Date: Wed, 28 Oct 2020 15:21:22 +0800	[thread overview]
Message-ID: <1603869682.6198.23.camel@mhfsdcap03> (raw)
In-Reply-To: <87wnzbg7on.fsf@baylibre.com>

On Tue, 2020-10-27 at 13:44 +0100, Mattijs Korpershoek wrote:
> Hi Ulf,
> 
> Ulf Hansson <ulf.hansson@linaro.org> writes:
> 
> > + Yong Mao, Chaotian Jing
> >
> > On Fri, 23 Oct 2020 at 14:29, Fabien Parent <fparent@baylibre.com> wrote:
> >>
> >> MT8516 SoC suffers from sometimes losing SDIO IRQs, this makes SDIO
> >> devices sometimes unstable. Make use of the new property
> >> recheck_sdio_irq to fix the SDIO stability issues on MT8516.
> >>
> >> Signed-off-by: Fabien Parent <fparent@baylibre.com>
> >
> > Maybe this is a common problem, thus I am thinking that potentially we
> > should enable the workaround for all variants?
> Not sure if this is of any help, but: we use the btmtksdio driver on a
> MT8183 soc with an Android kernel based on upstream.
> 
> With that kernel, we did not to apply this work-around in order to
> have a stable bluetooth experience (pairing with a remote controller)
> 
> However, on the MT8516 SoC, it's impossible for us to use btmtksdio
> without Fabien's fix.
> 
Yes. For mt8516 SoC,recheck_sdio_irq should be set to true for avoiding
SDIO dat1 irq lost issue. But for mt8183 SoC, it does not need recheck 
sdio irq mechanism.

> >
> > I have looped in Yong Mao (who invented the workaround) and Chaotian
> > Jing, to see if they can advise us how to proceed.
> >
> > In any case, I think we should add a stable tag and a fixes tag.
> >
> > Kind regards
> > Uffe

Hi Ulf,
Sorry. On the patch "mmc:mediatek:fix SDIO irq issue", I only consider
fixing the issue on mt8173 SoC.But for the whole MTK upstream SoC,
mt8183, mt2712, mt6779 and mt8192 does not need this mechanism,
but the other upstream Soc such as mt8135, mt8173, mt2701, mt7622, 
mt8516 and mt7620 need this recheck mechanism. And all future SoC of our
company does not need this mechanism.
If it's convenient for you, please help me to revise it.
Or I will submit a new patch to correct the value of setting.
Thanks.
> >
> >> ---
> >>  drivers/mmc/host/mtk-sd.c | 2 +-
> >>  1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/mmc/host/mtk-sd.c b/drivers/mmc/host/mtk-sd.c
> >> index a704745e5882..3dc102eefe49 100644
> >> --- a/drivers/mmc/host/mtk-sd.c
> >> +++ b/drivers/mmc/host/mtk-sd.c
> >> @@ -524,7 +524,7 @@ static const struct mtk_mmc_compatible mt7622_compat = {
> >>
> >>  static const struct mtk_mmc_compatible mt8516_compat = {
> >>         .clk_div_bits = 12,
> >> -       .recheck_sdio_irq = false,
> >> +       .recheck_sdio_irq = true,
> >>         .hs400_tune = false,
> >>         .pad_tune_reg = MSDC_PAD_TUNE0,
> >>         .async_fifo = true,
> >> --
> >> 2.28.0
> >>
> >
> > _______________________________________________
> > Linux-mediatek mailing list
> > Linux-mediatek@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-mediatek

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-10-28  7:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-23 12:29 [PATCH] mmc: host: mtk-sd: enable recheck_sdio_irq for MT8516 SoC Fabien Parent
2020-10-23 12:29 ` Fabien Parent
2020-10-23 12:29 ` Fabien Parent
2020-10-27 10:19 ` Matthias Brugger
2020-10-27 10:19   ` Matthias Brugger
2020-10-27 10:19   ` Matthias Brugger
2020-10-27 12:11 ` Ulf Hansson
2020-10-27 12:11   ` Ulf Hansson
2020-10-27 12:11   ` Ulf Hansson
2020-10-27 12:44   ` Mattijs Korpershoek
2020-10-27 12:44     ` Mattijs Korpershoek
2020-10-27 12:44     ` Mattijs Korpershoek
2020-10-28  7:21     ` yong.mao [this message]
2020-10-28  7:21       ` yong.mao
2020-10-28  9:40       ` Ulf Hansson
2020-10-28  9:40         ` Ulf Hansson
2020-10-28  9:40         ` Ulf Hansson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1603869682.6198.23.camel@mhfsdcap03 \
    --to=yong.mao@mediatek.com \
    --cc=chaotian.jing@mediatek.com \
    --cc=fparent@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=mkorpershoek@baylibre.com \
    --cc=ulf.hansson@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.