From: "Ramuthevar, Vadivel MuruganX" <vadivel.muruganx.ramuthevar@linux.intel.com>
To: kishon@ti.com
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
robh@kernel.org, andriy.shevchenko@intel.com,
cheol.yong.kim@intel.com, qi-ming.wu@intel.com,
peter.harliman.liem@intel.com
Subject: Re: [PATCH v6 0/2] phy: intel,lgm-emmc-phy: Add support for eMMC PHY on Intel LGM SoC
Date: Wed, 27 Nov 2019 09:28:32 +0800 [thread overview]
Message-ID: <8a29dc7e-8d81-2630-f086-e1ac400f5718@linux.intel.com> (raw)
In-Reply-To: <20191021095436.50303-1-vadivel.muruganx.ramuthevar@linux.intel.com>
Hi Kishon,
Kindly , can you please review the eMMC-PHY driver series of patches
if you have time.
---
With Best Regards
Vadivel Murugan
On 21/10/2019 5:54 PM, Ramuthevar,Vadivel MuruganX wrote:
> Rebased to kernel verson 5.4
>
> dt-bindings: phy: intel-emmc-phy: Add YAML schema for LGM eMMC PHY
> changes in v6:
> - cobined comaptible strings
> - added as contiguous and can be a single entry for reg properties
> changes in v5:
> - earlier Review-by tag given by Rob
> - rework done with syscon parent node.
>
> changes in v4:
> - As per Rob's review: validate 5.2 and 5.3
> - drop unrelated items.
>
> changes in v3:
> - resolve 'make dt_binding_check' warnings
>
> changes in v2:
> As per Rob Herring review comments, the following updates
> - change GPL-2.0 -> (GPL-2.0-only OR BSD-2-Clause)
> - filename is the compatible string plus .yaml
> - LGM: Lightning Mountain
> - update maintainer
> - add intel,syscon under property list
> - keep one example instead of two
>
> phy: intel-lgm-emmc: Add support for eMMC PHY
> No changes from patchV5
>
> Ramuthevar Vadivel Murugan (2):
> dt-bindings: phy: intel-emmc-phy: Add YAML schema for LGM eMMC PHY
>
> phy: intel-lgm-emmc: Add support for eMMC PHY
>
> .../bindings/phy/intel,lgm-emmc-phy.yaml | 63 +++++
> drivers/phy/Kconfig | 1 +
> drivers/phy/Makefile | 1 +
> drivers/phy/intel/Kconfig | 9 +
> drivers/phy/intel/Makefile | 2 +
> drivers/phy/intel/phy-intel-emmc.c | 283 +++++++++++++++++++++
> 6 files changed, 359 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/phy/intel,lgm-emmc-phy.yaml
> create mode 100644 drivers/phy/intel/Kconfig
> create mode 100644 drivers/phy/intel/Makefile
> create mode 100644 drivers/phy/intel/phy-intel-emmc.c
>
prev parent reply other threads:[~2019-11-27 1:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 9:54 [PATCH v6 0/2] phy: intel,lgm-emmc-phy: Add support for eMMC PHY on Intel LGM SoC Ramuthevar,Vadivel MuruganX
2019-10-21 9:54 ` [PATCH v6 1/2] dt-bindings: phy: intel-emmc-phy: Add YAML schema for LGM eMMC PHY Ramuthevar,Vadivel MuruganX
2019-10-29 15:48 ` Rob Herring
2019-10-30 3:51 ` Ramuthevar, Vadivel MuruganX
2019-10-21 9:54 ` [PATCH v6 2/2] phy: intel-lgm-emmc: Add support for " Ramuthevar,Vadivel MuruganX
2019-11-27 1:28 ` Ramuthevar, Vadivel MuruganX [this message]
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=8a29dc7e-8d81-2630-f086-e1ac400f5718@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;
as well as URLs for NNTP newsgroup(s).