Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp1081993imm; Wed, 6 Jun 2018 10:08:19 -0700 (PDT) X-Google-Smtp-Source: ADUXVKLttVUSZ4z1eQsKwHa9zjDcBH14GeHAJMhqA5dg1wmah3KJnk1GYp+CUuome2kQrnQu1x5S X-Received: by 2002:a65:6157:: with SMTP id o23-v6mr3313103pgv.310.1528304899899; Wed, 06 Jun 2018 10:08:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528304899; cv=none; d=google.com; s=arc-20160816; b=xroVucxJSLRqRZFMykq2VpwZVSnnMgsR6LmoTKUaJEg44UKBNW2q8VKWTg0YS3bcw2 rXOFcmYJWBGJdS12+RsaMiYWEgm/iDWYb2lfDQYX6gVB4B8+xHi+cIRAR8LS0bnp2uuB 7srQl+8h84vEWxDfOSHo/R32j2do0wfVWlHjrjtqDaKyBnw/KuFBcRMWdgGktfCbio2f jWyk/J1C9c7qgqGU6XvP1AudGa0fj3JBdBIKjMK+r9/AmO4taGCk/yLfEknrMAtWNPZT ccnOXejYUP4Zro4Zi5wtK5xmLUP1j3HAh4i/O8WqbmaNgIr3U81Ff50CDb2XZDr46x+p Y5Cw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=kOlnb9lxaCWKiotF8BEhLWzL0exIRhGkczeh7NoFbHI=; b=nssRSbtyj9QYvcgmdzZzoRsmFvUbU5pjogOz9EuFodMQ3qda+SH4pPcrn2cx+2T9YU C0+yFc/A06tvaknB+YQVjeettZYskdBwfZTj7teVEU9rBu8+n8VJGnSK1rcV7SMb+mvK W5OApRHslLekgWMMNyGFuGDIZHVYhIXroZiN/yNHYzPWkT9mBFpRfHUk7vVcwChOJCou EMbDX3Yp269DU8uUjeGElslPD0R3sAKNNu7sHa4ezEjtgxeQ0ZksZr9bGvBf4cHqjC/l /goKL+2IPbUzq3mGiZbQIeMy/y5ymsDobs2GZwnUfqTOiwp0WMu+uZezEmM8bBY7QMOO xosQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=P6my/TdB; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z19-v6si9019365pff.100.2018.06.06.10.08.05; Wed, 06 Jun 2018 10:08:19 -0700 (PDT) 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=pass header.i=@gmail.com header.s=20161025 header.b=P6my/TdB; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933663AbeFFRHo (ORCPT + 99 others); Wed, 6 Jun 2018 13:07:44 -0400 Received: from mail-qk0-f194.google.com ([209.85.220.194]:35492 "EHLO mail-qk0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753762AbeFFRHl (ORCPT ); Wed, 6 Jun 2018 13:07:41 -0400 Received: by mail-qk0-f194.google.com with SMTP id d130-v6so4429039qkc.2 for ; Wed, 06 Jun 2018 10:07:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=kOlnb9lxaCWKiotF8BEhLWzL0exIRhGkczeh7NoFbHI=; b=P6my/TdB8worfo0mSysacL7c51ZYjiLjAI7Aulhf9nKjfSvIlSNZ9BGRQyU/umdO5S EW7cJ3LqUPzlEkM9gtSadiRxnhO4OYBwaxrReKS1tdf0Prg1yUAL2Qdbm36NMyjvmcfK Erhum3nnOXiNrMBkwSnFXUNMrdvCu1vozdT17m/t7gqPOyqI7nYLbFET6uQ8MPU6rZsI EdF0sNXShbtvDBJ+0YJJucq8zQy8rBNGzStWLodA/uhLdACVmo/uCNL6dmOFZe2vjYeo eNlwAx/yVlEdqgozjPSVjBDjNFWk/ttZBgouiDFLUULgeLQCg+Bn6DX2/WD9653kdJem JoaA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=kOlnb9lxaCWKiotF8BEhLWzL0exIRhGkczeh7NoFbHI=; b=cDLSURHJnSkHbisylAjLYHtB988tYbBPCyTXHj+yqsedxhQ+/BkfPyJVMdNLAgtDIz Oa20Y3MjtLLzMUKudJnHLmlgIjDWD93woO3597xA338n9jsATLq5BKjuWBAZlSSHY4ky LJteX9jfo34DCjGZYJkarirwWuCTbdZYTB3dwWIUGtnRIwAzBjLGE4cCJ/+5xKrenfRo pAleAuI14DzU+o0E0iPByD3Tu9tauIEZhK8xPiVlqZbP80rbv/YE8/JU7QYtNk0XGEUa oyt3aFMLzbHu5lJCnBFicWbtw2kgO9ty7j/ePt6GsMsqDe0RufHGdPWJzjyWNv+opJT5 ONRA== X-Gm-Message-State: APt69E3GZF3/98pm3S7199fIM5KIG+GtzkAlik/cSOfW01fZXJYLwE1/ 55mQm6nFwNhSO1y+V2wNMvbn8lr2sOKKFh51t1gdr5Hb X-Received: by 2002:a37:ddce:: with SMTP id u75-v6mr3246002qku.147.1528304861124; Wed, 06 Jun 2018 10:07:41 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a0c:98f9:0:0:0:0:0 with HTTP; Wed, 6 Jun 2018 10:07:40 -0700 (PDT) In-Reply-To: References: <20180526193523.3896-1-mattst88@gmail.com> From: Andy Shevchenko Date: Wed, 6 Jun 2018 20:07:40 +0300 Message-ID: Subject: Re: [PATCH] parport: Add support for the WCH384 4S multi-IO card To: Matt Turner Cc: Sudip Mukherjee , LKML , Sergej Pupykin Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 6, 2018 at 8:04 PM, Andy Shevchenko wrote: > On Wed, Jun 6, 2018 at 9:07 AM, Matt Turner wrote: >> On Sat, May 26, 2018 at 12:35 PM, Matt Turner wrote: >>> This Multi-IO card has one serial 16550-like serial connectors. Here's >>> the lspci output, after this commit is applied: >>> >>> 01:00.0 Serial controller [0700]: Device [1c00:3470] (rev 10) (prog-if 05 [16850]) >>> Subsystem: Device [1c00:3470] >>> Flags: fast devsel, IRQ 16 >>> I/O ports at e000 [size=256] >>> Memory at f0100000 (32-bit, prefetchable) [size=32K] >>> I/O ports at e100 [size=4] >>> Expansion ROM at f7d00000 [disabled] [size=32K] >>> Capabilities: [60] Power Management version 3 >>> Capabilities: [68] MSI: Enable- Count=1/32 Maskable+ 64bit+ >>> Capabilities: [80] Express Legacy Endpoint, MSI 00 >>> Capabilities: [100] Advanced Error Reporting >>> Kernel driver in use: parport_serial >>> >>> This card was already added to the blacklist of 8250_pci.c in commit >>> 72a3c0e4e662 ("tty: Add support for the WCH384 4S multi-IO card"). > > First of all, this patch is in conflict with tty-next AFAICS. > > Second, what card w/o parport should do in parport_serial? > > Third, this patch brings more mess: either you should remove the code > from 8250_pci, or do not add it here. See below. > > it looks like the mentioned patch mistakenly added it to blacklist by > unknown reason. > > Feels to me like NAK to this one. > > And btw, you missed s letter in the model name across the code and I > don't see any of cards there listed with numports == 0. Ah, it seems that you have two identical VID:DID devices with either numports == 0 or 1. First one should be served by 8250_pci. The second one indeed is good to have here. Though, how to distinguish them? By PCI class? by sVID:sDID? -- With Best Regards, Andy Shevchenko