Received: by 2002:a05:6358:1087:b0:cb:c9d3:cd90 with SMTP id j7csp2492823rwi; Fri, 21 Oct 2022 04:38:38 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4te6SlIj5N1P7rvHgZPnljt0DZe61INtDGDTjeJ9NP0mRSIGe9wl3YAm7rLWLPIJdoVf92 X-Received: by 2002:a63:145d:0:b0:44b:f115:f90f with SMTP id 29-20020a63145d000000b0044bf115f90fmr16117227pgu.157.1666352318184; Fri, 21 Oct 2022 04:38:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1666352318; cv=none; d=google.com; s=arc-20160816; b=B2CWB4M1vhAEWXhkncou+erducpBbLAg9VWG9ZSniAcpK6gf06D6uR4TI32bQf8wfY zF9GwFPIJ/Z0GE9QoAm1opqQwmSH1WEwiKXQklb+ZwIdLTGAueMvhSjTAx8IuJl7GrUz o74GKmsf72FLwTM9Y0wbW2t1dLA4AbcOK4Z1BYx4OFW/++zbTMl6eqEa03EIZkJ/qiPF q5qtyZsjnXkVdT+5WvKOSKBa5BlMNs+sa0SDUz1rfhr9XFYK38BECWmavknrgvBHPj6q xOsVv9dyM+ajryKVGGgveqhoHTkdonX7lEnH4EpDhwwWO1QEeAkeRtEeouzXH38K7Csf 3fQA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=PnVnwFguNNNpUjd+EYnWREJ/4XFTPcPib0PK8AXo4A8=; b=UXWaRSH/fBgeqKZpbRyrfPcbNqNo2OfFE0PWKEN0uMf9AbWYzRGpP/Df4fA/97gq0d KAO4GhlbIkz0F0P9IKTlJ/o9tUR/z0HFmgQe4AE5r+6vaa26qK5Z2+1mRP6GTBuofsjU NOVANaZpc9CjK33KqYahhNytHqE1gIVHH5RlWz0S94hvLuVSWP9YgsPalhlBwhILsk80 aGxjbvdFOnh8KUOSHuqN5Ny4Cnu/huMGXrb5zzZPsR2kRQ3gY+vtQSBlXrCk9STNNSDa uyG/J/yznWO6a9YqE0KSR32LoV0yFIc8FrtysP/ouTm0GDXT0xxwa7TkIc8V+iOuyJY/ FJPg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id c18-20020a170903235200b00176b9906c4dsi30031730plh.153.2022.10.21.04.38.24; Fri, 21 Oct 2022 04:38:38 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229968AbiJULeH (ORCPT + 99 others); Fri, 21 Oct 2022 07:34:07 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34714 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230452AbiJULdm (ORCPT ); Fri, 21 Oct 2022 07:33:42 -0400 Received: from formenos.hmeau.com (helcar.hmeau.com [216.24.177.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A64FC261ADB for ; Fri, 21 Oct 2022 04:33:33 -0700 (PDT) Received: from loth.rohan.me.apana.org.au ([192.168.167.2]) by formenos.hmeau.com with smtp (Exim 4.94.2 #2 (Debian)) id 1olqGj-004djE-M0; Fri, 21 Oct 2022 19:33:31 +0800 Received: by loth.rohan.me.apana.org.au (sSMTP sendmail emulation); Fri, 21 Oct 2022 19:33:30 +0800 Date: Fri, 21 Oct 2022 19:33:30 +0800 From: Herbert Xu To: Peter Harliman Liem Cc: atenart@kernel.org, linux-crypto@vger.kernel.org, linux-lgm-soc@maxlinear.com, pvanleeuwen@rambus.com Subject: Re: [PATCH v2 0/3] crypto: inside-secure: Add Support for MaxLinear Platform Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Tue, Sep 27, 2022 at 11:10:07AM +0800, Peter Harliman Liem wrote: > Hi, > > I have been utilizing inside-secure driver on MaxLinear > SoC platform (which has eip197 hardware inside). > > One issue I found is that I needed to flip the endianness > in eip197_write_firmware() function, which for reason I am > not aware is using big-endian. > The firmware that I have is clearly using little-endian, > and unfortunately I do not have access to Marvell platform > to do more investigation or comparison there. > I have also tried to look for clues in Inside-Secure's > hardware/firmware documentation, without success. > > Thus, assuming each vendor may use different endian format, > on these patch set I add support for little-endian firmware > (default remains big-endian). MaxLinear platform can then > utilize the option, which is implemented as soc data. > > An alternative to this would be implementing the option > as a new device-tree property, but for now I assume we do > not need that since each platform endianness should be > fixed, and will not vary per board/hardware. > > Please help review. > > Thanks! > > v2: > Revert directory change for generic case. > Add missing driver data change in pci_device_id. > Rename data struct to safexcel_priv_data. > Rework endianness selection code casting, to fix warning caught by kernel test robot. > Rename mxl version string to eip197 'c'. > > Peter Harliman Liem (3): > crypto: inside-secure - Expand soc data structure > crypto: inside-secure - Add fw_little_endian option > crypto: inside-secure - Add MaxLinear platform > > drivers/crypto/inside-secure/safexcel.c | 69 ++++++++++++++++++------- > drivers/crypto/inside-secure/safexcel.h | 10 +++- > 2 files changed, 59 insertions(+), 20 deletions(-) > > -- > 2.17.1 All applied. Thanks. -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt