public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: "Christian A. Ehrhardt" <lk@c--e.de>
Cc: linux-usb@vger.kernel.org, Dell.Client.Kernel@dell.com,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Neil Armstrong" <neil.armstrong@linaro.org>,
	"Hans de Goede" <hdegoede@redhat.com>,
	"Jack Pham" <quic_jackp@quicinc.com>,
	"Fabrice Gasnier" <fabrice.gasnier@foss.st.com>,
	"Samuel Čavoj" <samuel@cavoj.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] usb: ucsi: Add quirk infrastructure
Date: Mon, 15 Jan 2024 09:53:13 +0200	[thread overview]
Message-ID: <ZaTkaf/OmhvEr7ZI@kuha.fi.intel.com> (raw)
In-Reply-To: <20240107001701.130535-3-lk@c--e.de>

On Sun, Jan 07, 2024 at 01:16:59AM +0100, Christian A. Ehrhardt wrote:
> Allow bus drivers to specify quirks for the UCSI core on
> attach. Allow the user to override the quirks on the command
> line.
> 
> Signed-off-by: Christian A. Ehrhardt <lk@c--e.de>
> ---
>  Documentation/admin-guide/kernel-parameters.txt |  5 +++++
>  drivers/usb/typec/ucsi/ucsi.c                   | 12 +++++++++++-
>  drivers/usb/typec/ucsi/ucsi.h                   |  6 +++++-
>  drivers/usb/typec/ucsi/ucsi_acpi.c              |  2 +-
>  drivers/usb/typec/ucsi/ucsi_ccg.c               |  2 +-
>  drivers/usb/typec/ucsi/ucsi_glink.c             |  2 +-
>  drivers/usb/typec/ucsi/ucsi_stm32g0.c           |  2 +-
>  7 files changed, 25 insertions(+), 6 deletions(-)
> 
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 0a6a4b7f7a3b..fd8152dd4450 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -6783,6 +6783,11 @@
>  			<port#>,<js1>,<js2>,<js3>,<js4>,<js5>,<js6>,<js7>
>  			See also Documentation/input/devices/joystick-parport.rst
>  
> +	typec_ucsi.quirks=	[USB]
> +			A hex value specifying the quirks to enable for
> +			the USB Type-C connector system software interface
> +			driver. This overrides auto detected quirks.

New module parameters are not going to be accepted.

Please just fix the issue with Dell's first like I proposed, and then
you can start thinking about the infra for the quirks.

thanks,


-- 
heikki

  reply	other threads:[~2024-01-15  7:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-07  0:16 [PATCH 0/4] Make UCSI on Dell Latitude work Christian A. Ehrhardt
2024-01-07  0:16 ` [PATCH 1/4] usb: ucsi: Add missing ppm_lock Christian A. Ehrhardt
2024-01-07  0:16 ` [PATCH 2/4] usb: ucsi: Add quirk infrastructure Christian A. Ehrhardt
2024-01-15  7:53   ` Heikki Krogerus [this message]
2024-01-07  0:17 ` [PATCH 3/4] usb: ucsi: Quirk to ack a connector change ack cmd Christian A. Ehrhardt
2024-01-07  0:17 ` [PATCH 4/4] usb: ucsi: Apply UCSI_ACK_CONNECTOR_CHANGE_ACK_CMD to Dell systems Christian A. Ehrhardt
2024-01-15  9:05   ` Heikki Krogerus
2024-01-15 11:57     ` Christian A. Ehrhardt

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=ZaTkaf/OmhvEr7ZI@kuha.fi.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=Dell.Client.Kernel@dell.com \
    --cc=fabrice.gasnier@foss.st.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lk@c--e.de \
    --cc=neil.armstrong@linaro.org \
    --cc=quic_jackp@quicinc.com \
    --cc=samuel@cavoj.net \
    /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