From owner-freebsd-drivers@freebsd.org Tue Oct 23 08:23:32 2018 Return-Path: Delivered-To: freebsd-drivers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F73310708A4 for ; Tue, 23 Oct 2018 08:23:32 +0000 (UTC) (envelope-from Shreyank.Amartya@amd.com) Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0041.outbound.protection.outlook.com [104.47.36.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "GlobalSign Organization Validation CA - SHA256 - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B6072701D8 for ; Tue, 23 Oct 2018 08:23:31 +0000 (UTC) (envelope-from Shreyank.Amartya@amd.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amdcloud.onmicrosoft.com; s=selector1-amd-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=BpLc/FLJmtQMLlQWCzDC5i7vFf75kRif/sO/5FoXX6c=; b=mVBJgnHql0jNKKToSimH09cCR0CttsqJKse5JFCXjnSGYusAeXzM5Ge91jp6mkW+drnWo3H2u1QXfDcIds8qOY7gl2y17K25r0M9bAf32eD2QznfIfW0v9M6g/M1GCdPOcW4Nwnwe2gyJ6njrLIl5laOposGdPFl5D3OUiHIVKQ= Received: from SN6PR12MB2813.namprd12.prod.outlook.com (52.135.100.27) by SN6PR12MB2832.namprd12.prod.outlook.com (20.177.251.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1273.18; Tue, 23 Oct 2018 08:23:27 +0000 Received: from SN6PR12MB2813.namprd12.prod.outlook.com ([fe80::f43e:fb06:f5cb:86b6]) by SN6PR12MB2813.namprd12.prod.outlook.com ([fe80::f43e:fb06:f5cb:86b6%6]) with mapi id 15.20.1250.028; Tue, 23 Oct 2018 08:23:27 +0000 From: "Amartya, Shreyank" To: "freebsd-drivers@freebsd.org" Subject: eMMC AMD platform Thread-Topic: eMMC AMD platform Thread-Index: AdRqp/Txi+uhfRAQRZex7esIDeBosg== Date: Tue, 23 Oct 2018 08:23:27 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=Shreyank.Amartya@amd.com; x-originating-ip: [202.56.249.162] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; SN6PR12MB2832; 20:9eXlwvyT9vQ/XmAkps4HEwPTy2ZnITIhS4+86mB9bJBOx6KOkcLJUkBJ6Ahshzm3JDEvLwP5w9kX6MfOM4AhnlM6+ylIQBdAFqNYuyxqozJH14w6KGnnHBMlZ4k/4p08+lzhwZq0r42S1UT3vXOd0HPyHarjVj0U78ScOuCJ28W5Qj9tIUaFunCtLlPRwxsSVT2lN5OFWZVf0jqx/1EdcaTiUHA++iYNteqErpl/CRxxqrLDclhAfuOYcaZl93T4 x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-correlation-id: 80c1fdf1-85aa-453f-806a-08d638c0cef6 x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(5600074)(711020)(4618075)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(7193020); SRVR:SN6PR12MB2832; x-ms-traffictypediagnostic: SN6PR12MB2832: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(21748063052155)(28532068793085)(190501279198761)(227612066756510); x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3002001)(3231355)(944501410)(52105095)(6055026)(148016)(149066)(150057)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123562045)(20161123564045)(20161123560045)(201708071742011)(7699051)(76991095); SRVR:SN6PR12MB2832; BCL:0; PCL:0; RULEID:; SRVR:SN6PR12MB2832; x-forefront-prvs: 0834BAF534 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(366004)(39860400002)(136003)(396003)(346002)(189003)(199004)(476003)(14444005)(9326002)(68736007)(7736002)(81166006)(256004)(8676002)(81156014)(8936002)(3480700004)(102836004)(2900100001)(7696005)(186003)(71200400001)(71190400001)(486006)(6436002)(236005)(54896002)(53936002)(6306002)(9686003)(55016002)(74316002)(6916009)(316002)(5630700001)(7116003)(26005)(5640700003)(5660300001)(2351001)(2906002)(97736004)(106356001)(33656002)(105586002)(86362001)(790700001)(6116002)(3846002)(66066001)(14454004)(606006)(99286004)(5250100002)(25786009)(478600001)(72206003)(966005)(2501003)(6506007); DIR:OUT; SFP:1101; SCL:1; SRVR:SN6PR12MB2832; H:SN6PR12MB2813.namprd12.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: amd.com does not designate permitted sender hosts) x-microsoft-antispam-message-info: 4J5/PAaxHTdkeNUJ1divsENI8TgFG2H1UglxlGWo88LGy/jEY68QtEwHj201DpgfkaYYeTsleCcr1AgILHBBHuJSqYTgKdJGW2b11OPFTjdf9roYebE1YielumnvkNGa/ixHNeBuQOZQ6Y1yyhgPipbdqBCeIK3PbVPtTuxMB3iZHIBpaRvfMEJdL9mvbZOg4yx5SKByPrIbBYV8Rzvxr4yQTcT/1rupl85c+IxY3Zldb9TI9LfqUQvc0WQUrQOY/DzO5Q6cf8NBfs1Y54zqatmxNsSAUeBPcysX6rytDebjQ1hfk6uYVj0NgbmIB9nwHL5ZHxbY/Ljmk+JX91VMKsyVMEsSlbUyXzrt1nwbC9Q= spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: amd.com X-MS-Exchange-CrossTenant-Network-Message-Id: 80c1fdf1-85aa-453f-806a-08d638c0cef6 X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Oct 2018 08:23:27.5320 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 3dd8961f-e488-4e60-8e11-a82d994e183d X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR12MB2832 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Oct 2018 08:23:32 -0000 Hi, I have an AMD eMMC 5.0 controller connected to an eMMC device. I recently got around to enabling HS400 mode but the performance is still s= ame what I was getting in HS200 mode. Is there a way to verify the HS400 mode is active? Patch for enabling HS400: https://reviews.freebsd.org/D17644 In order to enable the HS400 mode I had to clear the Sampling clock select = bit (Host control 2 register) and then set it later (as part of the patch). Now, I suspect that this led to reset of the tuning circuit and that even t= hough HS400 mode is enabled, since it is not tuned, I do not see increase i= n performance. Could that be a possibility? There is a similar patch for linux and I've tried it, it works on my board = with HS400 mode (~200 MB/s), measured using iozone. Linux patch: https://patchwork.kernel.org/patch/10086747/ Thanks Shreyank Amartya From owner-freebsd-drivers@freebsd.org Wed Oct 24 13:42:23 2018 Return-Path: Delivered-To: freebsd-drivers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E7882FD9AD1; Wed, 24 Oct 2018 13:42:22 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6B0108EBB0; Wed, 24 Oct 2018 13:42:22 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: by mail-wm1-x332.google.com with SMTP id y144-v6so5439255wmd.4; Wed, 24 Oct 2018 06:42:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=FmuqzWnIzVv/GkgUrKokOkwlmAIzkEMw7rzkWhzSit4=; b=eawrv0EvyT3T5hVrDsP724sQVc5cujw80a7bg4eBuQhrPwqTMt9mfZjJg7Huseon59 pzhQrSQ4AFbe9SEIOJn8bIsZXNd40XfyaqtfYKhsefTULUTwYZb9WX1F9VCRI9920r7M 0voZ5xLNdHk/IUatNBTH+bV7FtJfeqERe26SniodweEfvPG6z+vQk3gRXPsobE5GLo25 RuDB99omQhci3Gje6YBzM56kYUAQPwQF8SvTRbJMsJ3igWpr7wFo5Y93gcVnOOn02TF4 063Rgw/ZO2YPUazCFdPk2FoPWCKl6u/qJznnM3hCvSggfCZzSuMktB3YohnLVY/4pCHM vjzA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=FmuqzWnIzVv/GkgUrKokOkwlmAIzkEMw7rzkWhzSit4=; b=srKHyrYvl13zyl8s22gueQ+fF/REpMe/e0e+RMNrbJIZOfVmbNFaTa2QkEnyrW4FyU fTCGcloQgSg69HGSu8u8OJXGuBvO9zTG1YvSYKqyDS0mXZJAbnEOhIY+ZLBnfHjIVVWy hUebgFogFuAgfv2MvsrS3irJl0wuLRb5PhpIfpUu0VkBCQ4ZKE2wzTTSjmNAblSOIgRv adfH8Yej9s8MkkW/doyUA/VZ6MiXlLTESIOed95Q7januSyxU/ioGfYJr+EEnF0hukqM OXU3EQoEKz35SOAPkJ5Bb5xSJdy2FA4wy2eRTib8oGA1YcGCMQi5fraXFUM0OAh5P1DP EBGg== X-Gm-Message-State: AGRZ1gKWiJJNLXKmUvY6kMLvwsFGRdaEdwBHwiXLkt0VaGWHPMoCfpy+ NYLxN7JOjoFi3xll4lZhE/wkLPBVMO6BZ3Z3Y3d44oCN X-Google-Smtp-Source: AJdET5fnHDOcz2X2ovKE3zuhiDk4mEVEwvmbeSlwz5IXAa28ZjuFVQ5varsYexn4QZlcN2mEoff95TsbsMQuK0VMqKs= X-Received: by 2002:a1c:540d:: with SMTP id i13-v6mr2145358wmb.149.1540377663172; Wed, 24 Oct 2018 03:41:03 -0700 (PDT) MIME-Version: 1.0 From: Rajesh Kumar Date: Wed, 24 Oct 2018 16:10:51 +0530 Message-ID: Subject: Has anything changed from 11.2 to 12.0 in PCI MSI/MSIX path? To: freebsd-drivers@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Oct 2018 13:42:23 -0000 Hi, I have a amd64 based board. When I tried to boot 11.1 (or) 11.2 in that, I needed the following tunables to be set from loader prompt to get it booted (otherwise machine reboots continuously). hw.usb.xhci.msi=0 hw.usb.xhci.msix=0 hw.pci.enable_msi=0 hw.pci.enable_msix=0 But, when I tried with 12.0 - ALPHA4, I could able to get it booted without any tunables. So, has anything changed significantly on PCI MSI/MSI-X path? Note: I have a forum topic with my observations about the issue on 11.1/11.2 in the following thread https://forums.freebsd.org/threads/freebsd-11-1-installation-fails-and-rebooting.65814/ Let me know if you need any details. From owner-freebsd-drivers@freebsd.org Wed Oct 24 19:47:13 2018 Return-Path: Delivered-To: freebsd-drivers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 91E281037FBE; Wed, 24 Oct 2018 19:47:13 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46F14770FD; Wed, 24 Oct 2018 19:47:13 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from John-Baldwins-MacBook-Pro-2.local (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id E84B710A87D; Wed, 24 Oct 2018 15:47:11 -0400 (EDT) Subject: Re: Has anything changed from 11.2 to 12.0 in PCI MSI/MSIX path? To: Rajesh Kumar , freebsd-drivers@freebsd.org, freebsd-current@freebsd.org References: From: John Baldwin Message-ID: <2a595c73-4a93-6e3f-f93d-9038baeeb18a@FreeBSD.org> Date: Wed, 24 Oct 2018 12:47:11 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Wed, 24 Oct 2018 15:47:12 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Oct 2018 19:47:13 -0000 On 10/24/18 3:40 AM, Rajesh Kumar wrote: > Hi, > > I have a amd64 based board. When I tried to boot 11.1 (or) 11.2 in that, I > needed the following tunables to be set from loader prompt to get it booted > (otherwise machine reboots continuously). > > hw.usb.xhci.msi=0 > hw.usb.xhci.msix=0 > hw.pci.enable_msi=0 > hw.pci.enable_msix=0 > > But, when I tried with 12.0 - ALPHA4, I could able to get it booted without > any tunables. So, has anything changed significantly on PCI MSI/MSI-X > path? > > Note: I have a forum topic with my observations about the issue on > 11.1/11.2 in the following thread > https://forums.freebsd.org/threads/freebsd-11-1-installation-fails-and-rebooting.65814/ > > Let me know if you need any details. I believe this was fixed by r338360. -- John Baldwin From owner-freebsd-drivers@freebsd.org Thu Oct 25 17:25:00 2018 Return-Path: Delivered-To: freebsd-drivers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2D5461086DCB; Thu, 25 Oct 2018 17:25:00 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 87A9969EFB; Thu, 25 Oct 2018 17:24:59 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: by mail-wr1-x432.google.com with SMTP id l6-v6so10175877wrt.1; Thu, 25 Oct 2018 10:24:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6Wrubset3IpjY2z6yCwGo8u43H9U/nYor2Ikd3Svu0Y=; b=N6AWct3bLNX4HjK7pHH2R0QByC0hSqdJfmVFq0Ota7C3Q0OqJL8UHLngizZFs/tbFT OfYL2/ka3gqTRiRX8HXrSN5RV7WzhlLq2VmLh9FijbCXRoh7RMkj7PcMHO/LSV5Z3cvn TssPvncuZaph8keM1OwvLTt71pjxVXwmiTzG93A+BngmYOf8YOrH0XAtz36K24zTpav0 ApJ5HG4TYVttIBKQg7YfLmTuVlRcf04I7+acvys3UP4RmDyGvKa4Tem167Lp1+InyylX Ba3D9bVfP4ANK98VRP/xoYuOhBzj8Swk4Ey5nmN8LvhhB6tmLW38WYieDj315SpCZvmE zmog== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6Wrubset3IpjY2z6yCwGo8u43H9U/nYor2Ikd3Svu0Y=; b=Qg0XSVcFctBLiSHCSS6DiGaiMtwsLxhjPMsopk9Cw7LJ3B6CB4XT8wUw8xKjPe5DAk nrwy7JeXXpk+UyE/Kl2fxiGxVMoqfNsPNNg0JVDkXtb6BS9ybXBvMLwWbhVAN4ci0/+w i8aBocj7552cJP8jG4PHSsxxBgIAgEc1Sum3nbyGQ3RZkSDdTtFXkBvZVmW48zxD5+lB /Z8dJVTrDCd6P82j5wP6KdIYa8nwDKEB9JyadHOWrb0Z+5CvPKDNtDyjOLkFrihkgltE e17wk+F9wV4bT/ONwEcUyinBbOtv28mTIgI4ibyzEwFYbu/z6DXRvNQbzdVP0oAEOKh7 sXmA== X-Gm-Message-State: AGRZ1gKBawOCvco+aYxYMMdLs+/iaRGDmTP7u7CU7bKQ3cQtVeV3+YvT I7SQXfn8H5B1mN5YS4DTgk+QJph6AA3YXrx6biD/Ow== X-Google-Smtp-Source: AJdET5c8Nmd7jiN0sb34IRNDQjXX672F5wdQsqzdcl++QvUPK/lDRr41R1Evzg9IB8/s4qUWLvgza1QxjoS4mewLd/o= X-Received: by 2002:adf:a144:: with SMTP id r4-v6mr2769259wrr.169.1540488298171; Thu, 25 Oct 2018 10:24:58 -0700 (PDT) MIME-Version: 1.0 References: <2a595c73-4a93-6e3f-f93d-9038baeeb18a@FreeBSD.org> In-Reply-To: <2a595c73-4a93-6e3f-f93d-9038baeeb18a@FreeBSD.org> From: Rajesh Kumar Date: Thu, 25 Oct 2018 22:54:45 +0530 Message-ID: Subject: Re: Has anything changed from 11.2 to 12.0 in PCI MSI/MSIX path? To: jhb@freebsd.org Cc: freebsd-drivers@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Oct 2018 17:25:00 -0000 Hi John, Thanks a lot. It helps. I backported the changes to 11.2 and tried booting in my board with success without any need for the said tunables. I see those changes are marked for MFC after 2 Weeks. But I don't see them still in stable/11 branch. So, will it be taken into stable/11 branch by any chance? If not, can the backported changes be submitted for review to take into stable/11 branch? On Thu, Oct 25, 2018 at 1:17 AM John Baldwin wrote: > On 10/24/18 3:40 AM, Rajesh Kumar wrote: > > Hi, > > > > I have a amd64 based board. When I tried to boot 11.1 (or) 11.2 in that, > I > > needed the following tunables to be set from loader prompt to get it > booted > > (otherwise machine reboots continuously). > > > > hw.usb.xhci.msi=0 > > hw.usb.xhci.msix=0 > > hw.pci.enable_msi=0 > > hw.pci.enable_msix=0 > > > > But, when I tried with 12.0 - ALPHA4, I could able to get it booted > without > > any tunables. So, has anything changed significantly on PCI MSI/MSI-X > > path? > > > > Note: I have a forum topic with my observations about the issue on > > 11.1/11.2 in the following thread > > > https://forums.freebsd.org/threads/freebsd-11-1-installation-fails-and-rebooting.65814/ > > > > Let me know if you need any details. > > I believe this was fixed by r338360. > > -- > John Baldwin >