From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7581CC43219 for ; Fri, 3 May 2019 19:05:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4397E2075C for ; Fri, 3 May 2019 19:05:14 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=sifive.com header.i=@sifive.com header.b="YyLoqA+M" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726939AbfECTFN (ORCPT ); Fri, 3 May 2019 15:05:13 -0400 Received: from mail-it1-f195.google.com ([209.85.166.195]:35283 "EHLO mail-it1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726913AbfECTFM (ORCPT ); Fri, 3 May 2019 15:05:12 -0400 Received: by mail-it1-f195.google.com with SMTP id l140so10696246itb.0 for ; Fri, 03 May 2019 12:05:11 -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=WUEvVuMZ7YPl2dVmcnur9vXgWXYbDp4Kv2NYf/KfC/E=; b=YyLoqA+MOSgu5Z/mdOZYresCbnsrP9MOECqAR4bgemiqd1NPH4z1kTNshqMr1wGxrO 1ulkumKpTQ6uWLtA2Ene+eq+HrTs1KZoMqs9xg+p39iicmy0zTCL7uVABR+WOuDZA063 +oNPgr10wY9fURWnsMIn4Glzq/w4seTiQt6nzHUkagCRCpv7txThNbb5poKXXUtiaq0C amJC+5CNfkSN3LxFTXn27zjZN09O67v/k/iPmRYOidALpODycYOWZxGJ1kWkYY3q8zeE jHByq6IVQuw2xmMN/9K1zm6po5Ybx+hPTG4ELBhJgSBqEWzHWP+zmvqJygso2YzaXz1P hhwg== 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=WUEvVuMZ7YPl2dVmcnur9vXgWXYbDp4Kv2NYf/KfC/E=; b=fbq3Fj35ZPg3+LCrg8HFT7zuOkPPklcBOhhdB8Lj8qPvlQE3lqwd9LRrbIuWhQJccK AX/bXg/71/4tLipNGGI8RXuXzLbIC29Te2EEWRwSOWTX+qhPcS1uoyCvkkp8D+TjBho8 sn+50tJ18bUlfU3hJ37wx2m3M67G0JSMgVUYwUcze7/2XcHYLn6WChiJQKL0cJ0amt+W u9o8jreoJti/fmVFBYKCCVrvsCrJp577JKZmrf1aM+bJ2hP0qdmzmQwDcRO5WXOELQB8 EkPT9+YgoTxrQRvBIU2NDZiNYRFLS5xR7/XWmJPabe49YoAf2p70k8Ykl5GrDgGZu9sh 5iZQ== X-Gm-Message-State: APjAAAVJ9dRsrahRimg2QQYevAl9fXdyIGcZXjLjbUCo6eo6vpFdoop/ TbJtu1zVvu1dZL7Gs6MasSQqAg== X-Google-Smtp-Source: APXvYqzFS3nViSd8Ml55qWBQUACdB1pGNmsO/5+y7g1p6Gt2X232FHXVSyZ7sg92TLGrQz/n1IlHPQ== X-Received: by 2002:a02:1146:: with SMTP id 67mr8522400jaf.10.1556910311443; Fri, 03 May 2019 12:05:11 -0700 (PDT) Received: from localhost (74-95-18-198-Albuquerque.hfc.comcastbusiness.net. [74.95.18.198]) by smtp.gmail.com with ESMTPSA id d193sm1154451iog.34.2019.05.03.12.05.10 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 03 May 2019 12:05:10 -0700 (PDT) Date: Fri, 3 May 2019 12:05:09 -0700 (PDT) From: Paul Walmsley X-X-Sender: paulw@viisi.sifive.com To: Kevin Hilman cc: Paul Walmsley , Atish Patra , "linux-kernel@vger.kernel.org" , "linux-serial@vger.kernel.org" , "linux-riscv@lists.infradead.org" , "gregkh@linuxfoundation.org" Subject: Re: [PATCH v5 0/2] tty: serial: add DT bindings and serial driver for the SiFive FU540 UART In-Reply-To: <7hsgtwlm5t.fsf@baylibre.com> Message-ID: References: <20190413020111.23400-1-paul.walmsley@sifive.com> <7hmukmew5j.fsf@baylibre.com> <883f3d5f-9b04-1435-30d3-2b48ab7eb76d@wdc.com> <7h5zr9dcsi.fsf@baylibre.com> <7htvetbupi.fsf@baylibre.com> <7hsgtwlm5t.fsf@baylibre.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 Thu, 2 May 2019, Kevin Hilman wrote: > Paul Walmsley writes: > > > I'd recommend testing the DT patches with BBL and the open-source FSBL. > > That's the traditional way of booting RISC-V Linux systems. > > OK, but as you know, not the tradiaional way of booting most other linux > systems. ;) > > I'm working on getting RISC-V supported in kernelCI in a fully-automated > way, and I don't currently have the time to add add support for BBL+FSBL > to kernelCI automation tooling, so having u-boot support is the best way > to get support in kernelCI, IMO. That's great. Please keep hacking away on RISC-V support for kernelCI. My point is just that the U-boot and OpenSBI software stack you're working with is not going to be useful for automatic tests of some kernel patches yet. That stack is still very new, and was written around a non-upstream set of DT data. We are in the process of posting and merging patches to fix that, but it's going to take a few releases of both the kernel and those other boot stack components until things are sorted out in a more durable way. - Paul From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Walmsley Subject: Re: [PATCH v5 0/2] tty: serial: add DT bindings and serial driver for the SiFive FU540 UART Date: Fri, 3 May 2019 12:05:09 -0700 (PDT) Message-ID: References: <20190413020111.23400-1-paul.walmsley@sifive.com> <7hmukmew5j.fsf@baylibre.com> <883f3d5f-9b04-1435-30d3-2b48ab7eb76d@wdc.com> <7h5zr9dcsi.fsf@baylibre.com> <7htvetbupi.fsf@baylibre.com> <7hsgtwlm5t.fsf@baylibre.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <7hsgtwlm5t.fsf@baylibre.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-riscv" Errors-To: linux-riscv-bounces+glpr-linux-riscv=m.gmane.org@lists.infradead.org To: Kevin Hilman Cc: "gregkh@linuxfoundation.org" , "linux-kernel@vger.kernel.org" , Atish Patra , "linux-serial@vger.kernel.org" , Paul Walmsley , "linux-riscv@lists.infradead.org" List-Id: linux-serial@vger.kernel.org On Thu, 2 May 2019, Kevin Hilman wrote: > Paul Walmsley writes: > > > I'd recommend testing the DT patches with BBL and the open-source FSBL. > > That's the traditional way of booting RISC-V Linux systems. > > OK, but as you know, not the tradiaional way of booting most other linux > systems. ;) > > I'm working on getting RISC-V supported in kernelCI in a fully-automated > way, and I don't currently have the time to add add support for BBL+FSBL > to kernelCI automation tooling, so having u-boot support is the best way > to get support in kernelCI, IMO. That's great. Please keep hacking away on RISC-V support for kernelCI. My point is just that the U-boot and OpenSBI software stack you're working with is not going to be useful for automatic tests of some kernel patches yet. That stack is still very new, and was written around a non-upstream set of DT data. We are in the process of posting and merging patches to fix that, but it's going to take a few releases of both the kernel and those other boot stack components until things are sorted out in a more durable way. - Paul From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,T_DKIMWL_WL_HIGH autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B0F76C43219 for ; Fri, 3 May 2019 19:05:19 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 80DC92075C for ; Fri, 3 May 2019 19:05:19 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="eX60nTzk"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=sifive.com header.i=@sifive.com header.b="YyLoqA+M" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 80DC92075C Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=sifive.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-riscv-bounces+infradead-linux-riscv=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:Message-ID: In-Reply-To:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=QSWNoWT17Vo8kgk+0LOCwn5Eq7JDBgp1s2zP/+huj8c=; b=eX60nTzkNqm2UI cAPnM/j2sL+Xjwzq6o5MnZEs1mP6FOMr4xzVMBmdI6T3Peuxr9R82psauy+ZnJ/GFZ5DVIoGICsen RCyrJV3n9k5WnSc+4mfvV/Et+XjtWDPPj0PfQOPJu6a8izHU/2ZdLhCKwmoS637MQPKT4uL+jL1/K VH3tY22YANpEv7WziKC5Ac2aRuAcx7CZShIVuebme/X50Dqk3REvGJ+Q6FaViwW339u7m1/dYHLAF O6dQZ81BIOn8rr2oUxgUcqjX4oMwomEIY/3fODNgjKONKBSZLJKg7zEnXDu8xSUlria1nijyjOsEb w9zd3qgz7GBU/GKDI2UA==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1hMdUh-0004Pm-Ps; Fri, 03 May 2019 19:05:15 +0000 Received: from mail-it1-x144.google.com ([2607:f8b0:4864:20::144]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1hMdUe-0004Op-Fa for linux-riscv@lists.infradead.org; Fri, 03 May 2019 19:05:13 +0000 Received: by mail-it1-x144.google.com with SMTP id i131so10871458itf.5 for ; Fri, 03 May 2019 12:05:12 -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=WUEvVuMZ7YPl2dVmcnur9vXgWXYbDp4Kv2NYf/KfC/E=; b=YyLoqA+MOSgu5Z/mdOZYresCbnsrP9MOECqAR4bgemiqd1NPH4z1kTNshqMr1wGxrO 1ulkumKpTQ6uWLtA2Ene+eq+HrTs1KZoMqs9xg+p39iicmy0zTCL7uVABR+WOuDZA063 +oNPgr10wY9fURWnsMIn4Glzq/w4seTiQt6nzHUkagCRCpv7txThNbb5poKXXUtiaq0C amJC+5CNfkSN3LxFTXn27zjZN09O67v/k/iPmRYOidALpODycYOWZxGJ1kWkYY3q8zeE jHByq6IVQuw2xmMN/9K1zm6po5Ybx+hPTG4ELBhJgSBqEWzHWP+zmvqJygso2YzaXz1P hhwg== 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=WUEvVuMZ7YPl2dVmcnur9vXgWXYbDp4Kv2NYf/KfC/E=; b=A8nwxxpSNQwiZcDueadBwznEpIswYJPDj1FL+OTvbDTYaIx0X8Ft+fxvfmzh6agZfe rep+odCfPStSCUhuJhnX6FpBVPF2RsWQTY2L9ond8MFYfTwO2Hl3URn6VfDHto00GfAr mr/k+M83ahkMS0II6WImyM4jtyaZ1JxQkjnlWcNzNjPb8F62vBzqkBz00sgzYDm+jAKx Y1bRRsFZoCZ/y0V3abSlTy3lXN7wq/Nd+r22Deg+KvZThHSUU2K03L4sUI5b1Yk5v+jY 5fNeS9mr13USv/wZ60RfnnVnPJhkqJjX+i46ZWFRsXjx8/YATzp2Djwr8Ss8SA5SA3bh CNUQ== X-Gm-Message-State: APjAAAUxAt03mq7CxDDHZ43mLuxctrqSiHmTrYSpcNizdD6QdQQSvZOs WsKcHb4FvKuhJRPoiC6blNd8Vw== X-Google-Smtp-Source: APXvYqzFS3nViSd8Ml55qWBQUACdB1pGNmsO/5+y7g1p6Gt2X232FHXVSyZ7sg92TLGrQz/n1IlHPQ== X-Received: by 2002:a02:1146:: with SMTP id 67mr8522400jaf.10.1556910311443; Fri, 03 May 2019 12:05:11 -0700 (PDT) Received: from localhost (74-95-18-198-Albuquerque.hfc.comcastbusiness.net. [74.95.18.198]) by smtp.gmail.com with ESMTPSA id d193sm1154451iog.34.2019.05.03.12.05.10 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 03 May 2019 12:05:10 -0700 (PDT) Date: Fri, 3 May 2019 12:05:09 -0700 (PDT) From: Paul Walmsley X-X-Sender: paulw@viisi.sifive.com To: Kevin Hilman Subject: Re: [PATCH v5 0/2] tty: serial: add DT bindings and serial driver for the SiFive FU540 UART In-Reply-To: <7hsgtwlm5t.fsf@baylibre.com> Message-ID: References: <20190413020111.23400-1-paul.walmsley@sifive.com> <7hmukmew5j.fsf@baylibre.com> <883f3d5f-9b04-1435-30d3-2b48ab7eb76d@wdc.com> <7h5zr9dcsi.fsf@baylibre.com> <7htvetbupi.fsf@baylibre.com> <7hsgtwlm5t.fsf@baylibre.com> User-Agent: Alpine 2.21.9999 (DEB 301 2018-08-15) MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190503_120512_720760_8B6BBBF3 X-CRM114-Status: GOOD ( 12.64 ) X-BeenThere: linux-riscv@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "gregkh@linuxfoundation.org" , "linux-kernel@vger.kernel.org" , Atish Patra , "linux-serial@vger.kernel.org" , Paul Walmsley , "linux-riscv@lists.infradead.org" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-riscv" Errors-To: linux-riscv-bounces+infradead-linux-riscv=archiver.kernel.org@lists.infradead.org On Thu, 2 May 2019, Kevin Hilman wrote: > Paul Walmsley writes: > > > I'd recommend testing the DT patches with BBL and the open-source FSBL. > > That's the traditional way of booting RISC-V Linux systems. > > OK, but as you know, not the tradiaional way of booting most other linux > systems. ;) > > I'm working on getting RISC-V supported in kernelCI in a fully-automated > way, and I don't currently have the time to add add support for BBL+FSBL > to kernelCI automation tooling, so having u-boot support is the best way > to get support in kernelCI, IMO. That's great. Please keep hacking away on RISC-V support for kernelCI. My point is just that the U-boot and OpenSBI software stack you're working with is not going to be useful for automatic tests of some kernel patches yet. That stack is still very new, and was written around a non-upstream set of DT data. We are in the process of posting and merging patches to fix that, but it's going to take a few releases of both the kernel and those other boot stack components until things are sorted out in a more durable way. - Paul _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv