[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <878suzn9wx.fsf@haabendal.dk>
Date: Tue, 21 May 2019 16:45:34 +0200
From: Esben Haabendal <esben@...bendal.dk>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-serial@...r.kernel.org, Lee Jones <lee.jones@...aro.org>,
Enrico Weigelt <lkml@...ux.net>, Jiri Slaby <jslaby@...e.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Darwin Dingel <darwin.dingel@...iedtelesis.co.nz>,
Jisheng Zhang <Jisheng.Zhang@...aptics.com>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
He Zhe <zhe.he@...driver.com>, Marek Vasut <marex@...x.de>,
Douglas Anderson <dianders@...omium.org>,
Paul Burton <paul.burton@...s.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH resend] serial: 8250: Add support for using platform_device resources
Greg Kroah-Hartman <gregkh@...uxfoundation.org> writes:
> On Tue, May 21, 2019 at 01:34:26PM +0200, Esben Haabendal wrote:
>> Allow getting memory resource (mapbase or iobase) as well as irq from
>> platform_device resources.
>>
>> The UPF_DEV_RESOURCES flag must be set for devices where platform_device
>> resources are to be used. When not set, driver behaves as before.
>
> Nothing actually sets this flag in this patch, so I can't take this as
> you are adding new features that no one uses :(
>
> Where is the driver that sets this?
It sits here. It is a rather big and clunky mfd driver, not ready for
upstreaming in its current form. I hope to get around to clean it up.
But it is for a very specific hardware that is really available or
usable for anybody else. Does it make sense to spend effort on
submitting such a driver?
/Esben
Powered by blists - more mailing lists