From: "Ramuthevar, Vadivel MuruganX" <vadivel.muruganx.ramuthevar@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: kishon@ti.com, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, robh@kernel.org,
cheol.yong.kim@intel.com, qi-ming.wu@intel.com,
peter.harliman.liem@intel.com
Subject: Re: [PATCH v3 2/2] phy: intel-lgm-sdxc: Add support for SDXC PHY
Date: Wed, 4 Sep 2019 21:38:36 +0800 [thread overview]
Message-ID: <a36dcf94-4636-1742-4ae6-60cf2c03c7f5@linux.intel.com> (raw)
In-Reply-To: <20190904123957.GM2680@smile.fi.intel.com>
Hi Andy,
Thank you for the review comments .
On 4/9/2019 8:39 PM, Andy Shevchenko wrote:
> On Wed, Sep 04, 2019 at 02:27:19PM +0800, Ramuthevar,Vadivel MuruganX wrote:
>> From: Ramuthevar Vadivel Murugan <vadivel.muruganx.ramuthevar@linux.intel.com>
>>
>> Add support for SDXC PHY on Intel's Lightning Mountain SoC.
> What's the difference to eMMC PHY?
> Can they share the same / similar code?
eMMC and SDXC interface controller share the common driver since IP block
of the vendor(SDHC-ARASAN) is same, where as PHY is different. The PHY
is designed by Intel itself to support
specific eMMC card and SD/SDIO card specific. e.g: PAD, CLK, driver
strength..etc.
IP block of the PHY is different module for eMMC and SDXC to adapt the
controllers, that is reason we have different drivers.
---
With Best Regards
Vadivel
next prev parent reply other threads:[~2019-09-04 13:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 6:27 [PATCH v3 1/2] dt-bindings: phy: intel-sdxc-phy: Add YAML schema for LGM SDXC PHY Ramuthevar,Vadivel MuruganX
2019-09-04 6:27 ` [PATCH v3 2/2] phy: intel-lgm-sdxc: Add support for " Ramuthevar,Vadivel MuruganX
2019-09-04 12:39 ` Andy Shevchenko
2019-09-04 13:38 ` Ramuthevar, Vadivel MuruganX [this message]
2019-09-17 20:24 ` [PATCH v3 1/2] dt-bindings: phy: intel-sdxc-phy: Add YAML schema for LGM " Rob Herring
2019-09-18 2:26 ` Ramuthevar, Vadivel MuruganX
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=a36dcf94-4636-1742-4ae6-60cf2c03c7f5@linux.intel.com \
--to=vadivel.muruganx.ramuthevar@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=cheol.yong.kim@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.harliman.liem@intel.com \
--cc=qi-ming.wu@intel.com \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox