public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kris Chaplin <kris.chaplin@amd.com>
To: Rob Herring <robh@kernel.org>
Cc: Conor Dooley <conor@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	thomas.delev@amd.com, michal.simek@amd.com, conor+dt@kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	git@amd.com
Subject: Re: [PATCH 1/2] dt-bindings: w1: Add YAML DT Schema for AMD w1 master and MAINTAINERS entry
Date: Fri, 13 Oct 2023 18:58:51 +0100	[thread overview]
Message-ID: <2e0dd79b-ab76-8632-5e61-d682e1311ceb@amd.com> (raw)
In-Reply-To: <20231013171822.GA4177785-robh@kernel.org>


On 13/10/2023 18:18, Rob Herring wrote:
> i_1wire_master. It is a soft HDL core.
> Only 1 version of it (ever)? Like other PL IP, it needs a version number
> (and not v1, v2, etc. made up by you). Really, your versioning scheme
> should be documented (like
> bindings/sifive/sifive-blocks-ip-versioning.txt), but Xilinx started
> versioning stuff some time back.

I've specified the PL IP to have both an ID and version number register 
in it, which is queried by the driver on probe.  As such we can version 
autodiscover.  Should there be incompatibilty in the driver due to new 
features in future PL IP, the major version number in the register will 
increment and the same driver can be extended to support the modified 
behaviour.  The default code in this first version will check to ensure 
major is at 1. I'm working with our IP group to encourage that all new 
IP have this mechanism moving forwards, as registers are a lot cheaper 
in logic than they used to be.

+  if (ver_major != 1) {
+     dev_err(dev, "AMD AXI W1 Master version %u.%u is not supported by 
this driver",
+        ver_major, ver_minor);
+     return -ENODEV;
+  }

> Also, 'master' is not considered great terminology nowadays. Perhaps the
> catalog name should be updated.

Agreed -  I've used the term to fit with others in the subsystem.  Would 
this be something that is changed and aligned across W1?  If so I'm 
happy to get the HDL IP renamed and binding / driver documentation to 
match if an alternative designator to replace master has already been 
chosen and standardised across 1Wire.

Regards
Kris


  reply	other threads:[~2023-10-13 17:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13  9:30 [PATCH 0/2] w1: Add 1-wire master driver for AMD programmable logic IP Core Kris Chaplin
2023-10-13  9:30 ` [PATCH 1/2] dt-bindings: w1: Add YAML DT Schema for AMD w1 master and MAINTAINERS entry Kris Chaplin
2023-10-13 15:01   ` Conor Dooley
2023-10-13 15:04   ` Krzysztof Kozlowski
2023-10-13 15:07     ` Conor Dooley
2023-10-13 15:22       ` Krzysztof Kozlowski
2023-10-13 15:23       ` Kris Chaplin
2023-10-13 15:29         ` Krzysztof Kozlowski
2023-10-13 15:36           ` Kris Chaplin
2023-10-13 17:18         ` Rob Herring
2023-10-13 17:58           ` Kris Chaplin [this message]
2023-10-13  9:30 ` [PATCH 2/2] w1: Add 1-wire master driver for AMD programmable logic IP Core Kris Chaplin
2023-10-13 15:20   ` Krzysztof Kozlowski
2023-10-18 15:54     ` Kris Chaplin
2023-10-18 16:00       ` Krzysztof Kozlowski
2023-10-19 14:24 ` [PATCH v2 0/2] w1: Add AXI 1-wire host driver for AMD programmable logic IP core Kris Chaplin
2023-10-19 14:24   ` [PATCH v2 1/2] dt-bindings: w1: Add YAML DT schema for AMD AXI w1 host and MAINTAINERS entry Kris Chaplin
2023-10-19 14:30     ` Conor Dooley
2023-10-19 14:35       ` Michal Simek
2023-10-19 14:39         ` Kris Chaplin
2023-10-19 14:24   ` [PATCH v2 2/2] w1: Add AXI 1-wire host driver for AMD programmable logic IP core Kris Chaplin
2023-10-19 14:28   ` [PATCH v2 0/2] " Conor Dooley

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=2e0dd79b-ab76-8632-5e61-d682e1311ceb@amd.com \
    --to=kris.chaplin@amd.com \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=git@amd.com \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@amd.com \
    --cc=robh@kernel.org \
    --cc=thomas.delev@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