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=-9.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED 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 CB24BC4363D for ; Fri, 2 Oct 2020 10:24:24 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (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 653BD206FA for ; Fri, 2 Oct 2020 10:24:24 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="PflldzG7"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=intel.onmicrosoft.com header.i=@intel.onmicrosoft.com header.b="GlBgUfp9" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 653BD206FA Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:MIME-Version:In-Reply-To:References:Message-ID:Date: Subject:To:From:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=CjA4RHoMJPHrD4ZoEVg1IjU65LLy+5SuGrTGTMVXJXQ=; b=PflldzG7fZm61ZErj8SRn/AL7 tj3EZveB/Gx2X43PBOcNfduo8f7jItH7XeCerSmBxS590fMF/oKTYE3KwnCuMbag+eN9yhDNOu9nQ b1V6St+G8snaW2p21Yy6FUdeLLVIEEdaYTf0XR6USav9aXN6EPIH/e8gGzba5gc7GrvJPz+WidyDV 4rMqljKTb+eAHX0syY9CTuXqkUZhs2Dfxmc75bARq0wDsr8aHwNHfdWMCZbg4HevrWtzEJFIJ32VP Iv0it8KSk/n6IaHC8rS6aQ5W/2ZqjVpqcmqW3GOBbkrpUsZ/FQcHMz/gHPOjvbICRT/Sgmehv7yJq M6aPVXg7w==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kOIDK-0003Mo-Km; Fri, 02 Oct 2020 10:22:58 +0000 Received: from mga12.intel.com ([192.55.52.136]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1kOIDH-0003Lp-Pz for linux-arm-kernel@lists.infradead.org; Fri, 02 Oct 2020 10:22:57 +0000 IronPort-SDR: YsC6f8LtGatdhFvHGcYGmCrmkD6JmYiEhDO58ubi0Gj/VZISSim+64955JxCzc/0hY3jM5G2my vchR3Je4Hx9A== X-IronPort-AV: E=McAfee;i="6000,8403,9761"; a="142349897" X-IronPort-AV: E=Sophos;i="5.77,327,1596524400"; d="scan'208";a="142349897" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Oct 2020 03:22:49 -0700 IronPort-SDR: 01R//bSwrpT8AWXKJgbupPOu4wjn/yB7QVuKW8OCAyuWqF97bwSyXF9Wcz8ZDmuTCICn4v6JL5 fQP6/rlU1V0g== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.77,327,1596524400"; d="scan'208";a="515862195" Received: from orsmsx603.amr.corp.intel.com ([10.22.229.16]) by fmsmga005.fm.intel.com with ESMTP; 02 Oct 2020 03:22:49 -0700 Received: from orsmsx601.amr.corp.intel.com (10.22.229.14) by ORSMSX603.amr.corp.intel.com (10.22.229.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Fri, 2 Oct 2020 03:22:48 -0700 Received: from ORSEDG602.ED.cps.intel.com (10.7.248.7) by orsmsx601.amr.corp.intel.com (10.22.229.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5 via Frontend Transport; Fri, 2 Oct 2020 03:22:48 -0700 Received: from NAM11-CO1-obe.outbound.protection.outlook.com (104.47.56.172) by edgegateway.intel.com (134.134.137.103) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.1713.5; Fri, 2 Oct 2020 03:22:48 -0700 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=SsNf0qq3kffi4zb9L0qw5VBEQsBqv202KvecLrsOxdSSUgrPrxeQu3IPmUQPxklReH2ZDy6TpbuiIH7DeosCT4JKdzSIrxZwpt+K2GBxEpSUh1M3a94kLR7OMzXtj105RyQJbtEzKJ0M8Fe75eMHDPFdZ9q99XDkA7rMHmEMlsaNDjy5+M65m6tQSaQ7UEbi+NJ+u/nbNcwCJZgp5SKet/9oHbE2tl0dcATfV+ufbziN57iebUaog3INyceYz2eF13KeFtW/8vQRaOT2wJGi03C77oZ3/iakv1DbUTZY4GR5QzIFdaXczhQ5puEeG4fszWOzWGvc0abjyQ86qISIQg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=QmkKP1MtLc5+Bd3kvxJBTbfBZHIl7yuC7/u3qfJrdf8=; b=Gd64ozPHwkWPfmOPD6tDPfsdAGvyGTEHhSLWAZeYKZoCPsF2Rq8Aaev0AaAWDmHOKWgcNXCMdl1h0QK3vvB0owyLw3yJm94nWWtCjVwNn5it3199RjJyOOjjjBCWJcvCvMfzLhhxf9Qa1egjeNW7rlkeFE44oaLK5EPPo8CUEO7CXRNLJ5cixIjn1d8GYGFwf+eu2If+4NQSRxGbx4tA6wKYkG7E9xlm04cjsgxtmCuttPB3+mBaW32U4ugT1W210zJmqsLyD6KY84GhVpOI9Cj7Fc7kbyifIS2JaqRhocM/ohMX/GDnLcyy+NJQ6MFuUcbipgiE12dSXQoab+Uhrg== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=intel.com; dmarc=pass action=none header.from=intel.com; dkim=pass header.d=intel.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel.onmicrosoft.com; s=selector2-intel-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=QmkKP1MtLc5+Bd3kvxJBTbfBZHIl7yuC7/u3qfJrdf8=; b=GlBgUfp9EikaIoQX5MpOc4B26XlREDSxZ2tbRloOeEp60VqUafWL7AgAfGDTVNbNCyAfP3TS/3TTjn6ZYDvbzAELfCqKlImp6HU0IyxkybcYfiXGg7Qq4mc78PRwT1jT5NiWBcbo37TQfuJzbDe1S9KPuX7ycegUabou9cWusdo= Received: from BYAPR11MB3015.namprd11.prod.outlook.com (2603:10b6:a03:86::14) by BYAPR11MB3206.namprd11.prod.outlook.com (2603:10b6:a03:78::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.32; Fri, 2 Oct 2020 10:22:46 +0000 Received: from BYAPR11MB3015.namprd11.prod.outlook.com ([fe80::e1af:b9b8:7e60:e77c]) by BYAPR11MB3015.namprd11.prod.outlook.com ([fe80::e1af:b9b8:7e60:e77c%4]) with mapi id 15.20.3433.032; Fri, 2 Oct 2020 10:22:46 +0000 From: "Zulkifli, Muhammad Husaini" To: Michal Simek , Sudeep Holla Subject: RE: [PATCH v2 2/3] firmware: Keem Bay: Add support for Arm Trusted Firmware Service call Thread-Topic: [PATCH v2 2/3] firmware: Keem Bay: Add support for Arm Trusted Firmware Service call Thread-Index: AQHWl/61fFIKn6YDxkK/M5PRzKZE1amC4PoAgAEZhQCAAB6wAA== Date: Fri, 2 Oct 2020 10:22:46 +0000 Message-ID: References: <20201001142149.23445-1-muhammad.husaini.zulkifli@intel.com> <20201001142149.23445-3-muhammad.husaini.zulkifli@intel.com> <20201001153526.GD906@bogus> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-version: 11.5.1.3 dlp-product: dlpe-windows dlp-reaction: no-action authentication-results: xilinx.com; dkim=none (message not signed) header.d=none;xilinx.com; dmarc=none action=none header.from=intel.com; x-originating-ip: [42.189.177.181] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 7fe7ba70-56d3-4a27-4452-08d866bd1b6e x-ms-traffictypediagnostic: BYAPR11MB3206: x-ld-processed: 46c98d88-e344-4ed4-8496-4ed7712e255d,ExtAddr x-ms-exchange-transport-forked: True x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:10000; x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: GmGhdk8w4VYdcPbN0eCqgWmYu++9/2B3aCPDJ8K/+kYpc7yVp/qTRc14or5nH4OKR3O8W2CK9/HaZMA6MeMA/5xwjgUDdHTgOnwDYaRhE1tUrOQZyLDnoBxmzU+p7mh2hMbaY9z3hjHRASI6idB4fbFg/lk4MOr/fQOhfVwFQS08BSPwg4yFEVsBIETnxmLc1gkK2hkCfCsFRPnNqis75cUp1xr9Rdr/b8kFh4GMzTFniZYiaxkLQwHwoII71507y9eBxm2OHFus/3jtRZ2ZfEr3avzJuiscpT6gnNW7DquO7fHXIzWHRDQGEYeJvB24A0Rqa3Ww/cWGztGoD4SG9w== x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BYAPR11MB3015.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(366004)(136003)(39860400002)(346002)(376002)(396003)(7696005)(55016002)(9686003)(83380400001)(71200400001)(8936002)(6506007)(86362001)(2906002)(4326008)(107886003)(5660300002)(110136005)(66556008)(52536014)(8676002)(66446008)(26005)(64756008)(66946007)(54906003)(186003)(66476007)(33656002)(76116006)(316002)(478600001); DIR:OUT; SFP:1102; x-ms-exchange-antispam-messagedata: 0InjAz7K3BDPDErwVvI8qErvyoIo+kfkdeHMpNv85sX01bEiTqL4yOiM/EiBgb5KgjPFCNJ2QKj4hR74u/t/fDXWQ1/PSiDWscTQvVQ1zEH74OiGn2COajhJgD1+jFWCQppxNoxXIY7ss8J4FMTPmSmYj2fbmhKnedSIPWVj8pBtcOyMwSTcoLcYiQuyVVAiGFhKFNJL4NpsRc95zPJFrfOC6YGl8sTk+9731lM+pcZh8Qs2idkH4GEJgCsUlihK6pGC4YcfVL9LDGd32PYmuqf6hB4bvUYVKzkOlKaSJ6K1BoiClpM+cNPWCLevdhjh2/SKcI5KdRARK7bg+0D5VdFf5hoImrYfgaqFKwkXMS3s6fyF9QxuekNGevJrYu4RXyP+jJGCZXs37OSq4gDYQurgcRSqET22uIzKLd+JCsZRJHRPfaXeOtuMq3/vHzYUJzwWVle7i7PAPOvr4j43qa+r0McKS/afhm5vGnqYKvpVBy5SnI02JDETRDqLvwnQuWJPwUPmisZUHyRpQVmWVInc2fCBcPWQIOC+DM4QrkXHMWMG8TkYAtSwq8V/9ryN0lgP9mzugsNppbH5Sl9RSItTqVETFy6EWn++x8/FNvSDg2sQa4RibKSt4fx1R60Sz/Jl3TJnu1y4Y+YUmNBj1w== MIME-Version: 1.0 X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: BYAPR11MB3015.namprd11.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 7fe7ba70-56d3-4a27-4452-08d866bd1b6e X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Oct 2020 10:22:46.6909 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 46c98d88-e344-4ed4-8496-4ed7712e255d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: o/E7dT82tGu9d8MblTQEbxTAwdyJCERLTX/3+A3xezfXMwCAXl4/ZsKBcGf5ge2ntO5xpUJ/j4ENABQYX2AV1oBjtJIgXv+Wmo4HYZ6wizLTmBbPVo63oEMlKS4Nz9C9 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3206 X-OriginatorOrg: intel.com X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20201002_062256_044937_E1BDFA27 X-CRM114-Status: GOOD ( 20.79 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "ulf.hansson@linaro.org" , "arnd@arndb.de" , "Raja Subramanian, Lakshmi Bai" , "linux-mmc@vger.kernel.org" , "Hunter, Adrian" , "linux-kernel@vger.kernel.org" , "Wan Mohamad, Wan Ahmad Zainie" , "linux-arm-kernel@lists.infradead.org" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi Sudeep, >-----Original Message----- >From: Michal Simek >Sent: Friday, October 2, 2020 4:23 PM >To: Sudeep Holla ; Zulkifli, Muhammad Husaini > >Cc: Hunter, Adrian ; michal.simek@xilinx.com; >ulf.hansson@linaro.org; linux-mmc@vger.kernel.org; linux-arm- >kernel@lists.infradead.org; linux-kernel@vger.kernel.org; Raja Subramanian, >Lakshmi Bai ; arnd@arndb.de; Wan >Mohamad, Wan Ahmad Zainie >Subject: Re: [PATCH v2 2/3] firmware: Keem Bay: Add support for Arm Trusted >Firmware Service call > >Hi Sudeep, > >On 01. 10. 20 17:35, Sudeep Holla wrote: >> On Thu, Oct 01, 2020 at 10:21:48PM +0800, >muhammad.husaini.zulkifli@intel.com wrote: >>> From: Muhammad Husaini Zulkifli >>> >>> Add generic firmware driver for Keem Bay SOC to support Arm Trusted >>> Firmware Services call. >>> >>> Signed-off-by: Muhammad Husaini Zulkifli >>> >>> --- >>> drivers/firmware/Kconfig | 1 + >>> drivers/firmware/Makefile | 1 + >>> drivers/firmware/intel/Kconfig | 14 +++ >>> drivers/firmware/intel/Makefile | 4 + >>> drivers/firmware/intel/keembay_smc.c | 119 +++++++++++++++++++++ >>> include/linux/firmware/intel/keembay_smc.h | 27 +++++ >>> 6 files changed, 166 insertions(+) >>> create mode 100644 drivers/firmware/intel/Kconfig create mode >>> 100644 drivers/firmware/intel/Makefile create mode 100644 >>> drivers/firmware/intel/keembay_smc.c >>> create mode 100644 include/linux/firmware/intel/keembay_smc.h >>> >>> diff --git a/drivers/firmware/Kconfig b/drivers/firmware/Kconfig >>> index fbd785dd0513..41de77d2720e 100644 >>> --- a/drivers/firmware/Kconfig >>> +++ b/drivers/firmware/Kconfig >>> @@ -305,5 +305,6 @@ source "drivers/firmware/psci/Kconfig" >>> source "drivers/firmware/smccc/Kconfig" >>> source "drivers/firmware/tegra/Kconfig" >>> source "drivers/firmware/xilinx/Kconfig" >>> +source "drivers/firmware/intel/Kconfig" >>> >>> endmenu >>> diff --git a/drivers/firmware/Makefile b/drivers/firmware/Makefile >>> index 99510be9f5ed..00f295ab9860 100644 >>> --- a/drivers/firmware/Makefile >>> +++ b/drivers/firmware/Makefile >>> @@ -33,3 +33,4 @@ obj-y += psci/ >>> obj-y += smccc/ >>> obj-y += tegra/ >>> obj-y += xilinx/ >>> +obj-y += intel/ >>> diff --git a/drivers/firmware/intel/Kconfig >>> b/drivers/firmware/intel/Kconfig new file mode 100644 index >>> 000000000000..b2b7a4e5410b >>> --- /dev/null >>> +++ b/drivers/firmware/intel/Kconfig >>> @@ -0,0 +1,14 @@ >>> +# SPDX-License-Identifier: GPL-2.0-only menu "Intel Firmware >>> +Drivers" >>> + >>> +config KEEMBAY_FIRMWARE >>> + bool "Enable Keem Bay firmware interface support" >>> + depends on HAVE_ARM_SMCCC >> >> What is the version of SMCCC implemented ? Our current Arm Trusted Firmware framework supports v1.1. Does it mean I should use HAVE_ARM_SMCCC_DISCOVERY? Not really clear about this. As for HAVE_ARM_SMCCC will include support for the SMC and HVC. >> If SMCCC v1.1+, use HAVE_ARM_SMCCC_DISCOVERY >> >>> + default n >>> + help >>> + Firmware interface driver is used by device drivers >>> + to communicate with the arm-trusted-firmware >>> + for platform management services. >>> + If in doubt, say "N". >>> + >>> +endmenu >>> diff --git a/drivers/firmware/intel/Makefile >>> b/drivers/firmware/intel/Makefile new file mode 100644 index >>> 000000000000..e6d2e1ea69a7 >>> --- /dev/null >>> +++ b/drivers/firmware/intel/Makefile >>> @@ -0,0 +1,4 @@ >>> +# SPDX-License-Identifier: GPL-2.0 >>> +# Makefile for Intel firmwares >>> + >>> +obj-$(CONFIG_KEEMBAY_FIRMWARE) = keembay_smc.o >>> diff --git a/drivers/firmware/intel/keembay_smc.c >>> b/drivers/firmware/intel/keembay_smc.c >>> new file mode 100644 >>> index 000000000000..24013cd1f5da >>> --- /dev/null >>> +++ b/drivers/firmware/intel/keembay_smc.c >>> @@ -0,0 +1,119 @@ >>> +// SPDX-License-Identifier: GPL-2.0 >>> +/* >>> + * Copyright (C) 2020-2021, Intel Corporation */ >>> + >>> +#include >>> +#include >>> +#include >>> +#include >>> + >>> +#include >>> + >>> +static noinline int do_fw_call_fail(u64 arg0, u64 arg1) { >>> + return -ENODEV; >>> +} >>> + >>> +/** >>> + * Simple wrapper functions to be able to use a function pointer >>> + * Invoke do_fw_call_smc or others in future, depending on the >>> +configuration */ static int (*do_fw_call)(u64, u64) = >>> +do_fw_call_fail; >>> + >>> +/** >>> + * do_fw_call_smc() - Call system-level platform management layer (SMC) >>> + * @arg0: Argument 0 to SMC call >>> + * @arg1: Argument 1 to SMC call >>> + * >>> + * Invoke platform management function via SMC call. >>> + * >>> + * Return: Returns status, either success or error */ static >>> +noinline int do_fw_call_smc(u64 arg0, u64 arg1) { >>> + struct arm_smccc_res res; >>> + >>> + arm_smccc_smc(arg0, arg1, 0, 0, 0, 0, 0, 0, &res); >>> + >>> + return res.a0; >>> +} >>> + >>> +/** >>> + * keembay_sd_voltage_selection() - Set the IO Pad voltage >>> + * @volt: voltage selection either 1.8V or 3.3V >>> + * >>> + * This function is used to set the IO Line Voltage >>> + * >>> + * Return: 0 for success, Invalid for failure */ int >>> +keembay_sd_voltage_selection(int volt) { >>> + return do_fw_call(KEEMBAY_SIP_FUNC_ID, volt); >> >> >> What are the other uses of this KEEMBAY_SIP_* ? >> For now I tend to move this to the driver making use of it using >> arm_smccc_1_1_invoke directly if possible. I don't see the need for >> this to be separate driver. But do let us know the features >> implemented in the firmware. If it is not v1.1+, reasons for not >> upgrading as you need v1.1 for some CPU errata implementation. > >This driver has been created based on my request to move it out the mmc >driver. It looks quite hacky to have arm_smccc_res and call >arm_smccc_smc() also with some IDs where it is visible that the part of ID is just >based on any spec. >Also in v1 he is just calling SMC. But maybe there is going a need to call HVC >instead which is something what device driver shouldn't decide that's why >IMHO doing step via firmware driver is much better approach. >Of course if there is a better/cleaner way how this should be done I am happy >to get more information about it. > >Thanks, >Michal > > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel