From: Alper Nebi Yasak <alpernebiyasak@gmail.com>
To: Simon Glass <sjg@chromium.org>, Kever Yang <kever.yang@rock-chips.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Yifeng Zhao <yifeng.zhao@rock-chips.com>,
Peng Fan <peng.fan@nxp.com>,
Ashok Reddy Soma <ashok.reddy.soma@xilinx.com>,
Samuel Dionne-Riel <samuel@dionne-riel.com>,
Aswath Govindraju <a-govindraju@ti.com>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Jagan Teki <jagan@amarulasolutions.com>,
Stephen Carlson <stcarlso@linux.microsoft.com>,
Michal Simek <michal.simek@xilinx.com>,
Faiz Abbas <faiz_abbas@ti.com>,
Peter Robinson <pbrobinson@gmail.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
Jack Mitchell <ml@embed.me.uk>
Subject: Re: [PATCH v2 2/4] rockchip: sdhci: Fix RK3399 eMMC PHY power cycling
Date: Sat, 29 Jan 2022 01:37:48 +0300 [thread overview]
Message-ID: <2c4ac683-08c2-22fa-2b22-8173b2648cf4@gmail.com> (raw)
In-Reply-To: <CAPnjgZ26OyyqDDxZeuhOPL-VGUfrFbyWXWuF9O6DqBDrK71Rtw@mail.gmail.com>
On 21/01/2022 18:20, Simon Glass wrote:
> On Tue, 11 Jan 2022 at 06:40, Alper Nebi Yasak <alpernebiyasak@gmail.com> wrote:
>> diff --git a/drivers/mmc/rockchip_sdhci.c b/drivers/mmc/rockchip_sdhci.c
>> index 278473899c7c..f0d7ba4774d6 100644
>> --- a/drivers/mmc/rockchip_sdhci.c
>> +++ b/drivers/mmc/rockchip_sdhci.c
>> @@ -90,9 +90,10 @@ struct rockchip_sdhc {
>> };
>>
>> struct sdhci_data {
>> - int (*emmc_set_clock)(struct sdhci_host *host, unsigned int clock);
>> int (*emmc_phy_init)(struct udevice *dev);
>> int (*get_phy)(struct udevice *dev);
>> + void (*set_control_reg)(struct sdhci_host *host);
>> + int (*set_ios_post)(struct sdhci_host *host);
>
> These should each have a full function comment.
I tried to write some words for these and set_enhanced_strobe() in the
other patches, will send as v4 now.
> I don't see the kevin patches applied yet...what is happening there?
They're still not applied. I don't know what I can do about that besides
trying to send a pull request myself. Not feeling confident about that,
though, should I?
OTOH, I expect this series are testable and should be working with or
without those patches.
next prev parent reply other threads:[~2022-01-28 22:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 13:39 [PATCH v2 0/4] rockchip: sdhci: Fix reinit and add HS400 Enhanced Strobe support Alper Nebi Yasak
2022-01-11 13:39 ` [PATCH v2 1/4] mmc: sdhci: Add " Alper Nebi Yasak
2022-01-21 15:20 ` Simon Glass
2022-01-11 13:39 ` [PATCH v2 2/4] rockchip: sdhci: Fix RK3399 eMMC PHY power cycling Alper Nebi Yasak
2022-01-21 15:20 ` Simon Glass
2022-01-28 22:37 ` Alper Nebi Yasak [this message]
2022-01-11 13:39 ` [PATCH v2 3/4] rockchip: sdhci: Add HS400 Enhanced Strobe support for RK3399 Alper Nebi Yasak
2022-01-11 13:39 ` [PATCH v2 4/4] rockchip: sdhci: Add HS400 Enhanced Strobe support for RK3568 Alper Nebi Yasak
2022-01-12 2:03 ` 赵仪峰
2022-01-13 19:29 ` Alper Nebi Yasak
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=2c4ac683-08c2-22fa-2b22-8173b2648cf4@gmail.com \
--to=alpernebiyasak@gmail.com \
--cc=a-govindraju@ti.com \
--cc=ashok.reddy.soma@xilinx.com \
--cc=faiz_abbas@ti.com \
--cc=jagan@amarulasolutions.com \
--cc=jh80.chung@samsung.com \
--cc=kever.yang@rock-chips.com \
--cc=michal.simek@xilinx.com \
--cc=ml@embed.me.uk \
--cc=pbrobinson@gmail.com \
--cc=peng.fan@nxp.com \
--cc=philipp.tomsich@vrull.eu \
--cc=samuel@dionne-riel.com \
--cc=sjg@chromium.org \
--cc=stcarlso@linux.microsoft.com \
--cc=u-boot@lists.denx.de \
--cc=yifeng.zhao@rock-chips.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