From: Krzysztof Kozlowski <krzk@kernel.org>
To: yang.li@amlogic.com, 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, Ye He <ye.he@amlogic.com>
Subject: Re: [PATCH 2/4] Bluetooth: hci_uart: Add support for Amlogic HCI UART
Date: Sun, 7 Jul 2024 15:10:58 +0200 [thread overview]
Message-ID: <3e364c38-c5ac-49e6-9a9b-5b2b4e3cf5a1@kernel.org> (raw)
In-Reply-To: <20240705-btaml-v1-2-7f1538f98cef@amlogic.com>
On 05/07/2024 13:20, Yang Li via B4 Relay wrote:
> From: Yang Li <yang.li@amlogic.com>
>
> This patch introduces support for Amlogic Bluetooth controller over
> UART. In order to send the final firmware at full speed. It is a pretty
> straight forward H4 driver with exception of actually having it's own
> setup address configuration.
>
> Co-developed-by: Ye He <ye.he@amlogic.com>
Read submitting patches. Missing SoB.
> Signed-off-by: Yang Li <yang.li@amlogic.com>
> ---
> drivers/bluetooth/Kconfig | 13 +
> +
> +static void aml_serdev_remove(struct serdev_device *serdev)
> +{
> + struct aml_serdev *amldev = serdev_device_get_drvdata(serdev);
> +
> + hci_uart_unregister_device(&amldev->serdev_hu);
> +}
> +
> +static const struct aml_device_data data_w155s2 __maybe_unused = {
> + .iccm_offset = 256 * 1024,
> +};
> +
> +static const struct aml_device_data data_w265s2 __maybe_unused = {
How this can be "maybe_unused" while it is referenced always? This is
buggy. Either everything in OF chain can be unused or not. Not half yes,
half not.
> + .iccm_offset = 384 * 1024,
> +};
> +
> +static const struct of_device_id aml_bluetooth_of_match[] = {
> + { .compatible = "amlogic,w155s2-bt", .data = &data_w155s2 },
> + { .compatible = "amlogic,w265s2-bt", .data = &data_w265s2 },
> + { /* sentinel */ },
> +};
> +
> +static struct serdev_device_driver aml_serdev_driver = {
> + .probe = aml_serdev_probe,
> + .remove = aml_serdev_remove,
> + .driver = {
> + .name = "hci_uart_aml",
> + .of_match_table = of_match_ptr(aml_bluetooth_of_match),
So now you have warnings... drop of_match_ptr.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-07-07 13:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 11:20 [PATCH 0/4] Add support for Amlogic HCI UART Yang Li via B4 Relay
2024-07-05 11:20 ` [PATCH 1/4] dt-bindings: net: bluetooth: Add support for Amlogic Bluetooth Yang Li via B4 Relay
2024-07-07 13:08 ` Krzysztof Kozlowski
2024-07-11 10:58 ` Yang Li
2024-07-05 11:20 ` [PATCH 2/4] Bluetooth: hci_uart: Add support for Amlogic HCI UART Yang Li via B4 Relay
2024-07-07 13:10 ` Krzysztof Kozlowski [this message]
2024-07-11 10:33 ` Yang Li
2024-07-09 14:41 ` Luiz Augusto von Dentz
2024-07-11 11:59 ` Yang Li
2024-07-05 11:20 ` [PATCH 3/4] arm64: defconfig: Enable hci_uart for Amlogic Bluetooth Yang Li via B4 Relay
2024-07-07 13:08 ` Krzysztof Kozlowski
2024-07-11 11:40 ` Yang Li
2024-07-11 12:19 ` Krzysztof Kozlowski
2024-07-12 11:13 ` Yang Li
2024-07-05 11:20 ` [PATCH 4/4] MAINTAINERS: Add an entry for Amlogic HCI UART Yang Li via B4 Relay
2024-07-07 13:11 ` Krzysztof Kozlowski
2024-07-11 10:59 ` Yang Li
2024-07-12 12:34 ` Paul Menzel
2024-07-16 2:48 ` Yang Li
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=3e364c38-c5ac-49e6-9a9b-5b2b4e3cf5a1@kernel.org \
--to=krzk@kernel.org \
--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=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 \
--cc=yang.li@amlogic.com \
--cc=ye.he@amlogic.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;
as well as URLs for NNTP newsgroup(s).