All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ramuthevar, Vadivel MuruganX"  <vadivel.muruganx.ramuthevar@linux.intel.com>
To: Rob Herring <robh@kernel.org>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	devicetree@vger.kernel.org,
	Andy Shevchenko <andriy.shevchenko@intel.com>,
	cheol.yong.kim@intel.com, qi-ming.wu@intel.com,
	peter.harliman.liem@intel.com
Subject: Re: [PATCH v2 1/2] dt-bindings: phy: intel-emmc-phy: Add YAML schema for LGM eMMC PHY
Date: Wed, 21 Aug 2019 13:26:13 +0800	[thread overview]
Message-ID: <47e6d40d-7997-d2af-95aa-022c30c36791@linux.intel.com> (raw)
In-Reply-To: <CAL_JsqKvzogi9969fx9j6v58V5+EH-06tDx7-qy7xu84pGRSRA@mail.gmail.com>


On 20/8/2019 11:54 PM, Rob Herring wrote:
> On Tue, Aug 20, 2019 at 5:31 AM Ramuthevar,Vadivel MuruganX
> <vadivel.muruganx.ramuthevar@linux.intel.com> wrote:
>> From: Ramuthevar Vadivel Murugan <vadivel.muruganx.ramuthevar@linux.intel.com>
>>
>> Add a YAML schema to use the host controller driver with the
>> eMMC PHY on Intel's Lightning Mountain SoC.
>>
>> Signed-off-by: Ramuthevar Vadivel Murugan <vadivel.muruganx.ramuthevar@linux.intel.com>
>> ---
>> 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
>> ---
>>   .../bindings/phy/intel,lgm-emmc-phy.yaml           | 72 ++++++++++++++++++++++
>>   1 file changed, 72 insertions(+)
>>   create mode 100644 Documentation/devicetree/bindings/phy/intel,lgm-emmc-phy.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/phy/intel,lgm-emmc-phy.yaml b/Documentation/devicetree/bindings/phy/intel,lgm-emmc-phy.yaml
>> new file mode 100644
>> index 000000000000..ec177573aca6
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/phy/intel,lgm-emmc-phy.yaml
>> @@ -0,0 +1,72 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/phy/intel,lgm-emmc-phy.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Intel Lightning Mountain(LGM) eMMC PHY Device Tree Bindings
>> +
>> +maintainers:
>> +  - Ramuthevar Vadivel Murugan <vadivel.muruganx.ramuthevar@linux.intel.com>
>> +
>> +
>> +description:
>> +  -  Add a new compatible to use the host controller driver with the
>> +     eMMC PHY on Intel's Lightning Mountain SoC.
>> +
>> +$ref: /schemas/types.yaml#definitions/phandle
>> +  description:
>> +    - It also requires a "syscon" node with compatible = "intel,lgm-chiptop",
>> +      "syscon" to access the eMMC PHY register.
> Not valid schema. Please build 'make dt_binding_check' and fix any warnings.
Hi Rob,

Thank you much for the review comments, will check and update .

With Best Regards
Vadivel
>> +
>> +properties:
>> +  "#phy-cells":
>> +    const: 0
>> +
>> +  compatible:
>> +    const: intel,lgm-emmc-phy
>> +
>> +  reg:
>> +    maxItems: 1
>> +
>> +  intel,syscon:
>> +    items:
>> +      - description:
>> +         - |
>> +           e-MMC phy module should include the following properties
>> +           * reg, Access the e-MMC, get the base address from syscon.
>> +           * reset, reset the e-MMC module.
>> +
>> +  clocks:
>> +    items:
>> +      - description: e-MMC phy module clock
>> +
>> +  clock-names:
>> +    items:
>> +      - const: emmcclk
>> +
>> +  resets:
>> +    maxItems: 1
>> +
>> +required:
>> +  - "#phy-cells"
>> +  - compatible
>> +  - reg
>> +  - clocks
>> +  - clock-names
>> +  - resets
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> +  - |
>> +    emmc_phy: emmc_phy {
>> +        compatible = "intel,lgm-emmc-phy";
>> +        reg = <0xe0020000 0x100>;
>> +        intel,syscon = <&sysconf>;
>> +        clocks = <&emmc>;
>> +        clock-names = "emmcclk";
>> +        #phy-cells = <0>;
>> +    };
>> +
>> +...
>> --
>> 2.11.0
>>

  reply	other threads:[~2019-08-21  5:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-20 10:31 [PATCH v2 1/2] dt-bindings: phy: intel-emmc-phy: Add YAML schema for LGM eMMC PHY Ramuthevar,Vadivel MuruganX
2019-08-20 10:31 ` Ramuthevar,Vadivel MuruganX
2019-08-20 10:31 ` [PATCH v2 2/2] phy: intel-lgm-emmc: Add support for " Ramuthevar,Vadivel MuruganX
2019-08-20 10:31   ` Ramuthevar,Vadivel MuruganX
2019-08-20 13:56   ` Andy Shevchenko
2019-08-20 13:56     ` Andy Shevchenko
2019-08-20 13:59     ` Andy Shevchenko
2019-08-20 13:59       ` Andy Shevchenko
2019-08-21  5:34       ` Ramuthevar, Vadivel MuruganX
2019-08-21  5:34         ` Ramuthevar, Vadivel MuruganX
2019-08-21  5:33     ` Ramuthevar, Vadivel MuruganX
2019-08-21  5:33       ` Ramuthevar, Vadivel MuruganX
2019-08-20 15:54 ` [PATCH v2 1/2] dt-bindings: phy: intel-emmc-phy: Add YAML schema for LGM " Rob Herring
2019-08-20 15:54   ` Rob Herring
2019-08-21  5:26   ` Ramuthevar, Vadivel MuruganX [this message]
2019-08-21  5: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=47e6d40d-7997-d2af-95aa-022c30c36791@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 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.