From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932445AbcBIPAE (ORCPT <rfc822;w@1wt.eu>);
	Tue, 9 Feb 2016 10:00:04 -0500
Received: from mout.kundenserver.de ([212.227.126.130]:54421 "EHLO
	mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1756585AbcBIO77 (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 9 Feb 2016 09:59:59 -0500
From: Arnd Bergmann <arnd@arndb.de>
To: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
        ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
        devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
        linux-arm-kernel@lists.infradead.org, arm@kernel.org,
        brijeshkumar.singh@amd.com, thomas.lendacky@amd.com, leo.duran@amd.com,
        Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: Re: [PATCH V2 09/12] dtb: amd: Add KCS device tree node
Date: Tue, 09 Feb 2016 15:59:17 +0100
Message-ID: <4018438.bPuTyoUuqf@wuerfel>
User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; )
In-Reply-To: <1454954357-8395-10-git-send-email-Suravee.Suthikulpanit@amd.com>
References: <1454954357-8395-1-git-send-email-Suravee.Suthikulpanit@amd.com> <1454954357-8395-10-git-send-email-Suravee.Suthikulpanit@amd.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Provags-ID: V03:K0:+KdMyCgT9X0TjAGUgRSWcmoRDBn7D4FGcn5NDge6KKqmd5NoKrg
 QoU2PsmGECQBqXDF39pGGxLrNXE6u3ivYNm9lhY7ySJ1F5KQxHnnB2bOpi2xSe47amTllZU
 o0rvUijyIlGC9/tPM467tRUaRjrS0oVnqbm9wthlfvSo5WAScvmfsLa7AsZWubzS+x1I5D9
 Tb7+padlAEQJWx655aCqg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:UrepkfUTL9I=:YL0KhFxbT4VCMtq7nRG6mX
 ddeYi12Tizas9eFI6LFaRI/evvei5BODvwh36wFC+PLZ7plnKw/0WzfyPIk/36ejQ+QSC7hLK
 6PRNH5okgHHBmstWooZrhEJ0C1CwirupRqMu8ghKAEuxEVO7W9R2tKA0X/aek7Y8x9vCgI2UI
 kY0aHd3ruLZzJUjY77XbKZOR8Vcru3h8muCqb40Wnz6x09hZ/3JrRXhm8lFZ4jYHcBqqQJGUD
 Qg2rlKHnYtd3WSLYnkzZs+9455FaI2cQJM6UttqrtbC0GJ/9wF+cnd+BTqccCNMHvB/4tbOuv
 2xdjDgt8a+VR2IROphzlpO7sY7oV4zcKYrPPjI+Q9NI+C59/vbaU0fU8BRSXRHgv8nz5mxKSz
 Hlkks263Pe9SK29GKFqJ7V3kj9McZYen3Z26JVdjyq3PAiP/c+994XSIvIjUODrLPtcnlII1+
 3hTpOLKMBvBlK1EIkbjhR22gu/uGgzpk5DloRpNhZa+uPyXhcfi2Z3ymYW4s1zuwrpmVUBEK+
 hTQWpWh1IaMsZvLq5JTXrNp+LWjJI9PL23V3E5FXm0qsFPwHYb9eodKJTuk9PJFeMFQhL1663
 duWZ5A9PJBYpMDgxkorKZf8dTWPdCssu0xHywLiJioyn5dvtf9gTb0x0/eMY6Z1vb/L65CQQO
 BCuc+NpedmoAt9vAIGjm6ZhuVtoDn5cvIjiy9hdcsGU4wLzI+YVVZ+Ui1bM5p4lo6uMxMLg/y
 fgPwHH2vxKqODrTH
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Monday 08 February 2016 11:59:14 Suravee Suthikulpanit wrote:
> +
> +               ipmi_kcs: kcs@e0010000 {
> +                       status = "disabled";
> +                       compatible = "ipmi-kcs";
> +                       device_type = "ipmi";
> +                       reg = <0x0 0xe0010000 0 0x8>;
> +                       interrupts = <0 389 4>;
> +                       interrupt-names = "ipmi_kcs";
> +                       reg-size = <1>;
> +                       reg-spacing = <4>;
> +               };
>         };
> 

I see we don't have a binding file for this, can you add one please?


Why the strange name for the interrupt?

	Arnd