Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754879AbdCIN2m (ORCPT ); Thu, 9 Mar 2017 08:28:42 -0500 Received: from foss.arm.com ([217.140.101.70]:43408 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753861AbdCIN2k (ORCPT ); Thu, 9 Mar 2017 08:28:40 -0500 From: Suzuki K Poulose To: leo.yan@linaro.org Cc: linux-arm-kernel@lists.infradead.org, Wei Xu , catalin.marinas@arm.com, will.deacon@arm.com, mark.rutland@arm.com, mathieu.poirier@linaro.org, Stephen Boyd , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, mike.leach@linaro.org, Michael Turquette , Guodong Xu , John Stultz , Suzuki K Poulose Subject: Re: [v3 1/5] coresight: bindings for debug module Date: Thu, 9 Mar 2017 13:27:40 +0000 Message-Id: <1489066060-3513-1-git-send-email-suzuki.poulose@arm.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1488520809-31670-2-git-send-email-leo.yan@linaro.org> References: <1488520809-31670-2-git-send-email-leo.yan@linaro.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 273 Lines: 6 To be honest, coresight-debug sounds too generic and could be confusing with lot of the other components. To be precise, the area is for External Debug to a CPU. So "arm,coresight-cpu-debug" or even "arm,coresight-cpu-external-debug" sounds more appropriate to me. Suzuki