public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Puma Hsu <pumahsu@google.com>
Cc: mathias.nyman@intel.com, Thinh.Nguyen@synopsys.com,
	badhri@google.com, royluo@google.com, howardyen@google.com,
	albertccwang@google.com, raychi@google.com,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH 2/3] usb: xhci: Add support for Google XHCI controller
Date: Mon, 19 Feb 2024 07:30:33 +0100	[thread overview]
Message-ID: <2024021906-celestial-tuesday-bd24@gregkh> (raw)
In-Reply-To: <20240219061008.1761102-3-pumahsu@google.com>

On Mon, Feb 19, 2024 at 02:10:07PM +0800, Puma Hsu wrote:
> diff --git a/drivers/usb/host/xhci-goog.c b/drivers/usb/host/xhci-goog.c
> new file mode 100644
> index 000000000000..db027a5866db
> --- /dev/null
> +++ b/drivers/usb/host/xhci-goog.c
> @@ -0,0 +1,154 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * xhci-goog.c - xHCI host controller driver platform Bus Glue.
> + *
> + * Copyright (c) 2024 Google LLC

This code is older than 2024, right?  :)

> +	if (WARN_ON(!sysdev->dma_mask)) {

If this triggers, you just rebooted your device (as you run with
panic-on-warn enabled), so please, if this is something that can
actually happen, handle it properly and move on, don't reboot a device.

> +MODULE_ALIAS("platform:xhci-hcd-goog");

Why is this alias needed?  I thought that was only for older-style
platform devices

> +static int __init xhci_goog_init(void)
> +{
> +	return platform_driver_register(&usb_goog_xhci_driver);
> +}
> +module_init(xhci_goog_init);
> +
> +static void __exit xhci_goog_exit(void)
> +{
> +	platform_driver_unregister(&usb_goog_xhci_driver);
> +}
> +module_exit(xhci_goog_exit);

module_platform_driver()?

thanks,

greg k-h

  reply	other threads:[~2024-02-19  6:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19  6:10 [PATCH 0/3] usb: xhci: Add support for Google XHCI controller Puma Hsu
2024-02-19  6:10 ` [PATCH 1/3] dt-bindings: usb: Add xhci glue driver support Puma Hsu
2024-02-19 12:18   ` Krzysztof Kozlowski
2024-02-19  6:10 ` [PATCH 2/3] usb: xhci: Add support for Google XHCI controller Puma Hsu
2024-02-19  6:30   ` Greg KH [this message]
2024-02-21  9:22     ` Puma Hsu
2024-02-19 12:21   ` Krzysztof Kozlowski
2024-02-21  9:31     ` Puma Hsu
2024-02-21  9:52       ` Krzysztof Kozlowski
2024-02-22  9:45         ` Puma Hsu
2024-02-19  6:10 ` [PATCH 3/3] MAINTAINERS: Add maintainer for Google USB XHCI driver Puma Hsu
2024-02-19  6:31   ` Greg KH
2024-02-19  8:35     ` Puma Hsu

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=2024021906-celestial-tuesday-bd24@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=albertccwang@google.com \
    --cc=badhri@google.com \
    --cc=howardyen@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=pumahsu@google.com \
    --cc=raychi@google.com \
    --cc=royluo@google.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