On Sat, Aug 16, 2014 at 09:53:50AM +0300, Mika Westerberg wrote:
> The recent publication of the ACPI 5.1 specification [1] adds a reserved name
> for Device Specific Data (_DSD, Section 6.2.5). This mechanism allows for
> passing arbitrary hardware description data to the OS. The exact format of t
From: Max Eliaser
Make use of device property API in this driver so that both OF and ACPI
based system can use the same driver.
Signed-off-by: Max Eliaser
Signed-off-by: Aaron Lu
Reviewed-by: Darren Hart
Signed-off-by: Mika Westerberg
---
drivers/leds/leds-gpio.c | 130 +
From: Aaron Lu
Make use of device property API in this driver so that both OF based
system and ACPI based system can use this driver.
The driver isn't converted to descriptor based gpio API due to there are
a lot of existing users of struct gpio_keys_button that expects the gpio
integer field. T
From: "Rafael J. Wysocki"
Add a uniform interface by which device drivers can request device
properties from the platform firmware by providing a property name
and the corresponding data type.
Three general helper functions, device_property_get(),
device_property_read() and device_property_read_
This document describes the data format and interfaces of ACPI device
specific properties.
Signed-off-by: Mika Westerberg
Signed-off-by: Darren Hart
---
Documentation/acpi/properties.txt | 359 ++
1 file changed, 359 insertions(+)
create mode 100644 Document
If an MFD device is backed by ACPI namespace, we should allow subdevice
drivers to access their corresponding ACPI companion devices through normal
means (e.g using ACPI_COMPANION()).
This patch adds such support to the MFD core. If the MFD parent device
doesn't specify any ACPI _HID/_CID for the
From: Aaron Lu
With the unified device properties interface in place, add device tree support.
By adding the dev_prop_ops for of_node devices, drivers can access properties
from ACPI or Device Tree in a generic way.
Signed-off-by: Aaron Lu
Reviewed-by: Darren Hart
Signed-off-by: Mika Westerber
[ Resending with fewer people in CC list. For some reason the series never
reached attented mailing lists. ]
The recent publication of the ACPI 5.1 specification [1] adds a reserved name
for Device Specific Data (_DSD, Section 6.2.5). This mechanism allows for
passing arbitrary hardware descript
Device Tree is used in many embedded systems to describe the system
configuration to the OS. It supports attaching properties or name-value
pairs to the devices it describe. With these properties one can pass
additional information to the drivers that would not be available
otherwise.
ACPI is anot
From: Aaron Lu
Add a new API to get the GPIO's description pointer and its flags for
both OF based system and ACPI based system. This is useful in drivers
that do not need to care about the underlying firmware interface.
Signed-off-by: Aaron Lu
Signed-off-by: Max Eliaser
Signed-off-by: Darren
This is actually a single device with two sets of identical registers,
which just happen to start from a different offset. Instead of having
separate GPIO chips created we consolidate them to be single GPIO chip.
In addition having a single GPIO chip allows us to handle ACPI GPIO
translation in th
This patch is used to remove the selftests dependency on
OF_DYNAMIC config flag. Now, it selectively builds
only the functions required by the selftests.
Tested with and without OF_DYNAMIC enabled.
Signed-off-by: Gaurav Minocha
---
drivers/of/Kconfig |1 -
drivers/of/Makefile |2 +-
RK808 PMIC is a MFD with RTC as one of the device. Adding RTC driver
for supporting RTC device present inside RK808 PMIC.
Signed-off-by: Chris Zhong
---
drivers/rtc/Kconfig | 11 +
drivers/rtc/Makefile|1 +
drivers/rtc/rtc-rk808.c | 564
The regulator module consists of 4 DCDCs, 8 LDOs and 2 switches.
The output voltages are configurable and are meant to supply power
to the main processor and other components
Signed-off-by: Chris Zhong
---
drivers/regulator/Kconfig | 10 +
drivers/regulator/Makefile |1 +
The RK808 chip is a power management IC for multimedia and handheld
devices. It contains the following components:
- Regulators
- RTC
The rk808 core driver is registered as a platform driver and provides
communication through I2C with the host device for the different
components.
Signed-off-by:
rk808.txt: Add device tree bindings for rockchip's rk808 pmic.
Signed-off-by: Chris Zhong
---
Documentation/devicetree/bindings/mfd/rk808.txt | 128 +++
1 file changed, 128 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mfd/rk808.txt
diff --git a/Docume
This is the initial version of the RK808 PMIC. This is a power management IC
for multimedia products.
It provides regulators that are able to supply power to processor cores
and other components. The chip provides other modules including RTC, Clockout
Chris Zhong (4):
MFD: Add rk808 device tree
On Thu, Jul 31, 2014 at 10:43:34AM +0800, Sean Cross wrote:
> This patchset adds support for the Everest Semi ES8328 audio codec, used in
> the Novena open source laptop. It also adds support for using the es8328 on
> IMX boards.
Applied all, thanks.
signature.asc
Description: Digital signature
On Mon, Jul 28, 2014 at 03:05:03PM +0200, Andreas Färber wrote:
> The specification requires compatible = "adi,axi-spdif-1.00.a" but
> driver and example and file name indicate "adi,axi-spdif-tx-1.00.a".
> Change the specification to match the implementation.
Applied, let me once again remind you
On Tue, Jul 15, 2014 at 12:23:01PM +0800, Xiubo Li wrote:
> Changes in V6:
> - there is some mistake for V5 patch series, resend it.
Applied both, thanks.
signature.asc
Description: Digital signature
On Tue, Jul 08, 2014 at 11:40:57AM +0200, Jean-Francois Moine wrote:
> .../devicetree/bindings/drm/i2c/tda998x.txt| 13 ++
> drivers/gpu/drm/i2c/Makefile | 2 +-
> drivers/gpu/drm/i2c/tda998x_codec.c| 247
> +
> drivers/gpu/drm
On Wed, Jul 30, 2014 at 07:27:38PM +0800, Nicolin Chen wrote:
> The Freescale Generic ASoC Sound Card is a general ASoC DAI Link driver that
> can be used, ideally, for all Freescale CPU DAI drivers and external CODECs.
Applied, thanks.
signature.asc
Description: Digital signature
2014-08-02 13:30 GMT+02:00 Wolfram Sang :
> Hi,
>
>> res = platform_get_resource(dev, IORESOURCE_MEM, 0);
>> irq = platform_get_irq(dev, 0);
>> - if (res == NULL || irq < 0) {
>> - ret = -ENODEV;
>> - goto eclk;
>> - }
>> + if (res == NULL || irq < 0)
On Sat, Aug 16, 2014 at 09:53:50AM +0300, Mika Westerberg wrote:
> The recent publication of the ACPI 5.1 specification [1] adds a reserved name
> for Device Specific Data (_DSD, Section 6.2.5). This mechanism allows for
> passing arbitrary hardware description data to the OS. The exact format of t
On Fri, Aug 15, 2014 at 5:38 PM, Rob Herring wrote:
> Adding Greg...
>
> On Tue, Aug 12, 2014 at 9:30 PM, Stepan Moskovchenko
> wrote:
>> When we parse the device tree and allocate platform
>> devices, the 'name' of the newly-created platform_device
>> is set to point to the 'name' field of the '
On Thu, Aug 14, 2014 at 05:22:18PM +0300, Yaniv Gardi wrote:
> diff --git a/drivers/scsi/ufs/ufs-msm.h b/drivers/scsi/ufs/ufs-msm.h
> new file mode 100644
> index 000..6e93f1e
> --- /dev/null
> +++ b/drivers/scsi/ufs/ufs-msm.h
> @@ -0,0 +1,158 @@
[...]
> +};
> +
> +static LIST_HEAD(phy_list);
>
On Sat, Aug 16, 2014 at 05:18:28PM +0200, Markus Pargmann wrote:
> Hi,
>
> This series adds support to the cpsw driver to read the MACIDs of the am335x
> chip and use them as fallback. These addresses are only used if there are no
> mac addresses in the devicetree, for example set by a bootloader.
> + mac_addr[5] = (macid_lo >> 8) & 0xff;
> + mac_addr[4] = macid_lo & 0xff;
> + mac_addr[3] = (macid_hi >> 24) & 0xff;
> + mac_addr[2] = (macid_hi >> 16) & 0xff;
> + mac_addr[1] = (macid_hi >> 8) & 0xff;
> + mac_addr[0] = macid_hi & 0xff;
That looks twisted, but I assume
> diff --git a/drivers/net/ethernet/ti/Makefile
> b/drivers/net/ethernet/ti/Makefile
> index 9cfaab8152be..5a31c2b322ee 100644
> --- a/drivers/net/ethernet/ti/Makefile
> +++ b/drivers/net/ethernet/ti/Makefile
> @@ -8,5 +8,6 @@ obj-$(CONFIG_TI_DAVINCI_EMAC) += davinci_emac.o
> obj-$(CONFIG_TI_DAV
@Ivan: sorry about the double post.
Am 11.08.2014 um 16:40 schrieb Ivan T. Ivanov :
> diff --git a/include/dt-bindings/pinctrl/qcom,pmic-gpio.h
> b/include/dt-bindings/pinctrl/qcom,pmic-gpio.h
> new file mode 100644
> index 000..994e748
> --- /dev/null
> +++ b/include/dt-bindings/pinctrl/qcom
On 8/15/14, 23:53, "Mika Westerberg"
wrote:
>The recent publication of the ACPI 5.1 specification [1] adds a reserved
>name
>for Device Specific Data (_DSD, Section 6.2.5). This mechanism allows for
>passing arbitrary hardware description data to the OS. The exact format
>of the
>_DSD data is spe
Use dev_err instead of pr_err.
Signed-off-by: Markus Pargmann
---
drivers/net/ethernet/ti/cpsw.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/ti/cpsw.c b/drivers/net/ethernet/ti/cpsw.c
index 43b2777f8e04..b52df53441b0 100644
--- a/drivers/net/ethernet/
Signed-off-by: Markus Pargmann
---
arch/arm/boot/dts/am33xx.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index 4a4e02d0ce9e..cb1113bcc290 100644
--- a/arch/arm/boot/dts/am33xx.dtsi
+++ b/arch/arm/boot/dts/am33xx.dtsi
@
This patch adds a function to get the MACIDs from the am33xx SoC
control module registers which hold unique vendor MACIDs. This is only
used if of_get_mac_address() fails to get a valid mac address.
Signed-off-by: Markus Pargmann
---
Documentation/devicetree/bindings/net/cpsw.txt | 4 +++
drive
mac-address is an optional property. If no mac-address is set, a random
mac-address will be generated.
Signed-off-by: Markus Pargmann
---
Documentation/devicetree/bindings/net/cpsw.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/net/cpsw.
ret is set 0 at this point, so jumping to that error label would result
in a return value of 0. Set ret to -ENOMEM to return a proper error
value.
Signed-off-by: Markus Pargmann
---
drivers/net/ethernet/ti/cpsw.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/ethernet/ti/cpsw.c
There are 2 MACIDs stored in the control module of the am33xx. These are
read by the cpsw driver if no valid MACID was found in the devicetree.
Signed-off-by: Markus Pargmann
---
arch/arm/boot/dts/am33xx.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arc
Hi,
This series adds support to the cpsw driver to read the MACIDs of the am335x
chip and use them as fallback. These addresses are only used if there are no
mac addresses in the devicetree, for example set by a bootloader.
In v3 I removed the previously seperate driver and included the changes i
"MII_BUS_ID_SIZE" is defined in linux/phy.h which is not included in the
cpsw.h file.
Signed-off-by: Markus Pargmann
---
drivers/net/ethernet/ti/cpsw.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/ethernet/ti/cpsw.h b/drivers/net/ethernet/ti/cpsw.h
index 574f49da693f..1b710674
On Fri, Aug 08, 2014 at 09:44:25PM +0530, Suman Tripathi wrote:
> This patch removes the NCQ support from the APM X-Gene SoC AHCI
> Host Controller driver as it doesn't support it.
>
> Signed-off-by: Loc Ho
> Signed-off-by: Suman Tripathi
Applied to libata/for-3.17-fixes w/ stable cc'd.
Thanks
40 matches
Mail list logo
