From: Ulf Hansson <ulf.hansson@linaro.org>
To: rashmi.a@intel.com
Cc: linux-drivers-review-request@eclists.intel.com,
Michal Simek <michal.simek@xilinx.com>,
linux-mmc <linux-mmc@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kishon <kishon@ti.com>, Vinod Koul <vkoul@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-phy@lists.infradead.org,
Mark Gross <mgross@linux.intel.com>,
kris.pan@linux.intel.com, furong.zhou@intel.com,
mallikarjunappa.sangannavar@intel.com,
Adrian Hunter <adrian.hunter@intel.com>,
mahesh.r.vaidya@intel.com, nandhini.srikandan@intel.com,
"Raja Subramanian,
Lakshmi Bai" <lakshmi.bai.raja.subramanian@intel.com>
Subject: Re: [“PATCH” 0/2] [KMB] mmc clock-frequency property update and
Date: Tue, 29 Jun 2021 17:08:55 +0200 [thread overview]
Message-ID: <CAPDyKFpr=jjcjK=c7-cifYdGBw7ywmLsuJWw=bE8ZYqGuiUSfA@mail.gmail.com> (raw)
In-Reply-To: <20210603182242.25733-1-rashmi.a@intel.com>
On Thu, 3 Jun 2021 at 20:22, <rashmi.a@intel.com> wrote:
>
> From: Rashmi A <rashmi.a@intel.com>
>
> Patch1: If clock-frequency property is set and it is not the same as the
> current clock rate of clk_xin(base clock frequency), set clk_xin
> to use the provided clock rate.
>
> Patch2: Since the EMMC clock in KMB was changed from 200Mhz to 175Mhz in
> FIP,there were some warnings introduced, as the frequency values
> being checked was still wrt 200Mhz in code. Hence, the frequency
> checks are now updated based on the current 175Mhz EMMC clock
> changed in FIP.
>
> Review comments from Adrian Hunter have been incorporated.
> Above 2 patches are tested with Keem Bay evaluation module board.
>
> Please help to review this patch set.
>
>
> Rashmi A (2):
> mmc: sdhci-of-arasan: Use clock-frequency property to update clk_xin
> phy: intel: Fix for warnings due to EMMC clock 175Mhz change in FIP
>
> drivers/mmc/host/sdhci-of-arasan.c | 14 ++++++++++++--
> drivers/phy/intel/phy-intel-keembay-emmc.c | 3 ++-
> 2 files changed, 14 insertions(+), 3 deletions(-)
>
> --
> 2.17.1
>
Applied for fixes, thanks!
Kind regards
Uffe
WARNING: multiple messages have this Message-ID (diff)
From: Ulf Hansson <ulf.hansson@linaro.org>
To: rashmi.a@intel.com
Cc: linux-drivers-review-request@eclists.intel.com,
Michal Simek <michal.simek@xilinx.com>,
linux-mmc <linux-mmc@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kishon <kishon@ti.com>, Vinod Koul <vkoul@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-phy@lists.infradead.org,
Mark Gross <mgross@linux.intel.com>,
kris.pan@linux.intel.com, furong.zhou@intel.com,
mallikarjunappa.sangannavar@intel.com,
Adrian Hunter <adrian.hunter@intel.com>,
mahesh.r.vaidya@intel.com, nandhini.srikandan@intel.com,
"Raja Subramanian,
Lakshmi Bai" <lakshmi.bai.raja.subramanian@intel.com>
Subject: Re: [“PATCH” 0/2] [KMB] mmc clock-frequency property update and
Date: Tue, 29 Jun 2021 17:08:55 +0200 [thread overview]
Message-ID: <CAPDyKFpr=jjcjK=c7-cifYdGBw7ywmLsuJWw=bE8ZYqGuiUSfA@mail.gmail.com> (raw)
In-Reply-To: <20210603182242.25733-1-rashmi.a@intel.com>
On Thu, 3 Jun 2021 at 20:22, <rashmi.a@intel.com> wrote:
>
> From: Rashmi A <rashmi.a@intel.com>
>
> Patch1: If clock-frequency property is set and it is not the same as the
> current clock rate of clk_xin(base clock frequency), set clk_xin
> to use the provided clock rate.
>
> Patch2: Since the EMMC clock in KMB was changed from 200Mhz to 175Mhz in
> FIP,there were some warnings introduced, as the frequency values
> being checked was still wrt 200Mhz in code. Hence, the frequency
> checks are now updated based on the current 175Mhz EMMC clock
> changed in FIP.
>
> Review comments from Adrian Hunter have been incorporated.
> Above 2 patches are tested with Keem Bay evaluation module board.
>
> Please help to review this patch set.
>
>
> Rashmi A (2):
> mmc: sdhci-of-arasan: Use clock-frequency property to update clk_xin
> phy: intel: Fix for warnings due to EMMC clock 175Mhz change in FIP
>
> drivers/mmc/host/sdhci-of-arasan.c | 14 ++++++++++++--
> drivers/phy/intel/phy-intel-keembay-emmc.c | 3 ++-
> 2 files changed, 14 insertions(+), 3 deletions(-)
>
> --
> 2.17.1
>
Applied for fixes, thanks!
Kind regards
Uffe
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2021-06-29 15:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 18:22 [“PATCH” 0/2] [KMB] mmc clock-frequency property update and rashmi.a
2021-06-03 18:22 ` rashmi.a
2021-06-03 18:22 ` rashmi.a
2021-06-03 18:22 ` [“PATCH” 1/2] mmc: sdhci-of-arasan: Use clock-frequency property to update clk_xin rashmi.a
2021-06-03 18:22 ` rashmi.a
2021-06-03 18:22 ` rashmi.a
2021-06-04 6:13 ` Michal Simek
2021-06-04 6:13 ` Michal Simek
2021-06-04 6:13 ` Michal Simek
2021-06-17 10:04 ` Ulf Hansson
2021-06-17 10:04 ` Ulf Hansson
2021-06-17 10:18 ` Sai Krishna Potthuri
2021-06-17 10:18 ` Sai Krishna Potthuri
2021-06-17 10:18 ` Sai Krishna Potthuri
2021-06-03 18:22 ` [“PATCH” 2/2] phy: intel: Fix for warnings due to EMMC clock 175Mhz change in FIP rashmi.a
2021-06-03 18:22 ` rashmi.a
2021-06-03 18:22 ` rashmi.a
2021-06-08 12:52 ` Ulf Hansson
2021-06-08 12:52 ` Ulf Hansson
2021-06-08 12:52 ` Ulf Hansson
2021-06-09 3:40 ` Vinod Koul
2021-06-09 3:40 ` Vinod Koul
2021-06-09 3:40 ` Vinod Koul
2021-06-29 15:08 ` Ulf Hansson [this message]
2021-06-29 15:08 ` [“PATCH” 0/2] [KMB] mmc clock-frequency property update and 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='CAPDyKFpr=jjcjK=c7-cifYdGBw7ywmLsuJWw=bE8ZYqGuiUSfA@mail.gmail.com' \
--to=ulf.hansson@linaro.org \
--cc=adrian.hunter@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=furong.zhou@intel.com \
--cc=kishon@ti.com \
--cc=kris.pan@linux.intel.com \
--cc=lakshmi.bai.raja.subramanian@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-drivers-review-request@eclists.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=mahesh.r.vaidya@intel.com \
--cc=mallikarjunappa.sangannavar@intel.com \
--cc=mgross@linux.intel.com \
--cc=michal.simek@xilinx.com \
--cc=nandhini.srikandan@intel.com \
--cc=rashmi.a@intel.com \
--cc=vkoul@kernel.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.