From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B122BC43217 for ; Fri, 14 Oct 2022 09:37:49 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229783AbiJNJhs (ORCPT ); Fri, 14 Oct 2022 05:37:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48596 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230104AbiJNJhq (ORCPT ); Fri, 14 Oct 2022 05:37:46 -0400 Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 15DA916086B; Fri, 14 Oct 2022 02:37:45 -0700 (PDT) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 072865C00BA; Fri, 14 Oct 2022 05:37:42 -0400 (EDT) Received: from imap51 ([10.202.2.101]) by compute3.internal (MEProxy); Fri, 14 Oct 2022 05:37:42 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arndb.de; h=cc :cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm2; t=1665740262; x=1665826662; bh=psRGotoCAz loqk1qZuGwB6mybx3HJ07mki+PNF3q/YQ=; b=F9sOVc/vcSeuRDFyhAG6ap5rJs gGKFd6STnjAnczslV9BWi4dcYPnj5MhDoPmVmUU9sQtwQ+6Q+65bIUwkMgt6lciZ 4b++m8elA7yXphM+QbXG79bHPz+Tby3zz5lsBIuzcm46viciXa1Vc+AY0Rpkmbh+ v+9E7hLi8GBl8XNlllQDjHoEOA+FSM7RzGTGeB8cMOaGjd1YAs2k/nWivVQbqDME U4Z1FyZj9XSS9yEtXuqQo+ZkzlHk/+vq+jlws/hyFDDz60lFFk8kTMTiWj/ryvFD 1bIK04TtEwA0MNIZZzulpKrxr+kERu60ScFXt79EoQKf0etwFsaU6jg1SvVg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1665740262; x=1665826662; bh=psRGotoCAzloqk1qZuGwB6mybx3H J07mki+PNF3q/YQ=; b=LtoSLpDYcaC2rGFCLZR1DEuzYafMUgca6L5zhEh3OUb+ gPgXZWHFDG3StO2vUjLqeCSrEAAEqihFdxSR+rQoAB21KI7XfTUKaGshH5T6Ckv/ OnF1brWCarPFSkuAgnsOEy0z4Mm8pmcXQsuTR0NLXtlBBGjZgP6k64+dWjGRiROn OQGGTQ5JrwnGjroffmRlZda1TIBRUz644Hxf5IeulXhbHHTVutGT3Z/MuASXKzb9 4lIp8oe/nnLiaqbLnOJEjEmFIbtEixpe4kAoSd0VHYG9zuEwkvPsjRX/sy8CSOc2 Er9Ddg1OrGEJTE1V4tYlqTO7eYBex+7vV/sWRfY+cQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfeekvddgudekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvfevufgtsehttdertderredtnecuhfhrohhmpedftehr nhguuceuvghrghhmrghnnhdfuceorghrnhgusegrrhhnuggsrdguvgeqnecuggftrfgrth htvghrnhepffehueegteeihfegtefhjefgtdeugfegjeelheejueethfefgeeghfektdek teffnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprg hrnhgusegrrhhnuggsrdguvg X-ME-Proxy: Feedback-ID: i56a14606:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id DA3A9B60086; Fri, 14 Oct 2022 05:37:40 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.7.0-alpha0-1047-g9e4af4ada4-fm-20221005.001-g9e4af4ad Mime-Version: 1.0 Message-Id: In-Reply-To: References: <7ee4a1bd-0674-42d8-8980-8b029ca09e71@app.fastmail.com> <75eaeab3-7781-d60a-ae61-ae837f5dcec9@opensource.wdc.com> Date: Fri, 14 Oct 2022 11:37:20 +0200 From: "Arnd Bergmann" To: "Anders Roxell" , "Damien Le Moal" Cc: "Naresh Kamboju" , "Serge Semin" , "open list" , "Linux ARM" , regressions@lists.linux.dev, "open list:LIBATA SUBSYSTEM (Serial and Parallel ATA drivers)" , lkft-triage@lists.linaro.org, "Lukas Bulwahn" , "Niklas Cassel" Subject: Re: TI: X15 the connected SSD is not detected on Linux next 20221006 tag Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-ide@vger.kernel.org On Fri, Oct 14, 2022, at 11:22 AM, Anders Roxell wrote: > On Fri, 14 Oct 2022 at 09:53, Damien Le Moal > Tested this patch on todays linux-next tag: next-20221014 without enabling > CONFIG_AHCI_DWC and it worked as expected when booting [1]. > On the other hand I also tried a build/boot with CONFIG_AHCI_DWC enabled > and it worked as expected to boot [2]. Ok, great. Can you a patch to soc@kernel.org to enable the driver in the relevant defconfigs? > However, during building a warning [3] popped up: > > make --silent --keep-going --jobs=8 > O=/home/tuxbuild/.cache/tuxmake/builds/2/build ARCH=arm > CROSS_COMPILE=arm-linux-gnueabihf- 'CC=sccache > arm-linux-gnueabihf-gcc' 'HOSTCC=sccache gcc' > /builds/linux/drivers/ata/ahci_dwc.c:462:34: warning: 'ahci_dwc_plat' > defined but not used [-Wunused-variable] > 462 | static struct ahci_dwc_plat_data ahci_dwc_plat = { Strange, I can't reproduce this, and the ahci_dwc_plat symbol looks like it is clearly used in ahci_dwc_of_match[], at least in next-20221014. Do you also see this on mainline? Arnd