Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp981315ybb; Wed, 25 Mar 2020 13:16:46 -0700 (PDT) X-Google-Smtp-Source: ADFU+vvxGygDYSkiouRNERf/9E08r9ef1UHsfpiLyCLOXrrKPiaSVVhip8DcoXuYaIz/jnQaTJ/O X-Received: by 2002:aca:5109:: with SMTP id f9mr3667741oib.14.1585167406832; Wed, 25 Mar 2020 13:16:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1585167406; cv=none; d=google.com; s=arc-20160816; b=QLCn6fTIuQw5lyWaT5tPlYvr4xLmulwhgF56S2MVDsI7P1dFJQ6clT9MF3QHEXeNFB oUxGtTI6gbH6NLp4xlOerhWB4aXYEJP6FRQEILsPUO3JBT9eky2meV6PI05H870ImyYl OKCNkUTt/rus3S5nFifY+CFsbBpl003wGenq8UOQbnOSQMQDWV8Hd6UH/FK1kNISJf2f Y1NMssDd3TBQFjWNsm2XwLcygCBIvYAR4eYm220oOqJZpM2UZFD2CXIDknVoVlDYe3cY swGtKUc0bi3UIVoCrDwj92HYNCQvU4iwG1ebPA1auxkS7pLxq0U0GCfxAHGnn/iFsLcH 0Tag== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=P4Ii0TDkwdlQFHK60zjqPMZ23Hc82ZULQPDzrcrxaC8=; b=dqbnMoJ87waHHQJWfBVKJnU0+Z4mwtLrm/3IsMEEQVABPjiikpLoQhKMFcDIT24RTt 4s+ia/tRucowYlObj4a74k0OoL2upeUGtppeTWZWhtKZVmWEgeb7afBhzAgoT6rJz41B 0FWoNBOZnEx6WkUQ+tho2dcW28UjyAmqM6eJZsDMKt34sQW8o7aV6yipsXvn3/rq4W5o P63uf5e/UWUowFXWngXzJdzZJ/1DWTKkJbbScQ5813Ek8z7PKclYTVgLGXXysGvKfKUM u3LVdN7flQnhb1t9EMWkWa0J9M40DA4CDHXbw2OfNsdYC6DnKyxB5LvZCAXsEaKcgFJK oYig== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=oZy686pV; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x66si62606ota.244.2020.03.25.13.16.32; Wed, 25 Mar 2020 13:16:46 -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=@gmail.com header.s=20161025 header.b=oZy686pV; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727556AbgCYUQE (ORCPT + 99 others); Wed, 25 Mar 2020 16:16:04 -0400 Received: from mail-wm1-f68.google.com ([209.85.128.68]:33530 "EHLO mail-wm1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727328AbgCYUQD (ORCPT ); Wed, 25 Mar 2020 16:16:03 -0400 Received: by mail-wm1-f68.google.com with SMTP id w25so2986278wmi.0; Wed, 25 Mar 2020 13:15:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=P4Ii0TDkwdlQFHK60zjqPMZ23Hc82ZULQPDzrcrxaC8=; b=oZy686pVHSQV8lyVpekxmI1+huiDJ7QLLElLaZDKRDcctT+pOt1/2Y2xwrDxKsGeos 4SvsW8E/PLHAAzEea+YC8yH9ZfJ/HbxW1kU7H+O1uOetbk26GI2KPBymqpyofWh6gW/a D+TauRu6IgwANmhZQZtqfWgiQflfbwLyp8Z1avVEouhlzJy1BFyCeWOAGjrLzSXArW5V c2id3KUepfnpOVku/SYZCFlMelGDLBcxBAeRJ/S3N2bvSGVnXmQZTT49x3fCt29Cxid9 Ml8rLTeJuBfPSUR1VLAwSF6G/Z/LEjLH+dQthMTLQwwx2yefXw90ZhQToBeBp8mT8llW x02Q== 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:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=P4Ii0TDkwdlQFHK60zjqPMZ23Hc82ZULQPDzrcrxaC8=; b=J1XTS0eEu9ga4fvIzOr/xYFr9lkv5tuPs+GKmVDYfvG5LaA4dEffPkbs/iPLzV5b6J Vi60en/WBW1GdxKRlDhdTybTwH8ErU6JDJcJtdQCj5ekQlDVqYTnxcDroTPKxZYmS1I5 G1n0DrDXXXIRo4E8BuZ1XdhpwxGZvqL3+hv5jOPkHjhne49kUR/UPkdG7JOdzPPRcKcd VpR1vOsv6GiiVLzLg0B/gVlRNmJ1vRxzvaS9Vf6fAYcQnRxgnAEtAYsC3Q9fCA6mAajH PQynquZ1BnGd1DL3VaFstHyLKMcf9LJbffntOdWqlnq5/4G6V1LfQuOKyhzq6lU0OdDX pYxQ== X-Gm-Message-State: ANhLgQ09O/xLe6EZJWfmiQSghSKJBZqPVjzgI+uttlizMLv55K3hV3vv +2N/fVzUBrXAlyY2SW5nz/lLMqi6 X-Received: by 2002:a1c:4d7:: with SMTP id 206mr5008380wme.5.1585167358877; Wed, 25 Mar 2020 13:15:58 -0700 (PDT) Received: from localhost (p200300E41F4A9B0076D02BFFFE273F51.dip0.t-ipconnect.de. [2003:e4:1f4a:9b00:76d0:2bff:fe27:3f51]) by smtp.gmail.com with ESMTPSA id y7sm142535wrq.54.2020.03.25.13.15.57 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 25 Mar 2020 13:15:57 -0700 (PDT) Date: Wed, 25 Mar 2020 21:15:56 +0100 From: Thierry Reding To: LABBE Corentin Cc: Jon Hunter , Nicolas Chauvet , Prashant Gaikwad , pdeschrijver@nvidia.com, Michael Turquette , sboyd@kernel.org, axboe@kernel.dk, linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org, linux-ide@vger.kernel.org Subject: Re: tegra124-jetson-tk1: sata doesnt work since 5.2 Message-ID: <20200325201125.GA832965@ulmo> References: <20200319074401.GA4116@Red> <20200325134003.GA27961@Red> <20200325142306.GB27961@Red> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="A6N2fC+uXW/VQSAv" Content-Disposition: inline In-Reply-To: <20200325142306.GB27961@Red> User-Agent: Mutt/1.13.1 (2019-12-14) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --A6N2fC+uXW/VQSAv Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 25, 2020 at 03:23:06PM +0100, LABBE Corentin wrote: > On Wed, Mar 25, 2020 at 02:00:25PM +0000, Jon Hunter wrote: > >=20 > > On 25/03/2020 13:40, LABBE Corentin wrote: > > > On Thu, Mar 19, 2020 at 08:55:38AM +0100, Nicolas Chauvet wrote: > > >> Le jeu. 19 mars 2020 =C3=A0 08:44, LABBE Corentin a =C3=A9crit : > > >>> > > >>> Hello > > >>> > > >>> sata doesnt work on tegra124-jetson-tk1 on next and master and at l= east since 5.2 (but 5.1 works). > > >>> [ 0.492810] +5V_SATA: supplied by +5V_SYS > > >>> [ 0.493230] +12V_SATA: supplied by +VDD_MUX > > >>> [ 2.088675] tegra-ahci 70027000.sata: 70027000.sata supply ahci = not found, using dummy regulator > > >>> [ 2.097643] tegra-ahci 70027000.sata: 70027000.sata supply phy n= ot found, using dummy regulator > > >>> [ 3.314776] tegra-ahci 70027000.sata: 70027000.sata supply ahci = not found, using dummy regulator > > >>> [ 3.323658] tegra-ahci 70027000.sata: 70027000.sata supply phy n= ot found, using dummy regulator > > >>> [ 5.236964] tegra-ahci 70027000.sata: 70027000.sata supply ahci = not found, using dummy regulator > > >>> [ 5.245867] tegra-ahci 70027000.sata: 70027000.sata supply phy n= ot found, using dummy regulator > > >>> [ 5.254706] tegra-ahci 70027000.sata: 70027000.sata supply targe= t not found, using dummy regulator > > >>> [ 5.310270] phy phy-sata.6: phy poweron failed --> -110 > > >>> [ 5.315604] tegra-ahci 70027000.sata: failed to power on AHCI co= ntroller: -110 > > >>> [ 5.323022] tegra-ahci: probe of 70027000.sata failed with error= -110 > > >>> [ 35.694269] +5V_SATA: disabling > > >>> [ 35.697438] +12V_SATA: disabling > > >> > > >> It looks strange, because (on same device) , I have sata working as > > >> appropriate, but ethernet fails with me. > > >> https://bugzilla.kernel.org/show_bug.cgi?id=3D206217 > > >> > > >> It might worth to have another report. > > >> > > >=20 > > > Hello > > >=20 > > > Mine has ethernet works well. But I hit many problem with it and olde= r kernel. > > > Perhaps the 5.1.21, were I am stuck, does not have it. > > >=20 > > > Anyway, the tegra of kerneci has the same SATA problem. > > > https://storage.kernelci.org/next/master/next-20200325/arm/multi_v7_d= efconfig+CONFIG_SMP=3Dn/gcc-8/lab-baylibre/boot-tegra124-jetson-tk1.txt > > >=20 > > > Maintainers, any idea on this sata issue ? > >=20 > > I have checked our bootlogs for v5.6-rc7 and don't see the issue with > > either the tegra_defconfig or the multi_v7_defconfig. I am wondering if > > this could be due a difference in the bootloader version. Currently we > > are testing with a v2019.07 u-boot bootloader. Looks like the kernelci > > board is using an older u-boot. Obviously it should still work, but > > would be good to know if the reason why were are not seeing this is > > because of the bootloader. > >=20 > > Another thing to check would be the pll_e clock frequency on a working > > build and non-working build to see if there is a difference in the pll > > frequency that is causing this. > >=20 > > Cheers > > Jon > >=20 >=20 > Hello >=20 > My uboot is 2016.01-rc4-00002-g3861d78, so a bit old. > I have a mainline uboot build for this tegra, but still didnt find a clea= r way to update it. > Did you have a good documentation on how to update it ? > If possible some clear uboot commands to update it via tftp. Not sure about TFTP, but you can find the standard flashing scripts for various devices here: https://github.com/NVIDIA/tegra-uboot-flasher-scripts Those work by uploading the image via RCM and then running the commands to flash it. I think those scripts will also create the images that they will flash, so you should be able to download that image via TFTP and then flash it using the command that the tool would normally use. Thierry --A6N2fC+uXW/VQSAv Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEiOrDCAFJzPfAjcif3SOs138+s6EFAl57u/wACgkQ3SOs138+ s6GNUhAAkrcqqRMGZtLkT0sMvVkiyOWw3Bj/DAvkCBNjNgmtxBu//ZjPqOsK7B/h 4eZJO8SfPWTHHh3zi76o8xMbKu1KFQZxANZ6vNj71GwM2f7iqrHe/wYlD+vv5Myb hRYw7oSJVcaAhbTIeQCG4SrGFXT7EBpBHsQqRizsj9voCjY4TrWvG+ZTJZ6fqA5t +QtsdOy32rdCIJbLGzHTkzHZg3LDPr6x5KnPhtCUDzoVWJgmBlLjgjPzxcgxzawJ MGqvqEkl9I7TAdIBFoxna3HVOX1jZWS1NhCXSP8fJzxmKwrRIgDWP+QYkUegbmve RjiI8A94VcdOTnfDTyZSfo7m3rXP4gtLQDTP4r2VUjvElByBlwN5rHM8bNEOyZCM FgIVc8kByoK6+leOOfBQWl5aQiQoaUN1pnJHJk/VvC99spAv5Ik692/Tm7wH30SV keDGeh7J7QTdsJ/++Obc7vteJo1jNkh0fZLSSA6wukFAYUK9O/+bDkigVOcBmLNY H9otuH0Y1uGzwb0Jc1aRKDYOO9FDWNpTop2vGXNOz+BMLFBMjes6/EqmCEPgDtZH /4yxLajy71mEl01i8B4cyZSwD796xya9L7cinyVYevxpoxUOmOgb9p/QNG1ziy3C IZgWNp5TzacaL4iBFb/UZ86N8BMuwnWADLI8O+1l1kiONPp9i4A= =8N/K -----END PGP SIGNATURE----- --A6N2fC+uXW/VQSAv--