From: Viresh Kumar <viresh.kumar@linaro.org> To: Olof Johansson <olof@lixom.net> Cc: rjw@sisk.pl, cpufreq@vger.kernel.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, robin.randhawa@arm.com, Steve.Bannister@arm.com, Liviu.Dudau@arm.com, charles.garcia-tobin@arm.com, linaro-kernel@lists.linaro.org, mark.hambleton@broadcom.com, linux-arm-kernel@lists.infradead.org, Sudeep KarkadaNagesha <sudeep.karkadanagesha@arm.com>, Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com> Subject: Re: [PATCH] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue Date: Thu, 7 Mar 2013 10:29:54 +0800 [thread overview] Message-ID: <CAKohpo=sF3nEnA4Jgr3gx-vxJTeqp6P1JmoiU=tN-bS6VJQ4Fw@mail.gmail.com> (raw) In-Reply-To: <CAOesGMiOBxEHVgkr=K_4JVQ6+0Swy1uRmHaS8QwRxTJKs3J2Ow@mail.gmail.com> On 7 March 2013 09:50, Olof Johansson <olof@lixom.net> wrote: > On Wed, Mar 6, 2013 at 5:46 PM, Olof Johansson <olof@lixom.net> wrote: > >> This binding makes no sense to me. It needs to be substantially better >> documented, not just a couple of sentences that people that understand >> bit.LITTLE thoroughly can make sense of. >> >> It also duplicates the cpu binding. I suspect this should instead be done >> through additions of the cpu bindings instead of duplication. So this needs to >> be substantially reworked. Actually, i wasn't getting in new bindings for cpu/cluster for big LITTLE but was just trying to get bindings for getting freq-table for cpufreq driver. Lorenzo (cc'd) actually has a patch for getting the bindings in and he is looking to send them soon. I know these can change after some review and the plan was i will fix cpufreq bindings again once that patch is in. We don't have any mainlined hardware for it for now and so it wouldn't break anything. > Also, _ALWAYS_ cc devicetree-discuss on new bindings. get_maintainer > tells you to do so. I knew it and i messed up with it. Will surely take care of it next time.
WARNING: multiple messages have this Message-ID (diff)
From: viresh.kumar@linaro.org (Viresh Kumar) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue Date: Thu, 7 Mar 2013 10:29:54 +0800 [thread overview] Message-ID: <CAKohpo=sF3nEnA4Jgr3gx-vxJTeqp6P1JmoiU=tN-bS6VJQ4Fw@mail.gmail.com> (raw) In-Reply-To: <CAOesGMiOBxEHVgkr=K_4JVQ6+0Swy1uRmHaS8QwRxTJKs3J2Ow@mail.gmail.com> On 7 March 2013 09:50, Olof Johansson <olof@lixom.net> wrote: > On Wed, Mar 6, 2013 at 5:46 PM, Olof Johansson <olof@lixom.net> wrote: > >> This binding makes no sense to me. It needs to be substantially better >> documented, not just a couple of sentences that people that understand >> bit.LITTLE thoroughly can make sense of. >> >> It also duplicates the cpu binding. I suspect this should instead be done >> through additions of the cpu bindings instead of duplication. So this needs to >> be substantially reworked. Actually, i wasn't getting in new bindings for cpu/cluster for big LITTLE but was just trying to get bindings for getting freq-table for cpufreq driver. Lorenzo (cc'd) actually has a patch for getting the bindings in and he is looking to send them soon. I know these can change after some review and the plan was i will fix cpufreq bindings again once that patch is in. We don't have any mainlined hardware for it for now and so it wouldn't break anything. > Also, _ALWAYS_ cc devicetree-discuss on new bindings. get_maintainer > tells you to do so. I knew it and i messed up with it. Will surely take care of it next time.
next prev parent reply other threads:[~2013-03-07 2:29 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-05 4:52 [PATCH] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue Viresh Kumar 2013-03-05 4:52 ` Viresh Kumar 2013-03-05 10:52 ` Russell King - ARM Linux 2013-03-05 10:52 ` Russell King - ARM Linux 2013-03-05 16:38 ` Viresh Kumar 2013-03-05 16:38 ` Viresh Kumar 2013-03-06 17:25 ` Russell King - ARM Linux 2013-03-06 17:25 ` Russell King - ARM Linux 2013-03-06 23:09 ` Viresh Kumar 2013-03-06 23:09 ` Viresh Kumar 2013-03-07 0:32 ` Viresh Kumar 2013-03-07 0:32 ` Viresh Kumar 2013-03-07 0:49 ` Harvey Harrison 2013-03-07 0:49 ` Harvey Harrison 2013-03-07 1:46 ` Viresh Kumar 2013-03-07 1:46 ` Viresh Kumar 2013-03-07 0:51 ` Russell King - ARM Linux 2013-03-07 0:51 ` Russell King - ARM Linux 2013-03-07 2:03 ` Viresh Kumar 2013-03-07 2:03 ` Viresh Kumar 2013-03-07 11:49 ` Russell King - ARM Linux 2013-03-07 11:49 ` Russell King - ARM Linux 2013-03-07 17:04 ` Viresh Kumar 2013-03-07 17:04 ` Viresh Kumar 2013-03-07 1:46 ` Olof Johansson 2013-03-07 1:46 ` Olof Johansson 2013-03-07 1:50 ` Olof Johansson 2013-03-07 1:50 ` Olof Johansson 2013-03-07 2:29 ` Viresh Kumar [this message] 2013-03-07 2:29 ` Viresh Kumar
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAKohpo=sF3nEnA4Jgr3gx-vxJTeqp6P1JmoiU=tN-bS6VJQ4Fw@mail.gmail.com' \ --to=viresh.kumar@linaro.org \ --cc=Liviu.Dudau@arm.com \ --cc=Lorenzo.Pieralisi@arm.com \ --cc=Steve.Bannister@arm.com \ --cc=charles.garcia-tobin@arm.com \ --cc=cpufreq@vger.kernel.org \ --cc=linaro-kernel@lists.linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pm@vger.kernel.org \ --cc=mark.hambleton@broadcom.com \ --cc=olof@lixom.net \ --cc=rjw@sisk.pl \ --cc=robin.randhawa@arm.com \ --cc=sudeep.karkadanagesha@arm.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.