Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp3480045pxb; Mon, 16 Nov 2020 16:15:45 -0800 (PST) X-Google-Smtp-Source: ABdhPJxCE64cNFM8wonyCiQK43fsP7q/nC9shEXOer6SQvM1ORQ9SjFPxaN7cLWG1mUXaVvcYFTc X-Received: by 2002:a17:906:4dd3:: with SMTP id f19mr16057170ejw.364.1605572144934; Mon, 16 Nov 2020 16:15:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1605572144; cv=none; d=google.com; s=arc-20160816; b=PjQxgiUffBPclXHUnT5QM+EL1ODojkBVuqkltc2gkoe2gi+V8KHdRHeiuy6c/PkgbU +N40VE7LXMpNosguzU+/FGZwWQU/7j4AYEtIzbiVaw7t/LcQBeu4QJt0ZqKQERZB01wa YKhuRKVn8KD3a75tCC1qZqVOGg5K0aB5fJPOOILUl2F2NxP6yuNyh/wiJAuogqQwKkCa RMprXjQB5F8hYp5xnT+ejY+er+JF8/8NiFAl+whZqMXQmhvbuInRCcmeInFdkCr4RZ4v GgZ9N9BJlec7pJLn0utmxmN/FWmOmoDciDnQYq89nnvkC+8ADayuuvaJ12qdgcp83w7O dg+w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=v6DVfwneZBucr501V47pRDVWobUXH7yfFy4JGWjeR9Y=; b=mbYmCWLI6R5oHx6/wKV2WuEIJA6OioEV7Ml5OpC1aDi6+yCjSNS8jaycyA7gzv308A NxoVeBNWwH6so4yVsiL7QSX/8NyLIg+V/36qEcInn2ojHYDPldtgvWdBQ3DTmsDtX+Ez uD67Yh/E3IdZyZsyy1Bk9Bq8oq0ubWIVpG0optl2vrllj3k0eEwpbX5YNCpNiq0JqZvq ynll8ATfCnOg923smzblcNf8XJKY8cI7T6jVC+i7QAZpxaIZ4nl6Qw6J3S5Sasb/+tZN ka5G59Mt0Gb3zshIK15JRVbNku52JHQPj97Kl39zxPuRNwfpxxsfw0LFzOq6aE9RL2hs uYpQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id t17si13018286edq.418.2020.11.16.16.15.22; Mon, 16 Nov 2020 16:15:44 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731127AbgKQALB (ORCPT + 99 others); Mon, 16 Nov 2020 19:11:01 -0500 Received: from anhedonia.sammy.net ([67.23.44.4]:54043 "EHLO sammy.net" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1726310AbgKQALA (ORCPT ); Mon, 16 Nov 2020 19:11:00 -0500 X-Greylist: delayed 2620 seconds by postgrey-1.27 at vger.kernel.org; Mon, 16 Nov 2020 19:11:00 EST Received: from sammy by sammy.net with local (Exim 4.63) (envelope-from ) id 1kentn-00010k-IZ; Mon, 16 Nov 2020 18:27:03 -0500 Date: Mon, 16 Nov 2020 18:27:03 -0500 From: Sam Creasey To: Finn Thain Cc: Geert Uytterhoeven , Arnd Bergmann , "linux-kernel@vger.kernel.org" , Russell King , Tony Luck , Fenghua Yu , Greg Ungerer , Philip Blundell , Joshua Thompson , Sam Creasey , "James E.J. Bottomley" , Helge Deller , Thomas Gleixner , Daniel Lezcano , John Stultz , Stephen Boyd , Linus Walleij , "linux-ia64@vger.kernel.org" , Parisc List , linux-m68k , Linux ARM Subject: Re: [RFC 13/13] m68k: mac: convert to generic clockevent Message-ID: <20201116232703.GV14088@anhedonia-3> References: <20201008154651.1901126-1-arnd@arndb.de> <20201008154651.1901126-14-arnd@arndb.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 06, 2020 at 01:52:01PM +1100, Finn Thain wrote: > On Fri, 23 Oct 2020, Geert Uytterhoeven wrote: > > > > > > The arm/rpc timer seems to be roughly in the same category as most > > > > > of the m68k ones or the i8253 counter on a PC. It's possible that > > > > > some of them could use the same logic as > > > > > drivers/clocksource/i8253.o as long as there is any hardware > > > > > oneshot mode. > > > > > > > > There appear to be 15 platforms in that category. 4 have no > > > > clocksource besides the jiffies clocksource, meaning there's no > > > > practical alternative to using a periodic tick, like you did in your > > > > RFC patch: > > > > > > > > arch/m68k/apollo/config.c > > > > arch/m68k/q40/q40ints.c > > > > arch/m68k/sun3/sun3ints.c > > > > arch/m68k/sun3x/time.c > > > > > > Do any of these have users? I'm fairly sure sun3x has never worked in > > > mainline, sun3 seems to still need the same few patches it did 20 > > > years ago. I couldn't find much about Linux on Apollo or q40, the > > > information on the web for either of them seems to all be for > > > linux-2.4 kernels. > > > > They probably don't have any users. > > I have access to several Sun 3 machines but no time to work on that port, > unfortunately. > > Are these 4 platforms (those with no clocksource besides the "jiffies" > clocksource) the only reason for CONFIG_TIME_LOW_RES on m68k? Sun3x was probably at least as close (if not closer) than Sun3 to working in mainline back in the day, but unfortunately I'm in the same place as Finn... I've got the hardware, but time is harder to come by. -- Sam