linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wan Zongshun <vw@iommu.org>
To: Ulf Hansson <ulf.hansson@linaro.org>, Wan Zongshun <vincent.wan@amd.com>
Cc: linux-mmc <linux-mmc@vger.kernel.org>,
	Wan Zongshun <mcuos.com@gmail.com>, Borislav Petkov <bp@suse.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Huang Rui <ray.huang@amd.com>
Subject: Re: [PATCH 2/3] mmc: sdhci-pci: Add platform tuning callback for amd hs200 mode
Date: Fri, 15 Jan 2016 09:38:54 +0800	[thread overview]
Message-ID: <56984DAE.2060200@iommu.org> (raw)
In-Reply-To: <CAPDyKFp++EZB7a3PtAanJV7Wcn8ziwdFUJe80L36UwAFAEQzdA@mail.gmail.com>

>>
>> But I also met trouble in sdhci_execute_tuning of sdhci.c, I have to suppose
>> only sdhci_pci_platform_execute_tuning is returning -EPERM(current code,
>> my assumption is right), so that those vendor that has no
>> slot->platform_execute_tuning could be skipped and go next standard
>> tuning process.
>>
>> If you have better idea for my requirement, please correct me.
>
> sdhci needs to become a set of library functions.
>
> Typically the mmc_host_ops ->execute_tuning() callback for sdhci,
> should be assigned to a default function, unless the sdhci variant has
> assigned it to something else.
>
> Yes, I realize that it requires core changes to sdhci to allow this.
> Although it's necessary do this conversion as I won't accept any more
> changes for sdhci that doesn't move the code into this direction.
>

Ulf,

Then Can you point me what's my next step for submitting tuning 
workaround for AMD emmc4.5 driver?

What your mean is you will change sdhci-pci-core.c to a core and library 
function?
And then I can implement a AMD specific emmc-pci driver call to those libs?


> Kind regards
> Uffe
>
>>
>> Thanks!
>> Wan Zongshun.
>>
>> ---
>>   drivers/mmc/host/sdhci-pci-core.c | 23 +++++++++++++++++++++++
>>   drivers/mmc/host/sdhci-pci.h      |  1 +
>>   drivers/mmc/host/sdhci.c          |  3 ++-
>>   3 files changed, 26 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/mmc/host/sdhci-pci-core.c b/drivers/mmc/host/sdhci-pci-core.c
>> index 01c5723..e7b2bbe 100644
>> --- a/drivers/mmc/host/sdhci-pci-core.c
>> +++ b/drivers/mmc/host/sdhci-pci-core.c
>> @@ -905,8 +905,19 @@ static int amd_probe(struct sdhci_pci_chip *chip)
>>          return 0;
>>   }
>>

  reply	other threads:[~2016-01-15  1:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22 16:40 [PATCH 1/3] mmc: sdhci-pci: Add AMD HS200 mode tuning function Wan Zongshun
2015-12-22  9:52 ` Andy Shevchenko
2015-12-23  0:40   ` Wan ZongShun
2015-12-22 16:40 ` [PATCH 2/3] mmc: sdhci-pci: Add platform tuning callback for amd hs200 mode Wan Zongshun
2015-12-22 12:30   ` Andy Shevchenko
2015-12-23  0:18     ` Wan ZongShun
2016-01-12 14:34   ` Ulf Hansson
2016-01-15  1:38     ` Wan Zongshun [this message]
2016-01-15  7:26       ` Ulf Hansson
2015-12-22 16:40 ` [PATCH 3/3] mmc: sdhci-pci: enable AMD emmc " Wan Zongshun

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=56984DAE.2060200@iommu.org \
    --to=vw@iommu.org \
    --cc=bp@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=mcuos.com@gmail.com \
    --cc=ray.huang@amd.com \
    --cc=ulf.hansson@linaro.org \
    --cc=vincent.wan@amd.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).