Received: by 2002:a25:86ce:0:0:0:0:0 with SMTP id y14csp1037728ybm; Tue, 21 May 2019 07:44:46 -0700 (PDT) X-Google-Smtp-Source: APXvYqzO0SwecO2rRpYPUSfm701yGFRpc9o3GQhcxRdQZCG5tOkKA3D9565H0TkyLGKqcSHYae2O X-Received: by 2002:a65:654f:: with SMTP id a15mr66760291pgw.73.1558449886146; Tue, 21 May 2019 07:44:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558449886; cv=none; d=google.com; s=arc-20160816; b=tPj8CpIdqxZj8CTxU7XYvdNBa9ykwD2MQ44bPKRkknZ8fHRTubiQs7aTRTIiD1IzhF YUoG10yjd48fEmHpFI7eoI3GIKo36kTxvj1ayUPLGDuk7j4F2ojoL2Lk7AEFNpfBnPqI Iuk6BiKbggPdothdwCCoi+vRTZHuCbZvHP3ekMUjj6zPlruS2Jav44bF8lyyYeKeu3RK 2FD+JcUvsODvO95DkCLgPC7a7mAldS3FPmheycyWk/SgVZzVHdD3cdIht4padfFkzCeW wVuXI0hNWJDTzw84wgNLiK5cx70QA74H/lvEsHJGE35Fq1ZLbqWfmzQTt0pykimNv50a TLbw== 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:from:date:dkim-signature; bh=jQV6HvXicoQyKlZpuwVbnv3LHUejINnPVjJsxy7NdrU=; b=zFZ8fVjuOH/5mHOzqgbuGrJM4sMNbmxb1l7XzweX5IQhkInsoOBXAIGo48v54q8kkX FecR4fzQVTKZMv1A9GzAZF+gKm6vywIk+hJvZcDDBSKC3dSY9lKP5C23b51NhqRHnyP+ 9o6oulOGMy/hlL2qJZcZPMtuaXwSKu/YFKOxaUBMRfjN8gXfJfFxs+pLQK54MYdrx7uZ AsYqIFdB/Qs91AnvLY30wpAD2CvPMPo2Ud/cjdytA35DBuibpbn7qubAx4uLEpc3bnu1 iS7kkXuCUVmSnzdYzTNGgWv/zlPtSCrxsXa/8WJCLIazNK+scNgEUg5suGmOdphd7tn2 ADxA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=AVgioXlF; 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 3si22634418plo.300.2019.05.21.07.44.30; Tue, 21 May 2019 07:44:46 -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=@kernel.org header.s=default header.b=AVgioXlF; 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 S1728510AbfEUOnX (ORCPT + 99 others); Tue, 21 May 2019 10:43:23 -0400 Received: from mail.kernel.org ([198.145.29.99]:54102 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728256AbfEUOnW (ORCPT ); Tue, 21 May 2019 10:43:22 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 55F0021743; Tue, 21 May 2019 14:43:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1558449801; bh=CjiBRV0KckUnW7Mknwmgco2QEa8JWeLW/S4VvJH8+D4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=AVgioXlFw5pOPCAd/UjFET4MlbCEk0CFtZPTIOpxDQ4UcrOUQxrCdaE5FKkzweBHh xVBTlQmQKGA+qimMoRdVRgi7pycMXn9oVuVLJOXhciC40Hv/oAypuIzoEtZw3UDBXg RTe96lLoGwGm57ajuvWEI6O57AIE3W4Mr6aGgnDc= Date: Tue, 21 May 2019 16:43:19 +0200 From: Greg Kroah-Hartman To: Esben Haabendal Cc: Lee Jones , linux-serial@vger.kernel.org, Jiri Slaby , Nishanth Menon , Vignesh R , Tony Lindgren , Lokesh Vutla , Florian Fainelli , linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/2] serial: 8250: Add support for 8250/16550 as MFD function Message-ID: <20190521144319.GA28747@kroah.com> References: <87bm05mpmx.fsf@haabendal.dk> <20190514104741.GO4319@dell> <20190514122618.GA18859@kroah.com> <87imudky2o.fsf@haabendal.dk> <20190521100904.GA13612@kroah.com> <87pnocm59v.fsf@haabendal.dk> <20190521111817.GA24911@kroah.com> <87lfz0m3ge.fsf@haabendal.dk> <20190521125651.GA6264@kroah.com> <87h89nnajr.fsf@haabendal.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87h89nnajr.fsf@haabendal.dk> User-Agent: Mutt/1.11.4 (2019-03-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 21, 2019 at 04:31:52PM +0200, Esben Haabendal wrote: > Greg Kroah-Hartman writes: > > > On Tue, May 21, 2019 at 01:50:25PM +0200, Esben Haabendal wrote: > >> Greg Kroah-Hartman writes: > >> > >> > On Tue, May 21, 2019 at 01:11:08PM +0200, Esben Haabendal wrote: > >> >> Greg Kroah-Hartman writes: > >> >> > >> >> >> I will try ad hold back with this thread until you get back to it. > >> >> > > >> >> > Ok, I have no idea what is going on here, sorry. This is a really long > >> >> > and meandering thread, and I can't even find the original patches in my > >> >> > queue. > >> >> > > >> >> > So can you resend things and we can start over? :) > >> >> > >> >> Will do. > >> >> > >> >> > But note, using a mfd for a uart seems VERY odd to me... > >> >> > >> >> Ok. In my case, I have a pcie card with an fpga which includes 5 uart > >> >> ports, 3 ethernet interfaces and a number of custom IP blocks. > >> >> I believe that an mfd driver for that pcie card in that case. > >> > > >> > I believe you need to fix that fpga to expose individual pci devices > >> > such that you can properly bind the individual devices to the expected > >> > drivers :) > >> > >> Well, that is really out-of-scope of what I am doing here. > > > > Not really, if you have control over the fpga firmware (and odds are you > > do), just fix that and instantly your device works with all kernels, no > > need to change anything. > > > > Why not do this? > > Because I do not have control over fpga firmware. Who does? Why did they create it this way if it can not be accessed by an operating system as-is? Has it passed the PCI tests? Do you have a link to where you can get this crazy device? > >> > Seriously, who makes such a broken fpga device that goes against the PCI > >> > spec that way? Well, not so much as "goes against it", as "ignores all > >> > of the proper ideas of the past 20 years for working with PCI devices". > >> > >> Might be. But that is the firmware I have to work with here, and I > >> still hope we can find a good solution for implementing a driver without > >> having to maintain out-of-tree patches. > > > > As this hardware will not work on any operating system as-is, why not > > fix the firmware to keep from having to support a one-off device that no > > one else would be crazy enough to create? :) > > Clearly, someone has been crazy enough. Hopefully, we can be smart > enough to make Linux fit to it. Sometimes you need to go tell the hardware/firmware people not to do foolish things. You can not always fix their problems in software. Please push back on this. thanks, greg k-h