devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Gaddam, Sarath Babu Naidu" <sarath.babu.naidu.gaddam@amd.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"edumazet@google.com" <edumazet@google.com>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"krzysztof.kozlowski+dt@linaro.org" 
	<krzysztof.kozlowski+dt@linaro.org>
Cc: "michal.simek@xilinx.com" <michal.simek@xilinx.com>,
	"radhey.shyam.pandey@xilinx.com" <radhey.shyam.pandey@xilinx.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Sarangi, Anirudha" <anirudha.sarangi@amd.com>,
	"Katakam, Harini" <harini.katakam@amd.com>,
	"git (AMD-Xilinx)" <git@amd.com>
Subject: Re: [PATCH net-next V7] dt-bindings: net: xlnx,axi-ethernet: convert bindings document to yaml
Date: Tue, 2 May 2023 12:28:02 +0200	[thread overview]
Message-ID: <04112f5c-231d-559a-39f9-d183e8985a87@linaro.org> (raw)
In-Reply-To: <MW5PR12MB559857065E298E7A8485305D876F9@MW5PR12MB5598.namprd12.prod.outlook.com>

On 02/05/2023 12:09, Gaddam, Sarath Babu Naidu wrote:
> 
> 
>> -----Original Message-----
>> From: Gaddam, Sarath Babu Naidu
>> <sarath.babu.naidu.gaddam@amd.com>
>> Sent: Tuesday, March 28, 2023 9:31 PM
>> To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>;
>> davem@davemloft.net; edumazet@google.com; kuba@kernel.org;
>> pabeni@redhat.com; robh+dt@kernel.org;
>> krzysztof.kozlowski+dt@linaro.org
>> Cc: michal.simek@xilinx.com; radhey.shyam.pandey@xilinx.com;
>> netdev@vger.kernel.org; devicetree@vger.kernel.org; linux-arm-
>> kernel@lists.infradead.org; linux-kernel@vger.kernel.org; Sarangi,
>> Anirudha <anirudha.sarangi@amd.com>; Katakam, Harini
>> <harini.katakam@amd.com>; git (AMD-Xilinx) <git@amd.com>
>> Subject: RE: [PATCH net-next V7] dt-bindings: net: xlnx,axi-ethernet:
>> convert bindings document to yaml
>>
>>
>>
>>> -----Original Message-----
>>> From: Gaddam, Sarath Babu Naidu
>>> <sarath.babu.naidu.gaddam@amd.com>
>>> Sent: Tuesday, March 28, 2023 6:22 PM
>>> To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>;
>>> davem@davemloft.net; edumazet@google.com; kuba@kernel.org;
>>> pabeni@redhat.com; robh+dt@kernel.org;
>>> krzysztof.kozlowski+dt@linaro.org
>>> Cc: michal.simek@xilinx.com; radhey.shyam.pandey@xilinx.com;
>>> netdev@vger.kernel.org; devicetree@vger.kernel.org; linux-arm-
>>> kernel@lists.infradead.org; linux-kernel@vger.kernel.org; Sarangi,
>>> Anirudha <anirudha.sarangi@amd.com>; Katakam, Harini
>>> <harini.katakam@amd.com>; git (AMD-Xilinx) <git@amd.com>
>>> Subject: RE: [PATCH net-next V7] dt-bindings: net: xlnx,axi-ethernet:
>>> convert bindings document to yaml
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>>> Sent: Tuesday, March 14, 2023 9:22 PM
>>>> To: Gaddam, Sarath Babu Naidu
>>>> <sarath.babu.naidu.gaddam@amd.com>; davem@davemloft.net;
>>>> edumazet@google.com; kuba@kernel.org; pabeni@redhat.com;
>>>> robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org
>>>> Cc: michal.simek@xilinx.com; radhey.shyam.pandey@xilinx.com;
>>>> netdev@vger.kernel.org; devicetree@vger.kernel.org; linux-arm-
>>>> kernel@lists.infradead.org; linux-kernel@vger.kernel.org; Sarangi,
>>>> Anirudha <anirudha.sarangi@amd.com>; Katakam, Harini
>>>> <harini.katakam@amd.com>; git (AMD-Xilinx) <git@amd.com>
>>>> Subject: Re: [PATCH net-next V7] dt-bindings: net: xlnx,axi-ethernet:
>>>> convert bindings document to yaml
>>>>
>>>> On 08/03/2023 07:12, Sarath Babu Naidu Gaddam wrote:
>>>>> From: Radhey Shyam Pandey <radhey.shyam.pandey@xilinx.com>
>>>>>
>>>>> Convert the bindings document for Xilinx AXI Ethernet Subsystem
>>> from
>>>>> txt to yaml. No changes to existing binding description.
>>>>>
>>>>
>>>> (...)
>>>>
>>>>> +properties:
>>>>> +  compatible:
>>>>> +    enum:
>>>>> +      - xlnx,axi-ethernet-1.00.a
>>>>> +      - xlnx,axi-ethernet-1.01.a
>>>>> +      - xlnx,axi-ethernet-2.01.a
>>>>> +
>>>>> +  reg:
>>>>> +    description:
>>>>> +      Address and length of the IO space, as well as the address
>>>>> +      and length of the AXI DMA controller IO space, unless
>>>>> +      axistream-connected is specified, in which case the reg
>>>>> +      attribute of the node referenced by it is used.
>>>>
>>>> Did you test it with axistream-connected? The schema and description
>>>> feel contradictory and tests would point the issue.
>>>
>>> Thanks for review comments. We tested with axistream-connected and
>> did
>>> not observe any errors. Do you anticipate any issues/errors ?
>>
>> Just to add more details, we have tested it using below dt node
>>
>> 	axienet@0 {
>> 	        axistream-connected = <&dma>;
>>                         reg = <0x00 0x80000000 0x00 0x40000>;
>>                         compatible = "xlnx,axi-ethernet-2.01.a";
>>                         clock-names = "s_axi_lite_clk\0axis_clk\0ref_clk";
>>                         clocks = <0x03 0x47 0x03 0x47 0x18>;
>>                         phy-mode = "sgmii";
>>                         xlnx,rxcsum = <0x02>;
>>                         xlnx,rxmem = <0x1000>;
>>                         xlnx,txcsum = <0x02>;
>>                         pcs-handle = <0x19>;
>>                         phy-handle = <0x78>;
>>                         dmas = <0x17 0x00 0x17 0x01>;
>>                         dma-names = "tx_chan0\0rx_chan0";
>>                         mac-address = [ff ff ff ff ff ff];
>>                         managed = "in-band-status";
>>                         phandle = <0x79>;
>> 		mdio {
>>                                 #address-cells = <0x01>;
>>                                 #size-cells = <0x00>;
>>
>>                                 phy@0 {
>>                                         compatible = "ethernet-phy-ieee802.3-c22";
>>                                         reg = <0x00>;
>>                                         phandle = <0x78>;
>>                                 };
>>
>>                                 ethernet-phy@2 {
>>                                         device_type = "ethernet-phy";
>>                                         reg = <0x02>;
>>                                         phandle = <0x19>;
>>                                 };
>>                         };
>> 	};
>> This DT node works with our board. "&dma" is the dma DT node  and to
>> test the second case where dma  address and length  included  in the
>> axienet reg's property as below "reg = <0x00 0x80000000 0x00 0x40000
>> 0x0 0x80040000 0x0 0x1000>;"
>>
>> I did not observe any issue with above two cases. Used below command
>> to validate the yaml using above DT node.
>> make dtbs_check
>> DT_SCHEMA_FILES=Documentation/devicetree/bindings/net/xlnx,axi-
>> ethernet.yaml
>>
> 
> Hi Krzysztof,  Can you please comment If above explanation is acceptable ?
> I will address remaining review comments and send the next version.

