mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kris Chaplin <kris.chaplin@amd.com>
To: Rob Herring <robh@kernel.org>
Cc: thomas.delev@amd.com, michal.simek@amd.com,
	krzysztof.kozlowski@linaro.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	git@amd.com
Subject: Re: [RESEND v2 1/2] dt-bindings: w1: Add YAML DT schema for AMD AXI w1 host and MAINTAINERS entry
Date: Mon, 30 Oct 2023 15:52:12 +0000	[thread overview]
Message-ID: <83d88288-e82f-4c9c-b0ff-cc404e093a56@amd.com> (raw)
In-Reply-To: <20231030154015.GA1141490-robh@kernel.org>

Hi Rob,

On 30/10/2023 15:40, Rob Herring wrote:
> Is there a device side implementation? I can't really imagine that
> 1-wire would ever be implemented as firmware on the device side given
> its limited nature. So adding 'host' doesn't make this any more
> specific.
>
There are slave drivers as well as master, although these do not have a 
device tree binding.

The IP device from AMD is called "axi_1wire_host", and so we are hoping 
to stick with this binding if appropriate as it relates to the IP name.

Regards,
Kris


  reply	other threads:[~2023-10-30 15:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26  9:28 [RESEND v2 0/2] w1: Add AXI 1-wire host driver for AMD programmable logic IP core Kris Chaplin
2023-10-26  9:28 ` [RESEND v2 1/2] dt-bindings: w1: Add YAML DT schema for AMD AXI w1 host and MAINTAINERS entry Kris Chaplin
2023-10-30 15:40   ` Rob Herring
2023-10-30 15:52     ` Kris Chaplin [this message]
2023-10-30 16:02     ` Krzysztof Kozlowski
     [not found]     ` <df37f8db-a8c7-4a99-8828-3cb123afed1d@amd.com>
2023-10-30 16:19       ` Rob Herring
2023-10-30 16:32         ` Kris Chaplin
2023-10-26  9:28 ` [RESEND v2 2/2] w1: Add AXI 1-wire host driver for AMD programmable logic IP core Kris Chaplin

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=83d88288-e82f-4c9c-b0ff-cc404e093a56@amd.com \
    --to=kris.chaplin@amd.com \
    --cc=conor+dt@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

all inboxes | Powered by JetHome®