Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp2048633rwb; Fri, 2 Dec 2022 04:59:41 -0800 (PST) X-Google-Smtp-Source: AA0mqf4+JlkDK7xg+1KfoSWzc6gdEVbs9XiW3xF7I0w7nURwRhKVQm9DwtJ22qiSCsIOghEcjaH3 X-Received: by 2002:aa7:d1c5:0:b0:46b:a536:e8d0 with SMTP id g5-20020aa7d1c5000000b0046ba536e8d0mr12171952edp.261.1669985981351; Fri, 02 Dec 2022 04:59:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669985981; cv=none; d=google.com; s=arc-20160816; b=zmq5Yu+HfHQaugfYofDnlI8r65SDrC0SCx8tVxkBBmReRzkQLl9wLwy/d0yYs5YUKL ERVYBwhMV+NUKwskeNqq6lMWzlOQGgbOq2wV2Y1t8xG1O5F4YrI/1oTX8eafIjs2iTno NeoMGTkcUZGnN1dRtxLu1pl1rPypWqjb+3SB3jkTMpLE/V0bwAG9KySZg1rj/tTMOLuZ RsAveb1EXWKjTWE2A8PS8FDVBX1RjlvEf9xuOE6aGWR/wUc+agSAtAiwuuFq5tX996gs 7haQjw5VWssBPGaJQCjRE0V8/gZE3NsHCaYtpw42NiuBTbEP+s0jYzen6ZQSk9dK+CcS p+xA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=ZK5fcPFDNuOJ4gf893pW7oXnUnoQsb3ngtYlfdnmDE8=; b=LbFbhpw99Q9cYvqQsiOtiW/zZKCDJEdUMwjyab2/teMvC0mOLy1RKKXSwzs0w4FxFW j1oV8Zzr+44hN0IbenvJl+Av3qz27HaqLK0MYh0h0BYaUjctxX4imKp8QOgnLRdUJi3J h80cq1lj8+WKeFAt4fmgGZwEixw9p4XtSm1LkbWW5mJzFGfQZPmrsClLbgOOvTzyl08A AMX42CgJpuXfMB0UnyBCdVgmNBu9Zm6pQgk1W9O6+YoxS6DS9HVp5m49+Bz6toKA8tkQ xr870Q5wnPSfzaGV6HxkgBeFELm62TVj9D28lCZPHRFU2u4SfJph+gzV0ymX7u9SMeDy c7cw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=JGINdKTP; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id cs14-20020a170906dc8e00b007aea6b2696fsi8238906ejc.454.2022.12.02.04.59.17; Fri, 02 Dec 2022 04:59:41 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=JGINdKTP; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233525AbiLBMvN (ORCPT + 84 others); Fri, 2 Dec 2022 07:51:13 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50192 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231493AbiLBMvM (ORCPT ); Fri, 2 Dec 2022 07:51:12 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 23C72CA7A0; Fri, 2 Dec 2022 04:51:11 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id C853EB82162; Fri, 2 Dec 2022 12:51:09 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id EE0E5C433D6; Fri, 2 Dec 2022 12:51:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1669985468; bh=N8iaXOkKMk2SIfbdKoOvU4dUqWAClTiQ1M1kpcY5fRQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=JGINdKTPKXiGv6UTf0X8Qw+ztPj3cqJDc7ewQSCHgZN+TpOy/EsAsvFnTdcex3S4F L1YLM39fspk34rrak5QgmWiM2LPzi2rfMveQw/CoNRQAbLqMnUC8SRldMmdikyNFGU jT4x0NFBnRvLsvIvxOSXJjeNDGMCwAWBUTx5yG78= Date: Fri, 2 Dec 2022 13:51:04 +0100 From: Greg Kroah-Hartman To: Krzysztof Kozlowski Cc: Mathias Nyman , Arnd Bergmann , Daehwan Jung , Rob Herring , Krzysztof Kozlowski , Alim Akhtar , Mathias Nyman , Linus Walleij , Colin Ian King , Artur Bujdoso , Juergen Gross , Tomer Maimon , "open list:USB SUBSYSTEM" , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "moderated list:ARM/SAMSUNG S3C, S5P AND EXYNOS ARM ARCHITECTURES" , "open list:ARM/SAMSUNG S3C, S5P AND EXYNOS ARM ARCHITECTURES" , open list , sc.suh@samsung.com, taehyun.cho@samsung.com, jh0801.jung@samsung.com, eomji.oh@samsung.com Subject: Re: [RFC PATCH v1 2/2] usb: host: add xhci-exynos to support Exynos SOCs Message-ID: References: <1669860811-171746-1-git-send-email-dh10.jung@samsung.com> <1669860811-171746-3-git-send-email-dh10.jung@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Dec 02, 2022 at 01:23:56PM +0100, Krzysztof Kozlowski wrote: > On 02/12/2022 13:22, Mathias Nyman wrote: > > On 1.12.2022 11.01, Arnd Bergmann wrote: > >> On Thu, Dec 1, 2022, at 09:06, Greg Kroah-Hartman wrote: > >>> On Thu, Dec 01, 2022 at 11:13:31AM +0900, Daehwan Jung wrote: > >>>> This driver works with xhci platform driver. It needs to override > >>>> functions of xhci_plat_hc_driver. Wakelocks are used for sleep/wakeup > >>>> scenario of system. > >>> > >>> So this means that no other platform xhci driver can be supported in the > >>> same system at the same time. > >>> > >>> Which kind of makes sense as that's not anything a normal system would > >>> have, BUT it feels very odd. This whole idea of "override the platform > >>> driver" feels fragile, why not make these just real platform drivers and > >>> have the xhci platform code be a library that the other ones can use? > >>> That way you have more control overall, right? > > > > Agree that overriding the generic platform driver xhci_hc_platform_driver > > from this exynos driver is odd. > > > > But I don't understand how this works. > > Where are the hcds created and added when this xhci-exonys driver binds to > > the device? all this driver does in probe is the overriding? > > > > Am I missing something here? > > Because it is not a driver for Exynos... it's a driver for wakelocks for > their specific Android use-cases which the manufacturer ships for their > Android devices. Due to Google GKI, they try to squeeze into upstream. GKI has nothing to do with this, this is Samsung not understanding how to properly submit code upstream. Odd that it comes down to them only as this same driver is used by _many_ OEMs who have good teams that know how to upstream code properly. All the blame shouldn't be on Samsung right now (see Google's last attempt at getting USB hooks accepted for this same hardware IP block...) thanks, greg k-h