e "Rockchip I2S Device Driver"
- depends on CLKDEV_LOOKUP
+ depends on CLKDEV_LOOKUP && SND_SOC_ROCKCHIP
+ select SND_SOC_GENERIC_DMAENGINE_PCM
help
Say Y or M if you want to add support for I2S driver for
Rockchip I2S device. The device s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21.11.2014 19:58, Mark Brown wrote:
> On Fri, Nov 21, 2014 at 07:35:13PM +0100, Andreas Ruprecht wrote:
>> Currently, CONFIG_SND_SOC_ROCKCHIP_I2S could also be selected
>> without having CONFIG_SND_SOC_ROCKCHIP enabled.
>>
>> As this makes no sens
On Fri, Nov 21, 2014 at 07:35:13PM +0100, Andreas Ruprecht wrote:
> Currently, CONFIG_SND_SOC_ROCKCHIP_I2S could also be selected
> without having CONFIG_SND_SOC_ROCKCHIP enabled.
>
> As this makes no sense (and breaks the build, when the option
> CONFIG_SND_SOC_GENERIC_DMAENGINE_PCM - which would
/Kconfig b/sound/soc/rockchip/Kconfig
index b1fc0ca..74380b4 100644
--- a/sound/soc/rockchip/Kconfig
+++ b/sound/soc/rockchip/Kconfig
@@ -9,7 +9,7 @@ config SND_SOC_ROCKCHIP
config SND_SOC_ROCKCHIP_I2S
tristate "Rockchip I2S Device Driver"
- depends on CLKDEV_LOOKUP
+
This patch add device driver of Richtek RT5033 PMIC. The driver support
switching charger. rt5033 charger provide three charging mode.
Three charging mode are pre charge mode, fast cahrge mode and constant voltage
mode. They are have vary charge rate, charge parameters. The charge parameters
can
This patch adds device driver of Richtek PMIC.
The driver support battery fuel gange. Fuel gauge calculates and determines the
battery state of charge(SOC) according to battery open circuit voltage(OCV).
Also, this driver provides battery average voltage, voltage and bettery present
property.
Cc
This patch add device driver of Richtek RT5033 PMIC. The driver support
switching charger. rt5033 charger provide three charging mode.
Three charging mode are pre charge mode, fast cahrge mode and constant voltage
mode. They are have vary charge rate, charge parameters. The charge parameters
can
This patch adds device driver of Richtek PMIC.
The driver support battery fuel gange. Fuel gauge calculates and determines the
battery state of charge(SOC) according to battery open circuit voltage(OCV).
Also, this driver provides battery average voltage, voltage and bettery present
property.
Cc
This patch add device driver of Richtek RT5033 PMIC. The driver support
switching charger. rt5033 charger provide three charging mode.
Three charging mode are pre charge mode, fast cahrge mode and constant voltage
mode. They are have vary charge rate, charge parameters. The charge parameters
can
This patch adds device driver of Richtek PMIC.
The driver support battery fuel gange. Fuel gauge calculates and determines the
battery state of charge(SOC) according to battery open circuit voltage(OCV).
Also, this driver provides battery average voltage, voltage and bettery present
property.
Cc
On Tue, Nov 11, 2014 at 12:32 PM, Wolfram Sang wrote:
> On Tue, Oct 07, 2014 at 05:06:47PM -0700, Feng Kan wrote:
>> Add SLIMpro I2C device driver on APM X-Gene platform. This I2C
>> device driver use the SLIMpro Mailbox driver to tunnel message to
>> the SLIMpro coproces
On Wed, Nov 12, 2014 at 09:07:59PM +0900, Beomho Seo wrote:
> This patch add device driver of Richtek RT5033 PMIC.
> The driver support multiple regulator like LDO and synchronous Buck.
Applied, thanks.
signature.asc
Description: Digital signature
The AMBA bus driver defines runtime Power Management functions which
disable and unprepare AMBA bus clock. This is problematic for runtime PM
because unpreparing a clock might sleep so it is not interrupt safe.
However some drivers may want to implement runtime PM functions in
interrupt-safe way (
A DPRC (Data Path Resource Container) is an isolation device
that contains a set of DPAA networking devices to be
assigned to an isolation domain (e.g., a virtual machine).
Signed-off-by: J. German Rivera
Signed-off-by: Stuart Yoder
---
Changes addressed in v4:
- Addressed comments from Alex Gra
A DPRC (Data Path Resource Container) is an isolation device
that contains a set of DPAA networking devices to be
assigned to an isolation domain (e.g., a virtual machine).
Signed-off-by: J. German Rivera
Signed-off-by: Stuart Yoder
---
Changes addressed in v4:
- Addressed comments from Alex Gra
On 11/06/2014 07:51 AM, Alexander Graf wrote:
On 04.10.14 15:23, J. German Rivera wrote:
From: "J. German Rivera"
A DPRC (Data Path Resource Container) is an isolation device
that contains a set of DPAA networking devices to be
assigned to an isolation domain (e.g., a virtual machine).
Si
On 12 November 2014 15:32, Krzysztof Kozlowski wrote:
> The AMBA bus driver defines runtime Power Management functions which
> disable and unprepare AMBA bus clock. This is problematic for runtime PM
> because unpreparing a clock might sleep so it is not interrupt safe.
>
> However some drivers ma
The AMBA bus driver defines runtime Power Management functions which
disable and unprepare AMBA bus clock. This is problematic for runtime PM
because unpreparing a clock might sleep so it is not interrupt safe.
However some drivers may want to implement runtime PM functions in
interrupt-safe way (
This patch add device driver of Richtek RT5033 PMIC.
The driver support multiple regulator like LDO and synchronous Buck.
The integrated synchronous buck converter is designed to provide 0.6 A
application with high efficiency. Two LDOs are integrated. One safe LDO is
for 60mA and the other one LDO
This patch adds device driver of Richtek PMIC.
The driver support battery fuel gange. Fuel gauge calculates and determines the
battery state of charge(SOC) according to battery open circuit voltage(OCV).
Also, this driver provides battery average voltage, voltage and bettery present
property.
Cc
This patch add device driver of Richtek RT5033 PMIC. The driver support
switching charger. rt5033 charger provide three charging mode.
Three charging mode are pre charge mode, fast cahrge mode and constant voltage
mode. They are have vary charge rate, charge parameters. The charge parameters
can
Sorry, I will include your e-mail address next revision all patch-set.
On 11/11/2014 04:04 AM, Mark Brown wrote:
> On Mon, Nov 10, 2014 at 04:19:44PM +0900, Beomho Seo wrote:
>> This patch add device driver of Richtek RT5033 PMIC.
>> The driver support multiple regulator like LDO
On Tuesday 07 October 2014 17:06:47 Feng Kan wrote:
> diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
> index 2e45ae3..a03042c 100644
> --- a/drivers/i2c/busses/Kconfig
> +++ b/drivers/i2c/busses/Kconfig
> @@ -1009,6 +1009,15 @@ config I2C_CROS_EC_TUNNEL
> connected the
On Tue, Oct 07, 2014 at 05:06:47PM -0700, Feng Kan wrote:
> Add SLIMpro I2C device driver on APM X-Gene platform. This I2C
> device driver use the SLIMpro Mailbox driver to tunnel message to
> the SLIMpro coprocessor to do the work of accessing I2C components.
>
> Signed-o
On Mon, Nov 10, 2014 at 04:19:44PM +0900, Beomho Seo wrote:
> This patch add device driver of Richtek RT5033 PMIC.
> The driver support multiple regulator like LDO and synchronous Buck.
> The integrated synchronous buck converter is designed to provide 0.6 A
> application with high eff
This patch add device driver of Richtek RT5033 PMIC. The driver support
switching charger. rt5033 charger provide three charging mode.
Three charging mode are pre charge mode, fast cahrge mode and constant voltage
mode. They are have vary charge rate, charge parameters. The charge parameters
can
This patch add device driver of Richtek RT5033 PMIC.
The driver support multiple regulator like LDO and synchronous Buck.
The integrated synchronous buck converter is designed to provide 0.6 A
application with high efficiency. Two LDOs are integrated. One safe LDO is
for 60mA and the other one LDO
This patch adds device driver of Richtek PMIC.
The driver support battery fuel gange. Fuel gauge calculates and determines the
battery state of charge(SOC) according to battery open circuit voltage(OCV).
Also, this driver provides battery average voltage, voltage and bettery present
property.
Cc
On Mon, Oct 6, 2014 at 9:48 AM, German Rivera
wrote:
>>
>> I didn't notice this earlier, but I it was Freescale policy to use
>> EXPORT_SYMBOL() instead of EXPORT_SYMBOL_GPL(). Has that changed?
>>
> Please see change history in the cover letter for this patch series.
So I looked at the change h
ay (see pm_runtime_irq_safe()). In such case the AMBA
> > > bus driver should only disable/enable the clock in runtime suspend and
> > > resume callbacks.
> > >
> > > Detect the device driver behavior during runtime suspend. During runtime
>
On pią, 2014-11-07 at 13:28 +0100, Pavel Machek wrote:
> On Fri 2014-11-07 13:18:03, Krzysztof Kozlowski wrote:
> > On pią, 2014-11-07 at 13:13 +0100, Pavel Machek wrote:
> > > On Wed 2014-11-05 09:42:58, Krzysztof Kozlowski wrote:
> > > > On wto, 2014-11-04 at 21:18 +0100, Pavel Machek wrote:
> >
On Fri 2014-11-07 13:18:03, Krzysztof Kozlowski wrote:
> On pią, 2014-11-07 at 13:13 +0100, Pavel Machek wrote:
> > On Wed 2014-11-05 09:42:58, Krzysztof Kozlowski wrote:
> > > On wto, 2014-11-04 at 21:18 +0100, Pavel Machek wrote:
> > > > On Tue 2014-11-04 13:52:48, Krzysztof Kozlowski wrote:
> >
On pią, 2014-11-07 at 13:13 +0100, Pavel Machek wrote:
> On Wed 2014-11-05 09:42:58, Krzysztof Kozlowski wrote:
> > On wto, 2014-11-04 at 21:18 +0100, Pavel Machek wrote:
> > > On Tue 2014-11-04 13:52:48, Krzysztof Kozlowski wrote:
> > > > The AMBA bus driver defines runtime Power Management functi
On Wed 2014-11-05 09:42:58, Krzysztof Kozlowski wrote:
> On wto, 2014-11-04 at 21:18 +0100, Pavel Machek wrote:
> > On Tue 2014-11-04 13:52:48, Krzysztof Kozlowski wrote:
> > > The AMBA bus driver defines runtime Power Management functions which
> > > disable and unprepare AMBA bus clock. This is p
On Fri, Nov 07, 2014 at 11:52:04AM +0900, Beomho Seo wrote:
> +static int rt5033_regulator_dt_parse_data(struct device *dev)
> +{
> + int ret;
> + struct device_node *np;
> +
> + np = of_get_child_by_name(dev->parent->of_node, "regulators");
> + if (!np) {
> + dev_err(
e the clock in runtime suspend and
> > resume callbacks.
> >
> > Detect the device driver behavior during runtime suspend. During runtime
> > resume deal with clocks according to stored value.
> >
> > Signed-off-by: Krzysztof Kozlowski
> > ---
> > driv
This patch adds device driver of Richtek PMIC.
The driver support battery fuel gange. Fuel gauge calculates and determines the
battery state of charge(SOC) according to battery open circuit voltage(OCV).
Also, this driver provides battery average voltage, voltage and bettery present
property.
Cc
This patch add device driver of Richtek RT5033 PMIC.
The driver support multiple regulator like LDO and synchronous Buck.
The integrated synchronous buck converter is designed to provide 0.6 A
application with high efficiency. Two LDOs are integrated. One safe LDO is
for 60mA and the other one LDO
This patch add device driver of Richtek RT5033 PMIC. The driver support
switching charger. rt5033 charger provide three charging mode.
Three charging mode are pre charge mode, fast cahrge mode and constant voltage
mode. They are have vary charge rate, charge parameters. The charge parameters
can
rupt safe.
>
> However some drivers may want to implement runtime PM functions in
> interrupt-safe way (see pm_runtime_irq_safe()). In such case the AMBA
> bus driver should only disable/enable the clock in runtime suspend and
> resume callbacks.
>
> Detect the device driver behavior
On 04.10.14 15:23, J. German Rivera wrote:
> From: "J. German Rivera"
>
> A DPRC (Data Path Resource Container) is an isolation device
> that contains a set of DPAA networking devices to be
> assigned to an isolation domain (e.g., a virtual machine).
>
> Signed-off-by: J. German Rivera
> Sign
er some drivers may want to implement runtime PM functions in
> interrupt-safe way (see pm_runtime_irq_safe()). In such case the AMBA
> bus driver should only disable/enable the clock in runtime suspend and
> resume callbacks.
>
> Detect the device driver behavior during runtime suspend
(see pm_runtime_irq_safe()). In such case the AMBA
bus driver should only disable/enable the clock in runtime suspend and
resume callbacks.
Detect the device driver behavior during runtime suspend. During runtime
resume deal with clocks according to stored value.
Signed-off-by: Krzysztof Kozlowski
and
> > resume callbacks.
> >
> > Detect the device driver behavior during runtime suspend. During runtime
> > resume deal with clocks according to stored value.
> >
> > Signed-off-by: Krzysztof Kozlowski
> > ---
> > drivers/amba/bus.c
On wto, 2014-11-04 at 21:18 +0100, Pavel Machek wrote:
> On Tue 2014-11-04 13:52:48, Krzysztof Kozlowski wrote:
> > The AMBA bus driver defines runtime Power Management functions which
> > disable and unprepare AMBA bus clock. This is problematic for runtime PM
> > because unpreparing a clock might
On Tue 2014-11-04 13:52:48, Krzysztof Kozlowski wrote:
> The AMBA bus driver defines runtime Power Management functions which
> disable and unprepare AMBA bus clock. This is problematic for runtime PM
> because unpreparing a clock might sleep so it is not interrupt safe.
>
> However some drivers m
er some drivers may want to implement runtime PM functions in
> interrupt-safe way (see pm_runtime_irq_safe()). In such case the AMBA
> bus driver should only disable/enable the clock in runtime suspend and
> resume callbacks.
>
> Detect the device driver behavior during runtime suspend
Russell King - ARM Linux wrote:
>> >>
>> >> > That makes it pretty horrid from the point of view of having bus
>> >> > management code, because we now have the management of the bus clock
>> >> > split between the bus layer and the device drive
it pretty horrid from the point of view of having bus
> >> > management code, because we now have the management of the bus clock
> >> > split between the bus layer and the device driver.
> >> >
> >> > This is /really/ a problem for runtime PM.
(see pm_runtime_irq_safe()). In such case the AMBA
bus driver should only disable/enable the clock in runtime suspend and
resume callbacks.
Detect the device driver behavior during runtime suspend. During runtime
resume deal with clocks according to stored value.
Signed-off-by: Krzysztof Kozlowski
ecause we now have the management of the bus clock
>> > split between the bus layer and the device driver.
>> >
>> > This is /really/ a problem for runtime PM. Runtime PM permits there
>> > to be a bus layer involved - and runtime PM can also be coupled up
&
agement code, because we now have the management of the bus clock
> > > split between the bus layer and the device driver.
> > >
> > > This is /really/ a problem for runtime PM. Runtime PM permits there
> > > to be a bus layer involved - and runtime PM can als
On pon, 2014-11-03 at 15:44 +, Russell King - ARM Linux wrote:
> On Mon, Nov 03, 2014 at 10:41:02AM -0500, Alan Stern wrote:
> > Bear in mind, however, that once the irq_safe flag has been set, the
> > runtime PM core offers no way to turn it off again.
>
> Ah, I thought it did permit it to c
en the bus layer and the device driver.
> >
> > This is /really/ a problem for runtime PM. Runtime PM permits there
> > to be a bus layer involved - and runtime PM can also be coupled up
> > to PM domains as well. For all this stuff, the context which the
> > callba
Russell King - ARM Linux writes:
[...]
> Would another possible solution be to remember the irq-safeness in the
> suspend handler, and use that in the resume handler? Resume should
> /always/ undo what the suspend handler previously did wrt clk API stuff.
This seems more reasonable to me.
Cur
On Mon, Nov 03, 2014 at 10:41:02AM -0500, Alan Stern wrote:
> Bear in mind, however, that once the irq_safe flag has been set, the
> runtime PM core offers no way to turn it off again.
Ah, I thought it did permit it to change both ways. In that case, we
don't need to validate that it doesn't cha
On Mon, 3 Nov 2014, Russell King - ARM Linux wrote:
> That makes it pretty horrid from the point of view of having bus
> management code, because we now have the management of the bus clock
> split between the bus layer and the device driver.
>
> This is /really/ a problem
out removing runtime PM callbacks from amba/bus.c
> completely and moving this to child drivers. This way runtime PM would
> be obvious in each driver case.
That makes it pretty horrid from the point of view of having bus
management code, because we now have the management of the bus clock
spli
On sob, 2014-11-01 at 01:01 +, Russell King - ARM Linux wrote:
> On Sat, Nov 01, 2014 at 12:55:14AM +, Russell King - ARM Linux wrote:
> > On Sat, Nov 01, 2014 at 01:45:47AM +0100, Rafael J. Wysocki wrote:
> > > On Monday, October 20, 2014 11:04:46 AM Krzysztof Kozlowski wrote:
> > > > @@ -
On Sat, Nov 01, 2014 at 12:55:14AM +, Russell King - ARM Linux wrote:
> On Sat, Nov 01, 2014 at 01:45:47AM +0100, Rafael J. Wysocki wrote:
> > On Monday, October 20, 2014 11:04:46 AM Krzysztof Kozlowski wrote:
> > > @@ -198,8 +217,10 @@ static int amba_probe(struct device *dev)
> > >
On Sat, Nov 01, 2014 at 01:45:47AM +0100, Rafael J. Wysocki wrote:
> On Monday, October 20, 2014 11:04:46 AM Krzysztof Kozlowski wrote:
> > @@ -198,8 +217,10 @@ static int amba_probe(struct device *dev)
> > pm_runtime_enable(dev);
> >
> > ret = pcdrv->probe(pcdev, id);
> >
;
> However some drivers may want to implement runtime PM functions in
> interrupt-safe way (see pm_runtime_irq_safe()). In such case the AMBA
> bus driver should only disable/enable the clock in runtime suspend and
> resume callbacks.
>
> Detect the device driver behavior after
(see pm_runtime_irq_safe()). In such case the AMBA
bus driver should only disable/enable the clock in runtime suspend and
resume callbacks.
Detect the device driver behavior after calling its probe function and
store it. During runtime suspend/resume deal with clocks according to
stored value
er some drivers may want to implement runtime PM functions in
> interrupt-safe way (see pm_runtime_irq_safe()). In such case the AMBA
> bus driver should only disable/enable the clock in runtime suspend and
> resume callbacks.
>
> Detect the device driver behavior after calling its
cxl mm contexts.
Patch12: Add cxl specific support that needs to be built in to the
kernel (can't be a module).
Patches 13-15: Add the majority of the device driver and API header.
Patch16: Documentation.
The documentation in this last patch gives an overvie
Add SLIMpro I2C device driver on APM X-Gene platform. This I2C
device driver use the SLIMpro Mailbox driver to tunnel message to
the SLIMpro coprocessor to do the work of accessing I2C components.
Signed-off-by: Feng Kan
Signed-off-by: Hieu Le
---
drivers/i2c/busses/Kconfig | 9
Add proxy I2C device driver on APM X-Gene platform.
Signed-off-by: Feng Kan
Signed-off-by: Hieu Le
---
arch/arm64/boot/dts/apm-storm.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/apm-storm.dtsi
b/arch/arm64/boot/dts/apm-storm.dtsi
index 249f025..09daf4c
ecific support that needs to be built in to the
kernel (can't be a module).
Patches 13-15: Add the majority of the device driver and API header.
Patch16: Documentation.
The documentation in this last patch gives an overview of the hardware
architecture as well as the users
On 10/05/2014 09:53 AM, Timur Tabi wrote:
On Sat, Oct 4, 2014 at 8:23 AM, J. German Rivera
wrote:
+EXPORT_SYMBOL_GPL(dprc_scan_objects);
I didn't notice this earlier, but I it was Freescale policy to use
EXPORT_SYMBOL() instead of EXPORT_SYMBOL_GPL(). Has that changed?
Please see change h
On Sat, Oct 4, 2014 at 8:23 AM, J. German Rivera
wrote:
> +EXPORT_SYMBOL_GPL(dprc_scan_objects);
I didn't notice this earlier, but I it was Freescale policy to use
EXPORT_SYMBOL() instead of EXPORT_SYMBOL_GPL(). Has that changed?
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
T
From: "J. German Rivera"
A DPRC (Data Path Resource Container) is an isolation device
that contains a set of DPAA networking devices to be
assigned to an isolation domain (e.g., a virtual machine).
Signed-off-by: J. German Rivera
Signed-off-by: Stuart Yoder
---
Changes in v3:
- Addressed comme
German Rivera wrote:
I know that this is not necessary from the point of view of C boolean
semantics, but doing explicit comparison improves readability IMHO.
I guess we'll have to agree to disagree. I think it makes the code less
readable.
Anyway, this is subjective and largely a matter
On 09/30/2014 09:19 PM, Timur Tabi wrote:
On Fri, Sep 19, 2014 at 5:49 PM, J. German Rivera
wrote:
+static int __fsl_mc_device_remove(struct device *dev, void *data)
+{
+ WARN_ON(dev == NULL);
+ WARN_ON(data != NULL);
I see a lot of direct comparisons with NULL and 0. You don't
Scott Wood wrote:
> >+ if (num_child_objects_in_mc != 0) {
>
>Like here. Just do "if (num_child_objects_in_mc) {"
This seems to be a place that is testing for zero as a value rather than
as a stand-in for NULL, so I'd argue it's better style to leave it as
is.
But in this case, zero
On Tue, 2014-09-30 at 21:19 -0500, Timur Tabi wrote:
> On Fri, Sep 19, 2014 at 5:49 PM, J. German Rivera
> wrote:
> > +/**
> > + * dprc_remove_devices - Removes devices for objects removed from a DPRC
> > + *
> > + * @mc_bus_dev: pointer to the fsl-mc device that represents a DPRC object
> > + * @
On Fri, Sep 19, 2014 at 5:49 PM, J. German Rivera
wrote:
> +static int __fsl_mc_device_remove(struct device *dev, void *data)
> +{
> + WARN_ON(dev == NULL);
> + WARN_ON(data != NULL);
I see a lot of direct comparisons with NULL and 0. You don't need to
be so explicit:
WARN_ON(!dev)
be built in to the
kernel (can't be a module).
Patches 14-16: Add the majority of the device driver and API header.
Patch17: Documentation.
The documentation in this last patch gives an overview of the hardware
architecture as well as the userspace API.
The cxl driver has a user-sp
Signed-off-by: Rajat Jain
Signed-off-by: Rajat Jain
Signed-off-by: Guenter Roeck
---
MAINTAINERS |7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 3705430..0ef7a92 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7003,6 +7003,13 @@ S: Maintained
(see pm_runtime_irq_safe()). In such case the AMBA
bus driver should only disable/enable the clock in runtime suspend and
resume callbacks.
Detect the device driver behavior after calling its probe function and
store it. During runtime suspend/resume deal with clocks according to
stored value
(see pm_runtime_irq_safe()). In such case the AMBA
bus driver should only disable/enable the clock in runtime suspend and
resume callbacks.
Detect the device driver behavior after calling its probe function and
store it. During runtime suspend/resume deal with clocks according to
stored value
From: "J. German Rivera"
A DPRC (Data Path Resource Container) is an isolation device
that contains a set of DPAA networking devices to be
assigned to an isolation domain (e.g., a virtual machine).
Signed-off-by: J. German Rivera
Signed-off-by: Stuart Yoder
---
Changes in v2:
- Addressed comme
werpc needed by cxl.
Patches 10: Add call backs needed for invalidating cxl mm contexts.
Patch11: Add cxl specific support that needs to be built in to the
kernel (can't be a module).
Patches 12-15: Add the majority of the device driver and API header.
P
untime_irq_safe()). In such case the AMBA
>> > bus driver should only disable/enable the clock in runtime suspend and
>> > resume callbacks.
>> >
>> > Detect the device driver behavior after calling its probe function and
>> > store it. During ru
lock in runtime suspend and
> > resume callbacks.
> >
> > Detect the device driver behavior after calling its probe function and
> > store it. During runtime suspend/resume deal with clocks according to
> > stored value.
> >
> > Signed-off-by: Krzysztof Kozlowski
&
er some drivers may want to implement runtime PM functions in
> interrupt-safe way (see pm_runtime_irq_safe()). In such case the AMBA
> bus driver should only disable/enable the clock in runtime suspend and
> resume callbacks.
>
> Detect the device driver behavior after calling its
(see pm_runtime_irq_safe()). In such case the AMBA
bus driver should only disable/enable the clock in runtime suspend and
resume callbacks.
Detect the device driver behavior after calling its probe function and
store it. During runtime suspend/resume deal with clocks according to
stored value
On wto, 2014-09-16 at 10:20 +0100, Russell King - ARM Linux wrote:
> On Tue, Sep 16, 2014 at 10:51:33AM +0200, Krzysztof Kozlowski wrote:
> > @@ -191,8 +210,11 @@ static int amba_probe(struct device *dev)
> > pm_runtime_enable(dev);
> >
> > ret = pcdrv->probe(pcdev, id);
>
On Tue, Sep 16, 2014 at 10:51:33AM +0200, Krzysztof Kozlowski wrote:
> @@ -191,8 +210,11 @@ static int amba_probe(struct device *dev)
> pm_runtime_enable(dev);
>
> ret = pcdrv->probe(pcdev, id);
> - if (ret == 0)
> + if (ret == 0) {
> +
(see pm_runtime_irq_safe()). In such case the AMBA
bus driver should not unprepare/prepare the clock in runtime suspend and
resume callbacks.
Detect the device driver behavior after calling its probe function and
store it. During runtime suspend/resume deal with clocks according to
stored value
(see pm_runtime_irq_safe()). In such case the AMBA
bus driver should not unprepare/prepare the clock in runtime suspend and
resume callbacks.
Detect the device driver behavior after calling its probe function and
store it. During runtime suspend/resume deal with clocks according to
stored value
From: "J. German Rivera"
A DPRC (Data Path Resource Container) is an isolation device
that contains a set of DPAA networking devices to be
assigned to an isolation domain (e.g., a virtual machine).
Signed-off-by: J. German Rivera
Signed-off-by: Stuart Yoder
---
Changes in RFC v4:
- Fixed param
From: "J. German Rivera"
A DPRC (Data Path Resource Container) is an isolation device
that contains a set of DPAA networking devices to be
assigned to an isolation domain (e.g., a virtual machine).
Signed-off-by: J. German Rivera
Signed-off-by: Stuart Yoder
---
Changes in v4:
- Fixed parameter
On Wed, Sep 03, 2014 at 05:50:50PM +0530, Anand Moon wrote:
> Check was added to check dma address should not be 0x
> before unmap the dma.
> v1: remove unnecessary of bdp->cbd_bufaddr as suggested
> by Andy
I still have a whole pile of commits, one of them cleans up the handli
-API: device driver tries to free DMA
>memory it has not allocated
>
>Changes fix below warning:
>
>[ 167.331417] [ cut here ] [ 167.331456] WARNING:
>CPU: 0 PID: 1887 at lib/dma-debug.c:1080 check_unmap+0x7e4/0xb90()
>[ 167.331469] fec 2188000.ethernet: DMA
From: "J. German Rivera"
A DPRC (Data Path Resource Container) is an isolation device
that contains a set of DPAA networking devices to be
assigned to an isolation domain (e.g., a virtual machine).
Signed-off-by: J. German Rivera
---
drivers/bus/fsl-mc/Makefile |3 +-
drivers/bus/fsl-
From: "J. German Rivera"
A DPRC (Data Path Resource Container) is an isolation device
that contains a set of DPAA networking devices to be
assigned to an isolation domain (e.g., a virtual machine).
Signed-off-by: J. German Rivera
---
drivers/bus/fsl-mc/Makefile |3 +-
drivers/bus/fsl-
From: "J. German Rivera"
A DPRC (Data Path Resource Container) is an isolation device
that contains a set of DPAA networking devices to be
assigned to an isolation domain (e.g., a virtual machine).
Signed-off-by: J. German Rivera
---
drivers/bus/fsl-mc/Makefile |3 +-
drivers/bus/fsl-
From: "J. German Rivera"
A DPRC (Data Path Resource Container) is an isolation device
that contains a set of DPAA networking devices to be
assigned to an isolation domain (e.g., a virtual machine).
Signed-off-by: J. German Rivera
---
drivers/bus/fsl-mc/Makefile |3 +-
drivers/bus/fsl-
On Wed, Aug 13, 2014 at 03:10:44PM -0700, Dmitry Torokhov wrote:
> On Thu, Aug 14, 2014 at 06:02:23AM +0800, Greg KH wrote:
> > On Wed, Aug 13, 2014 at 10:20:33AM -0700, Dmitry Torokhov wrote:
> > > Hi Greg,
> > >
> > > On Sat, Feb 08, 2014 at 10:27:29AM -0800, Greg KH wrote:
> >
> > February? T
On Thu, Aug 14, 2014 at 06:02:23AM +0800, Greg KH wrote:
> On Wed, Aug 13, 2014 at 10:20:33AM -0700, Dmitry Torokhov wrote:
> > Hi Greg,
> >
> > On Sat, Feb 08, 2014 at 10:27:29AM -0800, Greg KH wrote:
>
> February? That's an old thread to dig up...
Well, yes ;)
>
>
> > > On Sat, Feb 08, 201
901 - 1000 of 1654 matches
Mail list logo
