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=-2.4 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no 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 45DB9C11D00 for ; Fri, 21 Feb 2020 00:11:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 19674222C4 for ; Fri, 21 Feb 2020 00:11:16 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=broadcom.com header.i=@broadcom.com header.b="OR4qbGMZ" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729446AbgBUALP (ORCPT ); Thu, 20 Feb 2020 19:11:15 -0500 Received: from mail-wr1-f66.google.com ([209.85.221.66]:44177 "EHLO mail-wr1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729373AbgBUALP (ORCPT ); Thu, 20 Feb 2020 19:11:15 -0500 Received: by mail-wr1-f66.google.com with SMTP id m16so26893wrx.11 for ; Thu, 20 Feb 2020 16:11:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=wXSbqjr+PXHQhEGWLVIbHnU0mAYhDxXp177C2dXLvkw=; b=OR4qbGMZ3kSLXHwlfMWDnVjvxT0c/b5fmtDsqdt6bhn6yadSOJmNHGjqCWZm2yVRAO ed/pScZ8+lYgnYH+P/9lFgMRmFo+EmDPQWLLyTUT3CJO+a8D2eeHF7rdlZaG1BnbIa9D tNOFC7Kt+sV47VYFwmPjmlJ/tZzxGLf0wgzqQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=wXSbqjr+PXHQhEGWLVIbHnU0mAYhDxXp177C2dXLvkw=; b=Uh5r56dZy1P4yhO2IWhypGRyTXEfB5rvoMUyft0YFgkwqzaAvoJSCDHIodRpVh22fW Wld+a0wOqccID4nS2pFWpv3ve7nGW5t5Cps6cB/zH5AZwdzlAGuNQPWqKr4k6A/It566 KBOl5Xv0WiTDkkbSthfZSsO5NomuvvsfKAcf3vSh5+sYIhOP4MMA+rxTRrVg5jB5zRyL +aV51Nule9DlQtxCeq843j0MOSQ2HjIRUElCkRJ6hqXJJQhiDUD7qZ8WgYh865T5d7ho 0O/WoAizhiz5z7sbDVVLAz2ZZBxzTRdA1EW/qUHlPmBNMTnu6LcdUFuDVMN/U5ByG7mz IHKA== X-Gm-Message-State: APjAAAUVnUrdemu4nFB8f+VXao97JgcLgoA+l3bZd0VimOtO8+UhhN/7 jQFFjR+uzXSAybOwnQowuEnvmQ== X-Google-Smtp-Source: APXvYqyZNpXUITw974Gj1d7jmXjJf2j4kz6bDP4xvQnH/etFM/nRGojeEXJirHn2sJxv9V2yWs/+Pw== X-Received: by 2002:a5d:510f:: with SMTP id s15mr44375580wrt.408.1582243873022; Thu, 20 Feb 2020 16:11:13 -0800 (PST) Received: from [10.136.13.65] ([192.19.228.250]) by smtp.gmail.com with ESMTPSA id q9sm1553085wrx.18.2020.02.20.16.11.08 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 20 Feb 2020 16:11:12 -0800 (PST) Subject: Re: [PATCH 2/7] firmware: add offset to request_firmware_into_buf To: Luis Chamberlain , Takashi Iwai Cc: Greg Kroah-Hartman , David Brown , Alexander Viro , Shuah Khan , bjorn.andersson@linaro.org, Shuah Khan , Arnd Bergmann , "Rafael J . Wysocki" , linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-fsdevel@vger.kernel.org, BCM Kernel Feedback , Olof Johansson , Andrew Morton , Dan Carpenter , Colin Ian King , Kees Cook , linux-kselftest@vger.kernel.org References: <20190822192451.5983-1-scott.branden@broadcom.com> <20190822192451.5983-3-scott.branden@broadcom.com> <10461fcf-9eca-32b6-0f9d-23c63b3f3442@broadcom.com> <93b8285a-e5eb-d4a4-545d-426bbbeb8008@broadcom.com> <20191011133120.GP16384@42.do-not-panic.com> From: Scott Branden Message-ID: Date: Thu, 20 Feb 2020 16:11:06 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <20191011133120.GP16384@42.do-not-panic.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: linux-arm-msm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org Archived-At: List-Archive: List-Post: On 2019-10-11 6:31 a.m., Luis Chamberlain wrote: > On Tue, Aug 27, 2019 at 12:40:02PM +0200, Takashi Iwai wrote: >> On Mon, 26 Aug 2019 19:24:22 +0200, >> Scott Branden wrote: >>> I will admit I am not familiar with every subtlety of PCI >>> accesses. Any comments to the Valkyrie driver in this patch series are >>> appreciated. >>> But not all drivers need to work on all architectures. I can add a >>> depends on x86 64bit architectures to the driver to limit it to such. >> But it's an individual board on PCIe, and should work no matter which >> architecture is? Or is this really exclusive to x86? > Poke Scott. > > Luis Yes, this is exclusive to x86. In particular, 64-bit x86 server class machines with PCIe gen3 support. There is no reason for these PCIe boards to run in other lower end machines or architectures.