Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp3357659imm; Mon, 4 Jun 2018 02:06:34 -0700 (PDT) X-Google-Smtp-Source: ADUXVKJT2pFw1JZLV23ZTB5zurCxAfjmLyiVF5UvChcA0OTnaAIvygp+soOXPaoUrAv8XcRWXgi9 X-Received: by 2002:a63:3759:: with SMTP id g25-v6mr16982853pgn.59.1528103194846; Mon, 04 Jun 2018 02:06:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528103194; cv=none; d=google.com; s=arc-20160816; b=v4OaJ+g6hYk7gcnovE6q3XIYSfjKD1ygBTmvVjkJNRv7DmTiGKKOBQUHvLBQZ/0JLX bFzO12D0y7L9p+2+hl2bpRN0NSVTt11ZjuAS/tX9rfoeu5blHOOTxfjooS5iYXilc7Am QHR10BAl4lsXemGGWm9ll+1d+giUOwG7NrvcYb2sD73fcl2/tEmfmFMro/FhSJxm/9CR m1CbwdUcUecIRgrA+cLNb4M5odPCFNeUlf4YXwF0xQ9tyAE0OREu7tXAA30W/N6az7Co 62ZveV9YKf9QTc8qnduD+NLMXQ4fJmtHQWpqz0m5wqQrH/ngexI0NBTqIF3wStEzi2oP pzIA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id :arc-authentication-results; bh=Oepg5b6j+3/r0R3u3gDS1pFa+sOo8TuC8QuWlhqJxII=; b=oHBgYQ61csZDvOxyqeK0rZ3dxJmUKfSAoqn2SoRrWBgTpt12igKi4dIKXI0p+kB1G2 pXPZel95ab0IoMGucpj9nw+5zuwHoXPriorZbce7qGxpHis6WWLM7wvIjqMovgRxTkyM 4y+O70MiKf18DonffeO0wjRAITSnsQsrj2vbkiAhxxwif7kCS0EHoonePlCYmVGpuaAG FMhHPu8btRvERJxufKsOyrufZxy7IY5wC1UZ5eYjRezk7s5uSv6iBXNx0NqGP7esANHx S0ghsWOUN+u0vYACHlqYhkoh8iVSxaoF9DQSxNjbyyE5XOXzwbACDo5+DJ58A+zGSDZ7 /oeQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c24-v6si3823828pgn.509.2018.06.04.02.06.20; Mon, 04 Jun 2018 02:06:34 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752181AbeFDJEw (ORCPT + 99 others); Mon, 4 Jun 2018 05:04:52 -0400 Received: from gate.crashing.org ([63.228.1.57]:50831 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750868AbeFDJEv (ORCPT ); Mon, 4 Jun 2018 05:04:51 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by gate.crashing.org (8.14.1/8.14.1) with ESMTP id w5494ELh009405; Mon, 4 Jun 2018 04:04:16 -0500 Message-ID: <0a28154deb468669a59c120a90d4aedc1e1e705b.camel@kernel.crashing.org> Subject: Re: [PATCH v2] cpuidle/powernv : Add Description for cpuidle state From: Benjamin Herrenschmidt To: Abhishek Goel , rjw@rjwysocki.net, daniel.lezcano@linaro.org, paulus@samba.org, mpe@ellerman.id.au, linux-pm@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org Cc: stewart@linux.vnet.ibm.com Date: Mon, 04 Jun 2018 19:04:14 +1000 In-Reply-To: <20180604081758.104201-1-huntbag@linux.vnet.ibm.com> References: <20180604081758.104201-1-huntbag@linux.vnet.ibm.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.1 (3.28.1-2.fc28) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2018-06-04 at 13:47 +0530, Abhishek Goel wrote: > + if (of_property_read_string_array(power_mgt, > + "ibm,cpu-idle-state-descs", descs, dt_idle_states) < 0) { > + of_property_read_string_array(power_mgt, > + "ibm,cpu-idle-state-names", descs, dt_idle_states); > + pr_warn("cpuidle-powernv: missing ibm,cpu-idle-state-descs in DT\n" > + "Name will be used for description\n"); > + } > > /* Is this a new property ? I'm not fan of adding yet another of those silly arrays. I would say this is the right time now to switch over to a node per state instead, as we discussed with Vaidy. Additionally, while doing that, we can provide the versioning mechanism I proposed so we can deal with state specific issues and erratas. Cheers, Ben.