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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 505BBC433FE for ; Tue, 1 Mar 2022 14:12:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235155AbiCAOMk (ORCPT ); Tue, 1 Mar 2022 09:12:40 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59908 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229730AbiCAOMj (ORCPT ); Tue, 1 Mar 2022 09:12:39 -0500 Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AC6852649 for ; Tue, 1 Mar 2022 06:11:57 -0800 (PST) Received: by mail-ej1-x632.google.com with SMTP id gb39so31764329ejc.1 for ; Tue, 01 Mar 2022 06:11:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MfimAMOL9WrDUaU8ysDXEywlIYs/LjUgbSBpoFo63aY=; b=diqOb2yAU+tqO43un6fTJiInrvAguRgXo6fKbg98DcAITNF7Gl/ir+uwUFM4exGOnE YWlZD/j93Kus3CV+xQR5OC5IMibNE7XQ2pB/aTfiI/1KZNPNXcOO3N9Wf3Vm40eucwnf KCZsoDpcY3RlPvtOsdJvp3hvhWagp6mK0k8X9hB4q0IxoucacjoWQi8jZW0I4mBzsyy9 n6oZMx4YJlf1gFF12Wsy9ZDaGuUem8Mt98GLD1DxF50P0y5ScMfaySWjOjxxNE6G+z7v xyulVL4kfYG9fG3Wd3tJMX78+QbEpgZ8N6/qMfJwekH8lawM05Io640S/r6Xl6082e7W cILg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MfimAMOL9WrDUaU8ysDXEywlIYs/LjUgbSBpoFo63aY=; b=EGEJF8hLep1NOdF0hgJ0bfhINBM6pZtSbAb0OPKN2JsL5suwAydNiRiXSJKSIazR1u 6G4pTYJ9piTadCVNClcOXTm2wMBVNWiTgrMyl1HqJOwwCVaYb+NdhqAvvwZQXkLStuU2 wBn1LLsm3og3JdGsyTjRDWmgWDEr0CnFlq83sE6uLJJRyzsnSddfpec+uxLJLDQivH8x Oa2sdy64n9wKLLQaWzG1THGsFXUJhRFpEbEp6utPa6/A9VohbX4RlpR6FSG10FH90tsj 6t7ti1qaVaHBKQmuN1ekzRiRbnpvqtbeuS6nrGMgM7Oie24xA9JGhTtTkj3oTueRNJiC HaCw== X-Gm-Message-State: AOAM531qbiKAhTeitl1t9boiZykauLvZU08Axk0ZCDll5+LU5Wa0+Y2+ o77693KVh8E/f3T8d5jqMgQRi8IlQwVtZVZBwsfTdA== X-Google-Smtp-Source: ABdhPJyQzWax9/NRtsMdZsexRmcWnD7j8+o1lWNAilFPrZ3u8SDBbGi9pMoyHhZ+JtbcuqS+XYYSjU6RcqlDOS3fzRU= X-Received: by 2002:a17:906:2ecd:b0:6d3:d7c9:8fa4 with SMTP id s13-20020a1709062ecd00b006d3d7c98fa4mr18884616eji.144.1646143916142; Tue, 01 Mar 2022 06:11:56 -0800 (PST) MIME-Version: 1.0 References: <20211028140009.23331-1-etienne.carriere@linaro.org> <58a0e791-9573-99c2-0cc5-3920a1048113@pengutronix.de> In-Reply-To: From: Etienne Carriere Date: Tue, 1 Mar 2022 15:11:44 +0100 Message-ID: Subject: Re: [PATCH v8 1/2] dt-bindings: arm: Add OP-TEE transport for SCMI To: Ahmad Fatoum Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Sudeep Holla , Cristian Marussi , Vincent Guittot , devicetree@vger.kernel.org, Rob Herring , Pengutronix Kernel Team Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi sorry, I sent the mail while i was still typing it... Here is with the full answer. On Tue, 1 Mar 2022 at 15:05, Etienne Carriere wrote: > > Hello Ahmad, > > On Mon, 28 Feb 2022 at 17:01, Ahmad Fatoum wrote: > > > > Hello Etienne, > > > > On 28.10.21 16:00, Etienne Carriere wrote: > > > Introduce compatible "linaro,scmi-optee" for SCMI transport channel > > > based on an OP-TEE service invocation. The compatible mandates a > > > channel ID defined with property "linaro,optee-channel-id". > > > > I just found this thread via the compatible in the STM32MP131 patch set: > > https://lore.kernel.org/all/20220225133137.813919-1-gabriel.fernandez@foss.st.com/ > > > > Linux doesn't care whether PSCI is provided by TF-A, OP-TEE or something > > else, so there is just the arm,psci* compatible. > > > > What's different about SCMI that this is not possible? Why couldn't the > > existing binding and driver be used to communicate with OP-TEE as secure > > monitor as well? > > Compatible "linaro,scmi-optee" denote a alternate SCMI transport to > those already in v5.16. It is names scmi-optee because the interface exposed to access SCMI services is based on TEE's interface (UUID to open a session with and invoke commands). The compatible is described in the Linux Documentation but not yet merged in the linux-next. It can be found in the tree of arm_scmi driver maintainers: https://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git/log/?h=for-linux-next This commit: https://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git/commit/?h=for-linux-next&id=b7d2cf7c817b86e705b97f72c6be192a6760a14f Br, Etienne > > > > > > Cheers, > > Ahmad > > > > > > > > Cc: devicetree@vger.kernel.org > > > Cc: Rob Herring > > > Signed-off-by: Etienne Carriere > > > --- > > > Changes since v6: > > > - Remove maxItems from linaro,optee-channel-id description > > > > > > No change since v5 > > > > > > Changes since v4: > > > - Fix sram node name in DTS example: s/-shm-/-sram-/ > > > > > > Changes since v3: > > > - Add description for linaro,optee-channel-id in patternProperties > > > specifying protocol can optionaly define a dedicated channel id. > > > - Fix DTS example (duplicated phandles issue, subnodes ordering) > > > - Fix typo in DTS example and description comments. > > > > > > Changes since v2: > > > - Define mandatory property linaro,optee-channel-id > > > - Rebased on yaml description file > > > > > > Changes since v1: > > > - Removed modification regarding mboxes property description. > > > --- > > > .../bindings/firmware/arm,scmi.yaml | 65 +++++++++++++++++++ > > > 1 file changed, 65 insertions(+) > > > > > > diff --git a/Documentation/devicetree/bindings/firmware/arm,scmi.yaml b/Documentation/devicetree/bindings/firmware/arm,scmi.yaml > > > index 5c4c6782e052..eae15df36eef 100644 > > > --- a/Documentation/devicetree/bindings/firmware/arm,scmi.yaml > > > +++ b/Documentation/devicetree/bindings/firmware/arm,scmi.yaml > > > @@ -38,6 +38,9 @@ properties: > > > The virtio transport only supports a single device. > > > items: > > > - const: arm,scmi-virtio > > > + - description: SCMI compliant firmware with OP-TEE transport > > > + items: > > > + - const: linaro,scmi-optee > > > > > > interrupts: > > > description: > > > @@ -83,6 +86,11 @@ properties: > > > description: > > > SMC id required when using smc or hvc transports > > > > > > + linaro,optee-channel-id: > > > + $ref: /schemas/types.yaml#/definitions/uint32 > > > + description: > > > + Channel specifier required when using OP-TEE transport. > > > + > > > protocol@11: > > > type: object > > > properties: > > > @@ -195,6 +203,12 @@ patternProperties: > > > minItems: 1 > > > maxItems: 2 > > > > > > + linaro,optee-channel-id: > > > + $ref: /schemas/types.yaml#/definitions/uint32 > > > + description: > > > + Channel specifier required when using OP-TEE transport and > > > + protocol has a dedicated communication channel. > > > + > > > required: > > > - reg > > > > > > @@ -226,6 +240,16 @@ else: > > > - arm,smc-id > > > - shmem > > > > > > + else: > > > + if: > > > + properties: > > > + compatible: > > > + contains: > > > + const: linaro,scmi-optee > > > + then: > > > + required: > > > + - linaro,optee-channel-id > > > + > > > examples: > > > - | > > > firmware { > > > @@ -340,7 +364,48 @@ examples: > > > reg = <0x11>; > > > #power-domain-cells = <1>; > > > }; > > > + }; > > > + }; > > > + > > > + - | > > > + firmware { > > > + scmi { > > > + compatible = "linaro,scmi-optee"; > > > + linaro,optee-channel-id = <0>; > > > + > > > + #address-cells = <1>; > > > + #size-cells = <0>; > > > + > > > + scmi_dvfs1: protocol@13 { > > > + reg = <0x13>; > > > + linaro,optee-channel-id = <1>; > > > + shmem = <&cpu_optee_lpri0>; > > > + #clock-cells = <1>; > > > + }; > > > + > > > + scmi_clk0: protocol@14 { > > > + reg = <0x14>; > > > + #clock-cells = <1>; > > > + }; > > > + }; > > > + }; > > > > > > + soc { > > > + #address-cells = <2>; > > > + #size-cells = <2>; > > > + > > > + sram@51000000 { > > > + compatible = "mmio-sram"; > > > + reg = <0x0 0x51000000 0x0 0x10000>; > > > + > > > + #address-cells = <1>; > > > + #size-cells = <1>; > > > + ranges = <0 0x0 0x51000000 0x10000>; > > > + > > > + cpu_optee_lpri0: optee-sram-section@0 { > > > + compatible = "arm,scmi-shmem"; > > > + reg = <0x0 0x80>; > > > + }; > > > }; > > > }; > > > > > > > > > -- > > Pengutronix e.K. | | > > Steuerwalder Str. 21 | http://www.pengutronix.de/ | > > 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | > > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | 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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 79753C43217 for ; Tue, 1 Mar 2022 14:13:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:Cc:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=HZuDo6TZ3HItzHC47gAbA9pSDfeVZQ3rT5kjlxbtWcQ=; b=CxgiPwbx3bIdGA 9uo9BX3Hdj0xCqmbFFBzSritpJpTTmB/uq1wSRissaEC0sxxA8BeR8qrpv+1DmF3rf8azl9ARYvAI qLwJeo4LM132YfYFQmD+HUrSRM9VbBgKl0rWwym507eeCcY1tqnToE7XVaTY2KVIwNQ5IQ12YcrKW CI+6rCXhkR0QfN0aWhhHkoEe7rSCvoTZ2SmD97IuFGb/TmfWjtIW/RVyP9gBvSHxb332Mx0+ItlAQ sk4wAGkK06zuLX+lMtIs1YdV1scnYU/o+HdojSaSW5G9t0GsxXmtm+oRM+wA1Xi+cngaS65wG3sx/ mbJmI2qFMrrZ2cTsF12w==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nP3EP-00Gzxn-Vi; Tue, 01 Mar 2022 14:12:02 +0000 Received: from mail-ej1-x629.google.com ([2a00:1450:4864:20::629]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nP3EL-00Gzwm-SV for linux-arm-kernel@lists.infradead.org; Tue, 01 Mar 2022 14:11:59 +0000 Received: by mail-ej1-x629.google.com with SMTP id r13so31752492ejd.5 for ; Tue, 01 Mar 2022 06:11:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MfimAMOL9WrDUaU8ysDXEywlIYs/LjUgbSBpoFo63aY=; b=diqOb2yAU+tqO43un6fTJiInrvAguRgXo6fKbg98DcAITNF7Gl/ir+uwUFM4exGOnE YWlZD/j93Kus3CV+xQR5OC5IMibNE7XQ2pB/aTfiI/1KZNPNXcOO3N9Wf3Vm40eucwnf KCZsoDpcY3RlPvtOsdJvp3hvhWagp6mK0k8X9hB4q0IxoucacjoWQi8jZW0I4mBzsyy9 n6oZMx4YJlf1gFF12Wsy9ZDaGuUem8Mt98GLD1DxF50P0y5ScMfaySWjOjxxNE6G+z7v xyulVL4kfYG9fG3Wd3tJMX78+QbEpgZ8N6/qMfJwekH8lawM05Io640S/r6Xl6082e7W cILg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MfimAMOL9WrDUaU8ysDXEywlIYs/LjUgbSBpoFo63aY=; b=6/mm2vseQfSz8uipUsUQYLk1S5lL32s+SJFoUMGCMureYzHRKxFWvbm2hh2SeEI+Jo 5vpCKsnMCq3lamFNdEp5nytQruSDEAzHwoqUecASxUjeg8T2g59CYXajVQbEn59pLWZ1 NRhhYVTVBA0pYPOFRR8guZm21h9pC5nAYPkq7d9pV/9wjpny2n46f7JZ8SsJxnGm1S1V AiqnfNbu2xm3HsR84IRVQLYguHByIO6Mp+6xYAG3ndAPUO+sZV9KVHeI6tFkYLcaMIJh 6UWbKGGgJmE+Dz6zQib9/scYuNkOMeqXb0nfYKoZgJzWoWs8M3cZw7cowakCyvGTkg/t V6cw== X-Gm-Message-State: AOAM5321CLWJv7GztlhMjDsKRl4nq4jaQdaot6uJLkAelBBKKwBozDFQ 6lY92iFkoe4ixAkAEP+DQ1Vm52okz17UCE7R08ahlm5CMV9I5w== X-Google-Smtp-Source: ABdhPJyQzWax9/NRtsMdZsexRmcWnD7j8+o1lWNAilFPrZ3u8SDBbGi9pMoyHhZ+JtbcuqS+XYYSjU6RcqlDOS3fzRU= X-Received: by 2002:a17:906:2ecd:b0:6d3:d7c9:8fa4 with SMTP id s13-20020a1709062ecd00b006d3d7c98fa4mr18884616eji.144.1646143916142; Tue, 01 Mar 2022 06:11:56 -0800 (PST) MIME-Version: 1.0 References: <20211028140009.23331-1-etienne.carriere@linaro.org> <58a0e791-9573-99c2-0cc5-3920a1048113@pengutronix.de> In-Reply-To: From: Etienne Carriere Date: Tue, 1 Mar 2022 15:11:44 +0100 Message-ID: Subject: Re: [PATCH v8 1/2] dt-bindings: arm: Add OP-TEE transport for SCMI To: Ahmad Fatoum Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Sudeep Holla , Cristian Marussi , Vincent Guittot , devicetree@vger.kernel.org, Rob Herring , Pengutronix Kernel Team X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220301_061157_952783_29970C65 X-CRM114-Status: GOOD ( 33.12 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 sorry, I sent the mail while i was still typing it... Here is with the full answer. On Tue, 1 Mar 2022 at 15:05, Etienne Carriere wrote: > > Hello Ahmad, > > On Mon, 28 Feb 2022 at 17:01, Ahmad Fatoum wrote: > > > > Hello Etienne, > > > > On 28.10.21 16:00, Etienne Carriere wrote: > > > Introduce compatible "linaro,scmi-optee" for SCMI transport channel > > > based on an OP-TEE service invocation. The compatible mandates a > > > channel ID defined with property "linaro,optee-channel-id". > > > > I just found this thread via the compatible in the STM32MP131 patch set: > > https://lore.kernel.org/all/20220225133137.813919-1-gabriel.fernandez@foss.st.com/ > > > > Linux doesn't care whether PSCI is provided by TF-A, OP-TEE or something > > else, so there is just the arm,psci* compatible. > > > > What's different about SCMI that this is not possible? Why couldn't the > > existing binding and driver be used to communicate with OP-TEE as secure > > monitor as well? > > Compatible "linaro,scmi-optee" denote a alternate SCMI transport to > those already in v5.16. It is names scmi-optee because the interface exposed to access SCMI services is based on TEE's interface (UUID to open a session with and invoke commands). The compatible is described in the Linux Documentation but not yet merged in the linux-next. It can be found in the tree of arm_scmi driver maintainers: https://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git/log/?h=for-linux-next This commit: https://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git/commit/?h=for-linux-next&id=b7d2cf7c817b86e705b97f72c6be192a6760a14f Br, Etienne > > > > > > Cheers, > > Ahmad > > > > > > > > Cc: devicetree@vger.kernel.org > > > Cc: Rob Herring > > > Signed-off-by: Etienne Carriere > > > --- > > > Changes since v6: > > > - Remove maxItems from linaro,optee-channel-id description > > > > > > No change since v5 > > > > > > Changes since v4: > > > - Fix sram node name in DTS example: s/-shm-/-sram-/ > > > > > > Changes since v3: > > > - Add description for linaro,optee-channel-id in patternProperties > > > specifying protocol can optionaly define a dedicated channel id. > > > - Fix DTS example (duplicated phandles issue, subnodes ordering) > > > - Fix typo in DTS example and description comments. > > > > > > Changes since v2: > > > - Define mandatory property linaro,optee-channel-id > > > - Rebased on yaml description file > > > > > > Changes since v1: > > > - Removed modification regarding mboxes property description. > > > --- > > > .../bindings/firmware/arm,scmi.yaml | 65 +++++++++++++++++++ > > > 1 file changed, 65 insertions(+) > > > > > > diff --git a/Documentation/devicetree/bindings/firmware/arm,scmi.yaml b/Documentation/devicetree/bindings/firmware/arm,scmi.yaml > > > index 5c4c6782e052..eae15df36eef 100644 > > > --- a/Documentation/devicetree/bindings/firmware/arm,scmi.yaml > > > +++ b/Documentation/devicetree/bindings/firmware/arm,scmi.yaml > > > @@ -38,6 +38,9 @@ properties: > > > The virtio transport only supports a single device. > > > items: > > > - const: arm,scmi-virtio > > > + - description: SCMI compliant firmware with OP-TEE transport > > > + items: > > > + - const: linaro,scmi-optee > > > > > > interrupts: > > > description: > > > @@ -83,6 +86,11 @@ properties: > > > description: > > > SMC id required when using smc or hvc transports > > > > > > + linaro,optee-channel-id: > > > + $ref: /schemas/types.yaml#/definitions/uint32 > > > + description: > > > + Channel specifier required when using OP-TEE transport. > > > + > > > protocol@11: > > > type: object > > > properties: > > > @@ -195,6 +203,12 @@ patternProperties: > > > minItems: 1 > > > maxItems: 2 > > > > > > + linaro,optee-channel-id: > > > + $ref: /schemas/types.yaml#/definitions/uint32 > > > + description: > > > + Channel specifier required when using OP-TEE transport and > > > + protocol has a dedicated communication channel. > > > + > > > required: > > > - reg > > > > > > @@ -226,6 +240,16 @@ else: > > > - arm,smc-id > > > - shmem > > > > > > + else: > > > + if: > > > + properties: > > > + compatible: > > > + contains: > > > + const: linaro,scmi-optee > > > + then: > > > + required: > > > + - linaro,optee-channel-id > > > + > > > examples: > > > - | > > > firmware { > > > @@ -340,7 +364,48 @@ examples: > > > reg = <0x11>; > > > #power-domain-cells = <1>; > > > }; > > > + }; > > > + }; > > > + > > > + - | > > > + firmware { > > > + scmi { > > > + compatible = "linaro,scmi-optee"; > > > + linaro,optee-channel-id = <0>; > > > + > > > + #address-cells = <1>; > > > + #size-cells = <0>; > > > + > > > + scmi_dvfs1: protocol@13 { > > > + reg = <0x13>; > > > + linaro,optee-channel-id = <1>; > > > + shmem = <&cpu_optee_lpri0>; > > > + #clock-cells = <1>; > > > + }; > > > + > > > + scmi_clk0: protocol@14 { > > > + reg = <0x14>; > > > + #clock-cells = <1>; > > > + }; > > > + }; > > > + }; > > > > > > + soc { > > > + #address-cells = <2>; > > > + #size-cells = <2>; > > > + > > > + sram@51000000 { > > > + compatible = "mmio-sram"; > > > + reg = <0x0 0x51000000 0x0 0x10000>; > > > + > > > + #address-cells = <1>; > > > + #size-cells = <1>; > > > + ranges = <0 0x0 0x51000000 0x10000>; > > > + > > > + cpu_optee_lpri0: optee-sram-section@0 { > > > + compatible = "arm,scmi-shmem"; > > > + reg = <0x0 0x80>; > > > + }; > > > }; > > > }; > > > > > > > > > -- > > Pengutronix e.K. | | > > Steuerwalder Str. 21 | http://www.pengutronix.de/ | > > 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | > > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel