Linux-PHY Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Yang Xiwen <forbidden405@outlook.com>,
	Vinod Koul <vkoul@kernel.org>,
	Kishon Vijay Abraham I <kishon@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jiancheng Xue <xuejiancheng@hisilicon.com>,
	Shawn Guo <shawn.guo@linaro.org>,
	Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Kishon Vijay Abraham I <kishon@ti.com>,
	David Yang <mmyangfl@gmail.com>
Subject: Re: [PATCH RFC v3 1/5] dt-bindings: phy: hisi-inno-usb2: convert to YAML
Date: Wed, 21 Feb 2024 09:23:30 +0100	[thread overview]
Message-ID: <f600daf1-a0db-4ff9-9bbb-77364e7fa22b@linaro.org> (raw)
In-Reply-To: <b4fe5565-9378-4786-8c55-113f9088f34a@linaro.org>

On 20/02/2024 12:43, Krzysztof Kozlowski wrote:
>>>
>>> hisi_inno_phy_write_reg() should be moved to a separate bus driver. It's 
>>> bus-related, not phy. PHY driver should not care how to access the bus, 
>>
>> So drivers are compatible or hardware? We talk about hardware, not
>> drivers...
>>
>>> but the bus driver should. The PHY driver only needs to use regmap_* 
>>> APIs to "write BIT(2) to addr 6".
>>
>> Different programming interface, so not compatible.
> 
> Although maybe I jumped to conclusions too fast. Do you claim that all
> registers are the same? All the values, offsets, fields and masks?

I still wait for the answer: yes or not, for above.

Best regards,
Krzysztof


-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

  parent reply	other threads:[~2024-02-21  8:23 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19 21:27 [PATCH RFC v3 0/5] phy: hisi-inno-phy: add support for hi3798mv200-usb2-phy Yang Xiwen via B4 Relay
2024-02-19 21:27 ` [PATCH RFC v3 1/5] dt-bindings: phy: hisi-inno-usb2: convert to YAML Yang Xiwen via B4 Relay
2024-02-19 21:30   ` Krzysztof Kozlowski
2024-02-19 21:33     ` Yang Xiwen
2024-02-19 21:36       ` Krzysztof Kozlowski
2024-02-19 21:50         ` Yang Xiwen
2024-02-19 21:32   ` Krzysztof Kozlowski
2024-02-19 21:35     ` Yang Xiwen
2024-02-19 21:37       ` Krzysztof Kozlowski
2024-02-19 21:49         ` Yang Xiwen
2024-02-20  8:16           ` Krzysztof Kozlowski
2024-02-20 10:40             ` Yang Xiwen
2024-02-20 11:41               ` Krzysztof Kozlowski
2024-02-20 11:43                 ` Krzysztof Kozlowski
2024-02-20 12:12                   ` Yang Xiwen
2024-02-21  8:22                     ` Krzysztof Kozlowski
2024-02-21  8:25                       ` Krzysztof Kozlowski
2024-02-21 11:15                         ` Yang Xiwen
2024-02-21 10:05                       ` Yang Xiwen
2024-02-21  8:23                   ` Krzysztof Kozlowski [this message]
2024-02-19 22:33   ` Rob Herring
2024-02-19 21:27 ` [PATCH RFC v3 2/5] arm64: dts: hi3798cv200: add hisilicon,inno-usb2-phy to compatible list Yang Xiwen via B4 Relay
2024-02-19 21:28 ` [PATCH RFC v3 3/5] phy: hisilicon: hisi-inno-phy: enable clocks for every ports Yang Xiwen via B4 Relay
2024-02-19 21:28 ` [PATCH RFC v3 4/5] phy: hisilicon: hisi-inno-phy: add support for Hi3798MV200 INNO PHY Yang Xiwen via B4 Relay
2024-02-19 21:34   ` Krzysztof Kozlowski
2024-02-19 21:37     ` Yang Xiwen
2024-02-21 12:53   ` Philipp Zabel
2024-02-19 21:28 ` [PATCH RFC v3 5/5] dt-bindings: phy: hisi-inno-usb2: add compatible of hisilicon,hi3798mv200-usb2-phy Yang Xiwen via B4 Relay
2024-02-19 21:35   ` Krzysztof Kozlowski
2024-02-20  8:18   ` Krzysztof Kozlowski
2024-02-20  9:25     ` Yang Xiwen

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=f600daf1-a0db-4ff9-9bbb-77364e7fa22b@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=forbidden405@outlook.com \
    --cc=kishon@kernel.org \
    --cc=kishon@ti.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=mmyangfl@gmail.com \
    --cc=p.zabel@pengutronix.de \
    --cc=robh+dt@kernel.org \
    --cc=shawn.guo@linaro.org \
    --cc=vkoul@kernel.org \
    --cc=xuejiancheng@hisilicon.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