From: Viresh Kumar <viresh.kumar@linaro.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
Mark Brown <broonie@kernel.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Rajendra Nayak <rnayak@codeaurora.org>,
Shiraz Hashim <shashim@codeaurora.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, robdclark@gmail.com
Subject: Re: [PATCH V3 1/8] drivers: Add boot constraints core
Date: Tue, 29 Aug 2017 11:52:17 +0200 [thread overview]
Message-ID: <20170829095217.GA3101@ubuntu> (raw)
In-Reply-To: <20170829063923.GD12198@kroah.com>
On 29-08-17, 08:39, Greg Kroah-Hartman wrote:
> How is this information getting to the kernel from the bootloader? I
> didn't see where that happened, just a single example driver that
> somehow "knew" what had to happen, which seems odd...
I tried to do it with DT earlier, but we couldn't reach to an agreement on what
bindings to add and so this series started doing things the old way. The kernel
would have platform specific drivers, which would exactly know what constraints
to set and we wouldn't need the bootloaders to pass anything for now.
> This is a lot of new code for no users,
I agree and so added the patch 8/8 to show a real user. I will convert that to a
patch going forward, which can be merged along with this series.
> I would like to see at least 3
> real drivers that are using it before we merge it, as then you have a
> chance of getting the user/kernel api correct.
Hmm, so I am quite sure that this is a fairly generic problem to solve,
specifically for all the handheld devices. I can get code for few of the Qcom
SoCs but they may end up using the same platform driver. Not sure if I can get
code for multiple SoC families in the beginning.
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 1/8] drivers: Add boot constraints core
Date: Tue, 29 Aug 2017 11:52:17 +0200 [thread overview]
Message-ID: <20170829095217.GA3101@ubuntu> (raw)
In-Reply-To: <20170829063923.GD12198@kroah.com>
On 29-08-17, 08:39, Greg Kroah-Hartman wrote:
> How is this information getting to the kernel from the bootloader? I
> didn't see where that happened, just a single example driver that
> somehow "knew" what had to happen, which seems odd...
I tried to do it with DT earlier, but we couldn't reach to an agreement on what
bindings to add and so this series started doing things the old way. The kernel
would have platform specific drivers, which would exactly know what constraints
to set and we wouldn't need the bootloaders to pass anything for now.
> This is a lot of new code for no users,
I agree and so added the patch 8/8 to show a real user. I will convert that to a
patch going forward, which can be merged along with this series.
> I would like to see at least 3
> real drivers that are using it before we merge it, as then you have a
> chance of getting the user/kernel api correct.
Hmm, so I am quite sure that this is a fairly generic problem to solve,
specifically for all the handheld devices. I can get code for few of the Qcom
SoCs but they may end up using the same platform driver. Not sure if I can get
code for multiple SoC families in the beginning.
--
viresh
next prev parent reply other threads:[~2017-08-29 9:52 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 9:23 [PATCH V3 0/8] drivers: Boot Constraints core Viresh Kumar
2017-08-01 9:23 ` Viresh Kumar
2017-08-01 9:23 ` [PATCH V3 1/8] drivers: Add boot constraints core Viresh Kumar
2017-08-01 9:23 ` Viresh Kumar
2017-08-29 6:39 ` Greg Kroah-Hartman
2017-08-29 6:39 ` Greg Kroah-Hartman
2017-08-29 9:52 ` Viresh Kumar [this message]
2017-08-29 9:52 ` Viresh Kumar
2017-08-29 12:03 ` Greg Kroah-Hartman
2017-08-29 12:03 ` Greg Kroah-Hartman
2017-09-04 9:15 ` Viresh Kumar
2017-09-04 9:15 ` Viresh Kumar
2017-09-04 9:38 ` Greg Kroah-Hartman
2017-09-04 9:38 ` Greg Kroah-Hartman
2017-09-19 22:46 ` Viresh Kumar
2017-09-19 22:46 ` Viresh Kumar
2017-08-01 9:23 ` [PATCH V3 2/8] drivers: boot_constraint: Add boot_constraints_disable kernel parameter Viresh Kumar
2017-08-01 9:23 ` Viresh Kumar
2017-08-29 6:37 ` Greg Kroah-Hartman
2017-08-29 6:37 ` Greg Kroah-Hartman
2017-08-29 6:48 ` Jani Nikula
2017-08-29 6:48 ` Jani Nikula
2017-08-29 10:02 ` Viresh Kumar
2017-08-29 10:02 ` Viresh Kumar
2017-08-29 11:56 ` Greg Kroah-Hartman
2017-08-29 11:56 ` Greg Kroah-Hartman
2017-08-01 9:23 ` [PATCH V3 3/8] drivers: boot_constraint: Add support for supply constraints Viresh Kumar
2017-08-01 9:23 ` Viresh Kumar
2017-08-01 9:23 ` [PATCH V3 4/8] drivers: boot_constraint: Add support for clk constraints Viresh Kumar
2017-08-01 9:23 ` Viresh Kumar
2017-08-01 9:23 ` [PATCH V3 5/8] drivers: boot_constraint: Add support for PM constraints Viresh Kumar
2017-08-01 9:23 ` Viresh Kumar
2017-08-01 9:23 ` [PATCH V3 6/8] drivers: boot_constraint: Add debugfs support Viresh Kumar
2017-08-01 9:23 ` Viresh Kumar
2017-08-29 6:36 ` Greg Kroah-Hartman
2017-08-29 6:36 ` Greg Kroah-Hartman
2017-08-29 10:04 ` Viresh Kumar
2017-08-29 10:04 ` Viresh Kumar
2017-08-01 9:23 ` [PATCH V3 7/8] drivers: boot_constraint: Manage deferrable constraints Viresh Kumar
2017-08-01 9:23 ` Viresh Kumar
2017-08-01 9:23 ` [PATCH V3 8/8] drivers: boot_constraint: Add Qualcomm display controller constraints Viresh Kumar
2017-08-01 9:23 ` Viresh Kumar
2017-09-04 16:25 ` Pavel Machek
2017-09-04 16:25 ` Pavel Machek
2017-09-19 22:40 ` Viresh Kumar
2017-09-19 22:40 ` 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=20170829095217.GA3101@ubuntu \
--to=viresh.kumar@linaro.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rnayak@codeaurora.org \
--cc=robdclark@gmail.com \
--cc=sboyd@codeaurora.org \
--cc=shashim@codeaurora.org \
--cc=vincent.guittot@linaro.org \
/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: link
Be 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.