Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp4425847imm; Wed, 30 May 2018 05:33:56 -0700 (PDT) X-Google-Smtp-Source: ADUXVKK2x2TtvoysJECXnt66UVuoVKN5NWge6aen7PRtb5aVJbT5ZPszwq1IP91vGRWUJfjwUIRn X-Received: by 2002:a17:902:aa04:: with SMTP id be4-v6mr2708915plb.20.1527683636134; Wed, 30 May 2018 05:33:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527683636; cv=none; d=google.com; s=arc-20160816; b=mHkFPQDZz6ttuTdSqfAzvsyyDKMlz+XzJZZrnURoJ55nLxi+oBY9WRSklpfZwuMro+ 5d8Oao+LICCI6iE40N98lH5H08NbhpUWNqiDyyupDZxO/1DvWBrTKTFEs0JNEeXDHtlg vZ16PclIEBpend/xsUIdVS0EkSPNg8uBln6EDxD7LiIe5KZIVRsDj5tyed1K2kW/TKD2 w6i5oCbY04P0o4o9sg+1G0nYQr9Os/cSEMZFWiZtjFAL+eh99ETtjmO39nYv77un7D4j GGXmPmXW4EoGTrH2v+rpMHpo4m1aOpPh7FtneVKTDEbd0Yzq36bxAUHbYKh4mtHAtR47 VENg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=ouwDGQ/HOIjTCt9yvuzFkZ3uK3szMNoxEc6df6Rirf0=; b=mZvAZH0l6ieRyctqvoXxbtyo7gRiFKfPzPftNkgpJdWOO6gPfHuV+ms+RUbLzwXj2m MUp4zqajjwzS5TD4gtrDGrppp+H6AKkVY5lyw7NgwIfPn+fjCnIFt9lIYFdcJZcj5jrN LiWHaPlDFSUaPG3vuRUzlmUKlfxTeX3c4cHOCtlvEFgxcrVFE9EwhKK9Qxzlh/lvCHi2 RHeyrEL8HJ3QLCPK5Gc2P3uxayLqW0362g3wPzYOibxaLYzrSKzfGQVkLt1xqp+bmmSn scmrD8ntY40NdVIX0F/Y7jhA7NN2Oe8CSq1nnZ6rpZACFDPS+eZIOyxICY7l4QYN5zk4 JtCQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=YFhfPUVz; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x17-v6si35543189pfh.354.2018.05.30.05.33.40; Wed, 30 May 2018 05:33:56 -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; dkim=pass header.i=@kernel.org header.s=default header.b=YFhfPUVz; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753222AbeE3McR (ORCPT + 99 others); Wed, 30 May 2018 08:32:17 -0400 Received: from mail.kernel.org ([198.145.29.99]:54530 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751817AbeE3McP (ORCPT ); Wed, 30 May 2018 08:32:15 -0400 Received: from mail-wr0-f178.google.com (mail-wr0-f178.google.com [209.85.128.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id AB51F208A2; Wed, 30 May 2018 12:32:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1527683535; bh=ouwDGQ/HOIjTCt9yvuzFkZ3uK3szMNoxEc6df6Rirf0=; h=In-Reply-To:References:From:Date:Subject:To:Cc:From; b=YFhfPUVzZZSjei2eoH3DO5hkSI6WuLQVk9x14UM6VxMlQH6+ahethOnbOpiWcqRrE GovB/TdWu5kIiA7dgYN3bCC5mZiPRYzPVmZA7PcgSuS1Cj+U4xL4N6tfmrXGBCPq53 m+vNmb9+ybbMTK0dmSrEvGpBKExTj5FU935D9QBc= Received: by mail-wr0-f178.google.com with SMTP id v13-v6so17668271wrp.13; Wed, 30 May 2018 05:32:14 -0700 (PDT) X-Gm-Message-State: ALKqPwfvFMnSIbUyhKCxzYnuzEnu5q6WBiuBg+XhNl/wVi29szsVBfZa vIblSZ5fJy00eCnk2Iryz55nkXAxIPW4yXrRXUg= X-Received: by 2002:adf:ea0f:: with SMTP id q15-v6mr2172288wrm.9.1527683533136; Wed, 30 May 2018 05:32:13 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:adf:9166:0:0:0:0:0 with HTTP; Wed, 30 May 2018 05:32:12 -0700 (PDT) In-Reply-To: <20180530043806.ksen4xyh3x3x4fqn@vireshk-i7> References: <20180530043806.ksen4xyh3x3x4fqn@vireshk-i7> From: Krzysztof Kozlowski Date: Wed, 30 May 2018 14:32:12 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 07/15] arm: dts: exynos: Add missing cooling device properties for CPUs To: Viresh Kumar Cc: arm@kernel.org, Rob Herring , Mark Rutland , Kukjin Kim , Vincent Guittot , ionela.voinescu@arm.com, Daniel Lezcano , chris.redpath@arm.com, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, "linux-samsung-soc@vger.kernel.org" , linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 30, 2018 at 6:38 AM, Viresh Kumar wrote: > On 29-05-18, 15:18, Krzysztof Kozlowski wrote: >> Thanks for the patch. >> >> In case of Exynos, the booting CPU always has these information in DT >> and the booting CPU cannot be changed (chosen by firmware/hardware >> configuration). > > But can the booting CPU be offlined ? > > If yes, then this is how things are broken right now. > > Build cpufreq driver as module, boot kernel, hotplug out CPU0, insert > cpufreq driver and that will try to find these properties in CPU1. OK, I see the possibility although it is still far away from use cases. You cannot hotplug booting CPU (CPU0) on Exynos kernels. It never worked. Strictly speaking - offlining will work. But bringing it online will likely hang the system. Best regards, Krzysztof