From: "Ramuthevar, Vadivel MuruganX" <vadivel.muruganx.ramuthevar@linux.intel.com>
To: Kishon Vijay Abraham I <kishon@ti.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Cc: andriy.shevchenko@intel.com, cheol.yong.kim@intel.com,
qi-ming.wu@intel.com, peter.harliman.liem@intel.com
Subject: Re: [PATCH v10 0/2] phy: intel-lgm-emmc: Add support for eMMC PHY
Date: Mon, 6 Jan 2020 16:01:45 +0800 [thread overview]
Message-ID: <9917ebc0-656e-6539-504a-208ef375a989@linux.intel.com> (raw)
In-Reply-To: <c5df1165-5b8d-f329-582f-15553eb5eb1a@ti.com>
Hi,
On 6/1/2020 3:24 PM, Kishon Vijay Abraham I wrote:
>
> On 17/12/19 7:26 AM, Ramuthevar,Vadivel MuruganX wrote:
>> Add eMMC-PHY support for Intel LGM SoC
> merged now, Thanks!
Thanks a lot!!! Kishon for the quick rely and merge.
---
Regards
Vadivel
>
> -Kishon
>
>> changes in v10:
>> - Rob's review comments update in YAML
>> - drop clock-names since it is single entry
>>
>> changes in v9:
>> - Rob's review comments update in YAML
>>
>> changes in v8:
>> Remove the extra Signed-of-by
>>
>> changes in v7:
>> Rebased to maintainer kernel tree phy-tag-5.5
>>
>> 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
>>
>>
>>
>> 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 | 56 ++++
>> 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, 352 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:[~2020-01-06 8:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 1:56 [PATCH v10 0/2] phy: intel-lgm-emmc: Add support for eMMC PHY Ramuthevar,Vadivel MuruganX
2019-12-17 1:56 ` [PATCH v10 1/2] dt-bindings: phy: intel-emmc-phy: Add YAML schema for LGM " Ramuthevar,Vadivel MuruganX
2019-12-18 14:46 ` Rob Herring
2020-01-13 17:55 ` Rob Herring
2020-01-14 2:56 ` Ramuthevar, Vadivel MuruganX
2019-12-17 1:56 ` [PATCH v10 2/2] phy: intel-lgm-emmc: Add support for " Ramuthevar,Vadivel MuruganX
2020-01-06 7:24 ` [PATCH v10 0/2] " Kishon Vijay Abraham I
2020-01-06 8:01 ` 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=9917ebc0-656e-6539-504a-208ef375a989@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 \
/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).