public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wei Xu <xuwei5@hisilicon.com>
To: Conor Dooley <conor@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Carvalho Chehab <mchehab+huawei@kernel.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: Re: [PATCH 1/2] dt-bindings: soc: hisilicon: document hi3660-usb3-otg-bc
Date: Tue, 21 May 2024 09:32:25 +0800	[thread overview]
Message-ID: <664BF9A9.3020206@hisilicon.com> (raw)
In-Reply-To: <20240520-bronzing-crumpet-c7b54753d2f1@spud>

Hi Conor,

On 2024/5/21 1:10, Conor Dooley wrote:
> On Sat, May 18, 2024 at 10:44:42PM +0200, Krzysztof Kozlowski wrote:
>> Add dedicated bindings for the Hisilicon Kirin 960 USB OTG Syscon,
>> to fully document the block and also fix dtbs_check warning:
>  
>>   hi3660-hikey960.dtb: usb3_otg_bc@ff200000: compatible: ['syscon', 'simple-mfd'] is too short
> 
>> +title: Hisilicon Kirin 960 USB OTG Syscon
>> +      - const: hisilicon,hi3660-usb3-otg-bc
> 
> I know you got it from the node name, what does "bc" mean here?

I think it might be the USB Battery Charging Specification.

Best Regards,
Wei

> Otherwise,
> Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
> 

  reply	other threads:[~2024-05-21  1:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-18 20:44 [PATCH 1/2] dt-bindings: soc: hisilicon: document hi3660-usb3-otg-bc Krzysztof Kozlowski
2024-05-18 20:44 ` [PATCH 2/2] arm64: dts: hisilicon: hi3660: add dedicated hi3660-usb3-otg-bc compatible Krzysztof Kozlowski
2024-05-20 17:10 ` [PATCH 1/2] dt-bindings: soc: hisilicon: document hi3660-usb3-otg-bc Conor Dooley
2024-05-21  1:32   ` Wei Xu [this message]
2024-06-23 12:27 ` Krzysztof Kozlowski
2024-06-24  0:34   ` Wei Xu

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=664BF9A9.3020206@hisilicon.com \
    --to=xuwei5@hisilicon.com \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=robh@kernel.org \
    /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