Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp4463086ybv; Tue, 25 Feb 2020 20:51:25 -0800 (PST) X-Google-Smtp-Source: APXvYqy9FgrVwJHBvpz1An633g+91MDlLb/FflfBGP+MjJz421QZUAs2SVtNbv0d9LZCkREg+oa8 X-Received: by 2002:a05:6830:1598:: with SMTP id i24mr1661029otr.260.1582692685564; Tue, 25 Feb 2020 20:51:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1582692685; cv=none; d=google.com; s=arc-20160816; b=G/S2BCk1JCHtyxkhPRl4i0j7bdVMfgo4HRaiOrcuImmvxlPcBEGUcHTKEj3f8qpM7O HnmfvBWF7uddOUhhTC2orFL5+58FiUn9ICF0NQg7W3dbBvW9Rw2VqwIYLtnM5auN67ft c8prDWtEvBJWS+JqNHvQqSVPrY9u/Af6z1mpniEBHVPMNIVyYVFe0DlfRGnfxC15gp+R l1L4pGzBfJEJb2HanqmdcBb8mSE7lrdjPI9vDm5VXn2F/ViiO/p5yVbYHNAAAQ9KI6jP ymKvTVMJ3uKYyMHl7XZGjvu5bcS8Rjs2KDo14lawf1L6KXb4+WZ4L6nafZnsL8tLHWFo VQTQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:date:from:dkim-signature; bh=aVk24eLY14K87OU1OB1xgRnj/7rTwtwPZpvkthfcADk=; b=qGTfvgDZBWEJWOZZMPb4HR4ZvG8YkL+K5Vuz4cmfrUieBtrYHLBnJ3f9a9iGPDG5pe d4T4MZEi5AGQ+N7E5HqZ00/tSMtKa6z+BTKUnwUfMXZ68EtjV0WuhOX2s/cAfy5+LMZy SQ8Xe+5+fHpiSk44XtFc8i/uszFJ8GJuZpLXMLd0WbufmoBjSXceTb+Ea4uqiAhfxxKV 9XItAY3iQRsknN8sFMLWRfSGHwr8Z0Rs1QTL+6lb+8STwDpp6xwlxhqiXIVtJ6MVcjQT I/Rx4RKnTFJYiciD1nAJc54yEb56ggRD5Z8OjLLn9awdMes55QlQYNb6LwDhxp5aumCg 1sBQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=d3+VJ6Im; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i17si510680oii.95.2020.02.25.20.51.12; Tue, 25 Feb 2020 20:51:25 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=d3+VJ6Im; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726561AbgBZEvJ (ORCPT + 99 others); Tue, 25 Feb 2020 23:51:09 -0500 Received: from mail-qv1-f51.google.com ([209.85.219.51]:39607 "EHLO mail-qv1-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726046AbgBZEvJ (ORCPT ); Tue, 25 Feb 2020 23:51:09 -0500 Received: by mail-qv1-f51.google.com with SMTP id y8so757840qvk.6; Tue, 25 Feb 2020 20:51:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:date:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=aVk24eLY14K87OU1OB1xgRnj/7rTwtwPZpvkthfcADk=; b=d3+VJ6ImQ8PNewkBm3dvALg/VYUIIY+pxIrYJwAoNyrcT52kEPGyTX4NBdE4k+YCSR c0Zy3/LNfKwzOKyytGbqnInfSj+y+5fAUr/4dmLzkyYC4dZxYTFheluz26HCnrt76mr1 4pbNbHfgppu3jRIcZlowuZ+eaFd4Uj/IreXvWwHnVw603SEW5uD8l2djXvPE94STKtbT KuGNFvS0fRTYSvsrDcF9Yq0ADcm0Z3qvpcjECwKDyk18HNgq0G/1exbTan3P653BH0DF 4nXtyzJrvr4KHRT17SJ988PeR0Mtf6VEp5sfuR3wEorl559E9OTVPwwT8c0dBGQNj4t0 TPSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:date:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=aVk24eLY14K87OU1OB1xgRnj/7rTwtwPZpvkthfcADk=; b=cILNXnMEbVai1CFF5DlpiJIr2Ash+ISHbFK6a6EfxyEKSC9XUUkN7XTWuVC1BwNCsA VWcvPKphAQBcmNDdD7z5B659o3i17gXduPfUZPgro7Fv8rjDVCBVEJCJY14PUi7mC9Fh JN95dcR0MD3nQf36bnrhVLkbyVx6cr6VP8ocXrObizVWzdHpz2eAx8DKlnsMq2+nFEkC +PGcYYOLMXuFW0M1RgGAIdyABrbd+YImdzE1Yw1mxEJCTAmsnJdDdDPdFrqhmLEiffrW WcB3aNfTHGTWfNfRey4Lo3aHm6kHnPS1ORTlu5e0w2mLVU1UrYVGfoWl6zja2rhH5sfz IDTg== X-Gm-Message-State: APjAAAUXTIC7n7xnnDFF3xinAGwjIjKUbk4tb7hspvy2YlrUoHgvk2pg hw224Lc7YuXU2GBbjPzi/FE= X-Received: by 2002:a0c:cd8e:: with SMTP id v14mr3118531qvm.182.1582692667662; Tue, 25 Feb 2020 20:51:07 -0800 (PST) Received: from rani.riverdale.lan ([2001:470:1f07:5f3::b55f]) by smtp.gmail.com with ESMTPSA id q5sm501066qkf.14.2020.02.25.20.51.06 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 25 Feb 2020 20:51:07 -0800 (PST) From: Arvind Sankar X-Google-Original-From: Arvind Sankar Date: Tue, 25 Feb 2020 23:51:05 -0500 To: Trevor Jacobs Cc: "Michael ." , Arvind Sankar , Ulf Hansson , Bjorn Helgaas , Dominik Brodowski , Linux PCI , Linux Kernel Mailing List , Kris Cleveland , Jeff , Morgan Klym , Philip Langdale , Pierre Ossman , Maxim Levitsky , "linux-mmc@vger.kernel.org" Subject: Re: PCI device function not being enumerated [Was: PCMCIA not working on Panasonic Toughbook CF-29] Message-ID: <20200226045104.GA2191053@rani.riverdale.lan> References: <20191029170250.GA43972@google.com> <20200222165617.GA207731@google.com> <20200226011310.GA2116625@rani.riverdale.lan> <6e9db1f6-60c4-872b-c7c8-96ee411aa3ca@aol.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <6e9db1f6-60c4-872b-c7c8-96ee411aa3ca@aol.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 25, 2020 at 09:12:48PM -0600, Trevor Jacobs wrote: > That's correct, I tested a bunch of the old distros including slackware, > and 2.6.32 is where the problem began. > > Also, the Panasonic Toughbook CF-29s effected that we tested are the > later marks, MK4 and MK5 for certain. The MK2 CF-29 worked just fine > because it has different hardware supporting the PCMCIA slots. I have > not tested a MK3 but suspect it would work ok as it also uses the older > hardware. > > Thanks for your help guys! > Trevor > Right, the distros probably all enabled MMC_RICOH_MMC earlier than upstream. Can you test a custom kernel based off your distro kernel but just disabling that config option? That's probably the easiest fix currently, even though not ideal. Perhaps there should be a command line option to disable specific pci quirks to make this easier. An ideal fix is I feel hard, given this quirk is based on undocumented config registers -- it worked on Dell machines (that's where the original authors seem to have gotten their info from), perhaps they had only one Cardbus slot, but the code ends up disabling your second Cardbus slot instead of disabling the MMC controller.