Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp6060018ybg; Tue, 22 Oct 2019 12:28:13 -0700 (PDT) X-Google-Smtp-Source: APXvYqwUHtm3fR04whmFRgWsUBNPzJb9VaHlpKTWcDgX6aq2NaHV4oyI1JeaHQH0KluM9inR4xbH X-Received: by 2002:a17:906:f15:: with SMTP id z21mr29412086eji.119.1571772493373; Tue, 22 Oct 2019 12:28:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571772493; cv=none; d=google.com; s=arc-20160816; b=cS3EWP4IB0qhq7qwy4GVlrxWaGGOxbqwqtGmtlCF7iSt/QCp66akZ2cODibxhxmkEM Er/ahQoTBqZ+yfwhMRrinrceaQWv2TkwmwPQ+UWEjqXD5YdBggLsWILjbP1LGOz+rhLZ 1PmfHit+BXdrpuJRWPh42gLhVaSDWqDzBiFgm22jeNky5oisyqWG/G89AJpt65DNEjqc GbYqcmN7JD5z065oPxfSgq3Q0JXyX1WscNmzG3SeQhjvJ9hDTAxUcvFdQkChwcdpN3+n 0h8ul+KBt9SwMOkEb5xf5pjZKQDdPwsnGAjHOeQb+x0uoASQNRfKPV1CRvx9yRyKgIpM pU7g== 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:references :message-id:in-reply-to:subject:cc:to:from:date:dkim-signature; bh=Z35gIg5VNnGoWRkAXQlW7xDcZ9tidybwVVKTt1ULIyc=; b=OGqrU0D2vFMtVF7DCd5j7BJ/uHM9FaF8UR67BIy6v62jUmdeDIay5SrQIhMH/Ob0Oz oot67Hdw9n7VdyWp9g+FLRks6UXaQMWQ9WMT/OfkHH1QuafptBj7LmsjGsyuBpevsKQM EGO6xjusgUfHPl5zZlI2gZeIh2KX2gV4rHH5oCC5xVzvqVw+UClobBn6509yFzIjmazr V+dQ5yc9/uph7QeKP8uLQBElyU5pXJzjZzFSLhl0Ezj4WdzX/i9PkL5sslU2l80qpRNR LNoxamSQrEgUzBLYTJseSuFxQ1T7pW/zgCfH9wWz6f+4pfkR9a39hs/IL4Lu9ozTJbID Ggeg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sifive.com header.s=google header.b="hJDge/es"; 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 o49si12518096edc.261.2019.10.22.12.27.47; Tue, 22 Oct 2019 12:28:13 -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=@sifive.com header.s=google header.b="hJDge/es"; 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 S1732810AbfJVTXO (ORCPT + 99 others); Tue, 22 Oct 2019 15:23:14 -0400 Received: from mail-io1-f66.google.com ([209.85.166.66]:40289 "EHLO mail-io1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727851AbfJVTXO (ORCPT ); Tue, 22 Oct 2019 15:23:14 -0400 Received: by mail-io1-f66.google.com with SMTP id p6so13649190iod.7 for ; Tue, 22 Oct 2019 12:23:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sifive.com; s=google; h=date:from:to:cc:subject:in-reply-to:message-id:references :user-agent:mime-version; bh=Z35gIg5VNnGoWRkAXQlW7xDcZ9tidybwVVKTt1ULIyc=; b=hJDge/esrdfFa6YNY6zLpWrNhnT1vMnK+6yKTySDF7X7A8kCqh7g9VGIGrCqmA3eDy +vJNbdHEIOyA+LAKuepLExmBXpYgtvAgSB46fxRVydVoEIY7Ud4+EggtysvenHkitn6J MxsUlNxJCjHVXO42qsHq7j0dQUXN+zylw/DteC9iJ9z4dY1vUnEQ74ZyGwWYhKEOlPpb 0XHXco2eC7xKOUZWHVbrpMTtsWk9aDmDwJpu2r91G89jJLjmXRtEh36B6kyr5BMttz3s LigN5pbeqY5psQxX7XzLxSxWkHSJkziPmqXJgTSzGbHHCD9zQo26yq4n5eM6oKNyZfMD UrbA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:in-reply-to:message-id :references:user-agent:mime-version; bh=Z35gIg5VNnGoWRkAXQlW7xDcZ9tidybwVVKTt1ULIyc=; b=diHzQu8r/DmhdLPymdAiwvRg+FJJbBT7MgPzGFD5GDBkHe9LNV0ylpE60XPSVvQSCW 1YeFPls2Qhpfc9A4Tt3++RezmI6TbuxQp49FKHjLqC+NPA2WYNgI+6FzDS5jsqmCzCNN ILDF3tuS8jobbY9mS2a6708AIxz8k3kYkKwCAqj2BsXJw3Fvn7SsYRV8rvmqGParV3Ww OIlGz86QT7PqKSCKo4krgEvc676PwttsCrgc5flu4i6RysouQfJJBYCMgVh7JQnMGIs9 XsEX9uUC3wNzYKJayOMZN+KDwwJ4kwNVx2rFIzJcoHCQko59/Vpa5sTsYbx1xDQtskvl eGOQ== X-Gm-Message-State: APjAAAXVnlRHsJjqfvyMt89shComfvI1Hu5eZvlVD80RZPqN/7AvF1U7 jlLzQItSmGni1wKglid2HbzVRw== X-Received: by 2002:a02:3081:: with SMTP id q123mr5395163jaq.24.1571772193149; Tue, 22 Oct 2019 12:23:13 -0700 (PDT) Received: from localhost (67-0-11-246.albq.qwest.net. [67.0.11.246]) by smtp.gmail.com with ESMTPSA id d6sm5642705iop.34.2019.10.22.12.23.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 22 Oct 2019 12:23:12 -0700 (PDT) Date: Tue, 22 Oct 2019 12:23:11 -0700 (PDT) From: Paul Walmsley X-X-Sender: paulw@viisi.sifive.com To: Anup Patel cc: Palmer Dabbelt , "aou@eecs.berkeley.edu" , Greg KH , "rkir@google.com" , Atish Patra , Alistair Francis , Christoph Hellwig , "anup@brainfault.org" , "linux-riscv@lists.infradead.org" , "linux-kernel@vger.kernel.org" Subject: RE: [PATCH v2 2/2] RISC-V: defconfig: Enable Goldfish RTC driver In-Reply-To: Message-ID: References: <20190925063706.56175-3-anup.patel@wdc.com> User-Agent: Alpine 2.21.9999 (DEB 301 2018-08-15) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 14 Oct 2019, Anup Patel wrote: > > -----Original Message----- > > From: Palmer Dabbelt > > Sent: Saturday, October 12, 2019 11:09 PM > > To: Anup Patel > > Cc: Paul Walmsley ; aou@eecs.berkeley.edu; > > Greg KH ; rkir@google.com; Atish Patra > > ; Alistair Francis ; > > Christoph Hellwig ; anup@brainfault.org; linux- > > riscv@lists.infradead.org; linux-kernel@vger.kernel.org; Anup Patel > > > > Subject: Re: [PATCH v2 2/2] RISC-V: defconfig: Enable Goldfish RTC driver > > > > On Tue, 24 Sep 2019 23:38:08 PDT (-0700), Anup Patel wrote: > > > We have Goldfish RTC device available on QEMU RISC-V virt machine > > > hence enable required driver in RV32 and RV64 defconfigs. My understanding is that the Goldfish support is still under discussion on the QEMU side and isn't merged yet - is that accurate? https://lists.gnu.org/archive/html/qemu-devel/2019-10/msg04904.html > > > > Reviewed-by: Palmer Dabbelt > > > > IIRC there was supposed to be a follow-up to your QEMU patch set to rebase > > it on top of a refactoring of their RTC code, but I don't see it in my inbox. LMK > > if I missed it, as QEMU's soft freeze is in a few weeks and I'd like to make > > sure I get everything in. > > I was hoping for QEMU RTC refactoring to be merged soon but it has not > happened so far. I will wait couple of more days then send v3 of QEMU > patches. The patch looks fine to me, but let's wait until the underlying support actually appears on the QEMU "hardware". Could you resend once that's happened? thanks, - Paul