devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yang Li <yang.li@amlogic.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	Marcel Holtmann <marcel@holtmann.org>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>
Cc: linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/3] dt-bindings: net: bluetooth: Add support for Amlogic Bluetooth
Date: Wed, 24 Jul 2024 14:48:48 +0800	[thread overview]
Message-ID: <ee98ce34-a08b-4aa1-aa16-d3539460c396@amlogic.com> (raw)
In-Reply-To: <bbe8d8ad-d78c-43fe-8beb-39453832b5bf@kernel.org>


On 2024/7/22 15:58, Krzysztof Kozlowski wrote:
> On 22/07/2024 09:41, Yang Li wrote:
>>>>>> +    description: bluetooth chip 3.3V supply regulator handle
>>>>>> +
>>>>>> +  clocks:
>>>>>> +    maxItems: 1
>>>>>> +    description: clock provided to the controller (32.768KHz)
>>>>>> +
>>>>>> +  antenna-number:
>>>>>> +    default: 1
>>>>>> +    description: device supports up to two antennas
>>>>> Keep it consistent - either descriptions are the last property or
>>>>> somewhere else. Usually the last.
>>>>>
>>>>>> +    $ref: /schemas/types.yaml#/definitions/uint32
>>>>> And what does it mean? What happens if BT uses antenna number 2, not 1?
>>>>> What is connected to the other antenna? It really feels useless to say
>>>>> which antenna is connected to hardware.
>>>> Sorry, the antenna description was incorrect, it should specify whether
>>>>
>>>> Bluetooth and WiFi coexist. I will change it as below:
>>>>
>>>>        aml,work-mode:
>>>>        type: boolean
>>>>        description: specifywhether Bluetooth and WiFi coexist.
>>> So one device can be used on different boards - some without WiFi
>>> antenna? But, why in the binding of bluetooth you describe whether there
>>> is WiFi antenna?
>> Yes, it can be used on dirfferent boards. The device can operate in both
> Please do not respond to only partial part of the comment. It is obvious
> device can work on different boards. You do not have to confirm it. The
> question was different - why do you need this property? I gave you
> possible answer, but you skipped this and answered with obvious statement.

I'm sorry. I didn't explain it clearly.

Board design should be optimized for specific use cases: use the 
standalone mode for high-speed, stable, and Bluetooth-only applications; 
opt for the coexistence mode in cost-sensitive scenarios with lower 
performance demands. Once the hardware is determined, the user needs to 
configure the working mode of the firmware.

>
>> standalone mode and coexistence mode. typically running standalone mode.
>>
>> Therefore, I would like to revise the description as follows:
>>
>> aml,coexisting:
>>       type: boolean
>>       description: Enable coexistence mode, allowing shared antenna usage
>> with Wi-Fi.
> Why this is not enabled always?

The board design determines whether to enable this property.

Well, I know I should clearly describe why this property is enabled 
here, so I modify it as follows:

aml,coexisting:
      type: boolean
      description: Enable co-existence mode on boards sharing antennas 
with Wi-Fi.

>
> Best regards,
> Krzysztof
>

  reply	other threads:[~2024-07-24  6:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-18  7:42 [PATCH v2 0/3] Add support for Amlogic HCI UART Yang Li via B4 Relay
2024-07-18  7:42 ` [PATCH v2 1/3] dt-bindings: net: bluetooth: Add support for Amlogic Bluetooth Yang Li via B4 Relay
2024-07-18 11:40   ` Krzysztof Kozlowski
2024-07-19  8:20     ` Yang Li
2024-07-20 18:25       ` Krzysztof Kozlowski
2024-07-22  7:41         ` Yang Li
2024-07-22  7:58           ` Krzysztof Kozlowski
2024-07-24  6:48             ` Yang Li [this message]
2024-07-30  5:52               ` Yang Li
2024-07-18  7:42 ` [PATCH v2 2/3] Bluetooth: hci_uart: Add support for Amlogic HCI UART Yang Li via B4 Relay
2024-07-18 11:43   ` Krzysztof Kozlowski
2024-07-19  8:26     ` Yang Li
2024-07-18 18:43   ` Sai Krishna Gajula
2024-07-18 19:01     ` Luiz Augusto von Dentz
2024-07-19  9:05       ` Yang Li
2024-07-18  7:42 ` [PATCH v2 3/3] MAINTAINERS: Add an entry for Amlogic HCI UART (M: Yang Li) Yang Li via B4 Relay

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=ee98ce34-a08b-4aa1-aa16-d3539460c396@amlogic.com \
    --to=yang.li@amlogic.com \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh@kernel.org \
    --cc=will@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;
as well as URLs for NNTP newsgroup(s).