From: Dilip Kota <eswara.kota@linux.intel.com>
To: Rob Herring <robh@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
devicetree@vger.kernel.org,
Kishon Vijay Abraham I <kishon@ti.com>,
Andy Shevchenko <andriy.shevchenko@intel.com>,
cheol.yong.kim@intel.com, chuanhua.lei@linux.intel.com,
qi-ming.wu@intel.com, yixin.zhu@intel.com
Subject: Re: [PATCH v4 2/3] dt-bindings: phy: Add YAML schemas for Intel Combophy
Date: Wed, 4 Mar 2020 17:16:22 +0800 [thread overview]
Message-ID: <068bcf8c-83b0-57ee-3fb8-c0fe1bf6e5d8@linux.intel.com> (raw)
In-Reply-To: <CAL_JsqLKFbaiaeNAq_b9xDQRWVG8dXkWt2+cKucRPEzynC20XQ@mail.gmail.com>
On 3/4/2020 12:26 AM, Rob Herring wrote:
> On Tue, Mar 3, 2020 at 3:24 AM Dilip Kota <eswara.kota@linux.intel.com> wrote:
>>
>> On 3/3/2020 9:50 AM, Rob Herring wrote:
>>> On Mon, Mar 02, 2020 at 04:43:24PM +0800, Dilip Kota wrote:
>>>> Combophy subsystem provides PHY support to various
>>>> controllers, viz. PCIe, SATA and EMAC.
>>>> Adding YAML schemas for the same.
>>>>
>>>> Signed-off-by: Dilip Kota <eswara.kota@linux.intel.com>
>>>> ---
>>>> Changes on v4:
>>>> No changes.
>> ...
>>>> +additionalProperties: false
>>>> +
>>>> +examples:
>>>> + - |
>>>> + #include <dt-bindings/phy/phy-intel-combophy.h>
>>>> + combophy@d0a00000 {
>>>> + compatible = "intel,combophy-lgm", "intel,combo-phy";
>>>> + clocks = <&cgu0 1>;
>>>> + reg = <0xd0a00000 0x40000>,
>>>> + <0xd0a40000 0x1000>;
>>>> + reg-names = "core", "app";
>>>> + resets = <&rcu0 0x50 6>,
>>>> + <&rcu0 0x50 17>;
>>>> + reset-names = "phy", "core";
>>>> + intel,syscfg = <&sysconf 0>;
>>>> + intel,hsio = <&hsiol 0>;
>>>> + intel,phy-mode = <COMBO_PHY_PCIE>;
>>>> +
>>>> + phy@0 {
>>> You need a 'reg' property to go with a unit-address.
>>>
>>> Really, I'd just simplify this to make parent 'resets' be 4 entries and
>>> put '#phy-cells = <1>;' in the parent. Then you don't need these child
>>> nodes.
>> If child nodes are not present, use case like PCIe controller-0 using
>> phy@0 and PCIe controller-1 using phy@1 wont be possible.
> Yes, it will be.
>
> For controller-0:
> phys = <&phy 0>;
>
> For controller-1:
> phys = <&phy 1>;
OH got it, arg cell can be utilized for PHY id.
I started working on your suggestion in simplifying it, but below point
is haunting while doing the changes. So felt to check with you whether
the better one is going with existing DT node or the one without child
nodes!.
Existing DT node skeleton, replicates hardware design ComboPhy
with 2 PHYs. (ComboPhy as parent node and 2PHYs as child nodes)
Regards,
Dilip
>
> Rob
next prev parent reply other threads:[~2020-03-04 9:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 8:43 [PATCH v4 0/3] Add Intel ComboPhy driver Dilip Kota
2020-03-02 8:43 ` [PATCH v4 1/3] mfd: syscon: Add fwnode_to_regmap Dilip Kota
2020-03-02 8:43 ` [PATCH v4 2/3] dt-bindings: phy: Add YAML schemas for Intel Combophy Dilip Kota
2020-03-03 1:50 ` Rob Herring
2020-03-03 9:24 ` Dilip Kota
2020-03-03 16:26 ` Rob Herring
2020-03-04 9:16 ` Dilip Kota [this message]
2020-03-13 8:36 ` Dilip Kota
2020-03-02 8:43 ` [PATCH v4 3/3] phy: intel: Add driver support for ComboPhy Dilip Kota
2020-03-02 11:19 ` Andy Shevchenko
2020-03-03 8:41 ` Dilip Kota
2020-03-03 10:07 ` Andy Shevchenko
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=068bcf8c-83b0-57ee-3fb8-c0fe1bf6e5d8@linux.intel.com \
--to=eswara.kota@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=cheol.yong.kim@intel.com \
--cc=chuanhua.lei@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qi-ming.wu@intel.com \
--cc=robh@kernel.org \
--cc=yixin.zhu@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).