The DTS you pointed obviously cannot work with the binding - it has
obvious mistakes. Starting with phy-mode. So whatever you did, was not
correct testing. Since nothing from your code is upstream, I cannot
verify it.

Upstream your DTS first.

Best regards,
Krzysztof


  reply	other threads:[~2023-05-02 10:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08  6:12 [PATCH net-next V7] dt-bindings: net: xlnx,axi-ethernet: convert bindings document to yaml Sarath Babu Naidu Gaddam
2023-03-13 23:15 ` Jakub Kicinski
2023-03-14 15:52   ` Krzysztof Kozlowski
2023-03-14 15:52 ` Krzysztof Kozlowski
2023-03-28 12:52   ` Gaddam, Sarath Babu Naidu
2023-03-28 16:01     ` Gaddam, Sarath Babu Naidu
2023-05-02 10:09       ` Gaddam, Sarath Babu Naidu
2023-05-02 10:28         ` Krzysztof Kozlowski [this message]
2023-05-02 10:26     ` Krzysztof Kozlowski
2023-05-03  9:30       ` Gaddam, Sarath Babu Naidu
2023-05-18  6:17         ` Gaddam, Sarath Babu Naidu
2023-05-18 14:34           ` Krzysztof Kozlowski
2023-05-18 14:38             ` Krzysztof Kozlowski

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=04112f5c-231d-559a-39f9-d183e8985a87@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=anirudha.sarangi@amd.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=git@amd.com \
    --cc=harini.katakam@amd.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=radhey.shyam.pandey@xilinx.com \
    --cc=robh+dt@kernel.org \
    --cc=sarath.babu.naidu.gaddam@amd.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).