Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3171001yba; Mon, 8 Apr 2019 12:41:59 -0700 (PDT) X-Google-Smtp-Source: APXvYqzFT3rH0ku176A4inPhOWZ1Dd+wt/u96PnJY6cwke5tfA8EF7SD8XiDjwtScAY7IR/cjvqS X-Received: by 2002:a65:6150:: with SMTP id o16mr30029571pgv.285.1554752519270; Mon, 08 Apr 2019 12:41:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554752519; cv=none; d=google.com; s=arc-20160816; b=wgYDMH7a9SJReTgBT6Ld4i/NbRs27oijurGt2rlQ3pGUHGmVEFRDNjKsoMbKjnK6VB /vHWKz+KP+nUucjPBVZY6NNsboI1rgUCgkCfrIUaLnQblX4HXDGUryarCnljia2UCoR+ mhYFqNzWS32fclHByB2alO5Iw1y96RPa9o0vHG/oStWKvNI9AE1fINRZIVPSsOxQqTGG W3FwnQFbKHOH0hv54vBhVh758VhfUOpV/rxhGRyq9ILkJT90GZV439OSgV9dTlMqI39X 7jlZ+YLMzeEa+ObNOkUqaYTvyt3oiRuCPIt1low+AuNmyOQTMy7SDT7XivtuaKZfGpzk bqZw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:message-id :in-reply-to:date:references:subject:cc:to:from; bh=c/GwtjC00GN2+rRYBHC/iF59K1/pBV84KH+tI7VbicQ=; b=QQlHNWobJmmuTfUaSiP6vyscep91e4pzkqeBC9mesTnKQjbnpfsl/YwjS//uhZG41c RjG0yYT9JavfvToRcJsC0AfSxtnCbf7ZrB8zfUxOevASrtM7AAdM10zLnu2gtX9kat08 SDNw7oFIA1IsITPWiBcUOayXNa3qeLdpI+ltj7XS63xFHo5bFmCXcur0syRzwEW3lir5 Ufbiifm69/fuDwRHtRR2IbFEZwwtcw2ZdoRrZIbjI5b2cWAkdu8/uR1Gd9Z++VUYhuad PdKAlEKrRlrZvccpedrAOQ0IYIqnI9q8nbSWAQoM5vIcTt29cCgRLAOR1+UtEQ2XFKe4 cjwg== ARC-Authentication-Results: i=1; mx.google.com; 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 q61si28258630plb.245.2019.04.08.12.41.44; Mon, 08 Apr 2019 12:41:59 -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; 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 S1728977AbfDHTOv (ORCPT + 99 others); Mon, 8 Apr 2019 15:14:51 -0400 Received: from smtp05.smtpout.orange.fr ([80.12.242.127]:41442 "EHLO smtp.smtpout.orange.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728879AbfDHTOt (ORCPT ); Mon, 8 Apr 2019 15:14:49 -0400 Received: from belgarion ([90.76.58.102]) by mwinf5d81 with ME id xvEk1z00A2CLFkS03vElm2; Mon, 08 Apr 2019 21:14:46 +0200 X-ME-Helo: belgarion X-ME-Auth: amFyem1pay5yb2JlcnRAb3JhbmdlLmZy X-ME-Date: Mon, 08 Apr 2019 21:14:46 +0200 X-ME-IP: 90.76.58.102 From: Robert Jarzmik To: Arnd Bergmann Cc: Antonio Ospite , Alexandre Belloni , Harald Welte , linux-rtc@vger.kernel.org, Linux Kernel Mailing List Subject: Re: Removing pcap? (EZX support in mainline linux) References: <20190407140741.GE7480@piout.net> <20190408085812.db187b4a6f8ffc76d3d5ebdc@ao2.it> X-URL: http://belgarath.falguerolles.org/ Date: Mon, 08 Apr 2019 21:14:44 +0200 In-Reply-To: (Arnd Bergmann's message of "Mon, 8 Apr 2019 16:02:11 +0200") Message-ID: <87d0lwpavv.fsf@belgarion.home> User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/26 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Arnd Bergmann writes: > On Mon, Apr 8, 2019 at 8:58 AM Antonio Ospite wrote: >> On Sun, 7 Apr 2019 16:07:41 +0200 >> Alexandre Belloni wrote: >> adding Robert to CC as he is listed as the current maintainer of >> ARM/EZX SMARTPHONES in the MAINTAINERS file. >> >> > I've had a look at the PCAP RTC driver because I'm removing a few >> > deprecated APIs. While doing so, I've discovered that the driver has >> > never worked properly because PCAP_RTC_TOD_MASK and PCAP_RTC_DAY_MASK >> > are both missing a bit so every day would roll over at 18:12:15 and the >> > whole the date would roll over in 2014. >> > >> > I discussed with Arnd about 59ee93a528b9 ("ARM: pxa: remove irq_to_gpio >> > from ezx-pcap driver") and it seems the whole EZX support has been >> > broken for a while. >> > >> >> As Harald said in another message I tried taking over OpenEZX for a >> while, but eventually lost interest. >> >> JFTR some parts of the project has been backed up here: >> https://gitlab.com/openezx >> >> I should also have a git backup of the wiki somewhere. >> >> > Is it worth fixing the RTC driver or could I remove it? >> > >> >> I am not aware of any active user but I'd leave the final word to >> Robert, IIRC he received some EZX hardware "recently". >> >> FWIW I think EZX code can be removed if it is a maintenance burden for >> anyone. > > I would prefer if we could either keep or remove all of the ezx code, but not > just remove a particular driver. Removing it all now would let us skip that > discussion the next time someone has a problem with another device driver > for it. I'm on the same page here. I'm not strongly either for or against EZX removal (which would impact AFAIK 6 old Motorola smartphones). If I can find the wiki archives to cross-check the mask issue (especially PCAP_RTC_DAY_MASK), I wouldn't mind seeing a patch on that if it is kept. If I can make the EZX boot (the one I got from Antonia), I could even test it. As if it's worth it, I'm not personally an active user of this specific platform, so if no one is, one less would be less maintainance burden. Cheers. -- Robert