On Thu, Sep 10, 2015 at 05:08:50PM +1000, David Gibson wrote:
> On Fri, Aug 28, 2015 at 09:53:06AM -0500, Rob Herring wrote:
> > On Fri, Aug 28, 2015 at 12:23 AM, Matt Porter <mpor...@konsulko.com> wrote:
> > > Add a skeleton DT binding document that serves as the
On Tue, Sep 01, 2015 at 09:59:14AM -0700, Tim Bird wrote:
> On Thu, Aug 27, 2015 at 10:23 PM, Matt Porter <mpor...@konsulko.com> wrote:
> > Documentation explaining the syntax and format of the YAML-based DT binding
> > documentation.
> >
> > Signed-off-by:
Documentation explaining the syntax and format of the YAML-based DT binding
documentation.
Signed-off-by: Matt Porter <mpor...@konsulko.com>
---
.../devicetree/bindings/dt-binding-format.txt | 105 +
1 file changed, 105 insertions(+)
create mode 100644 Documen
, see TODO list)
There's a lot of other possibilities for validation tools using
only the data we have today in the bindings. In addition, Frank
Rowand covered some DT debug techniques that would benefit from
the binding documentation being 100% reliably searchable.
-Matt
Matt Porter (3):
Documen
Convert the SPI slave portion of the spi-bus.txt binding to the
standard YAML DT binding format.
Signed-off-by: Matt Porter <mpor...@konsulko.com>
---
.../devicetree/bindings/spi/spi-slave.yaml | 108 +
1 file changed, 108 insertions(+)
create mode
Add a skeleton DT binding document that serves as the canonical
example for implementing YAML-based DT bindings documentation.
The skeleton binding illustrates use of all fields and variations
described in the dt-binding-format.txt documentation.
Signed-off-by: Matt Porter <mpor...@konsulko.
On Mon, Aug 31, 2015 at 09:05:00AM -0500, Rob Herring wrote:
> On Fri, Aug 28, 2015 at 12:13 PM, Matt Porter <mpor...@konsulko.com> wrote:
> > On Fri, Aug 28, 2015 at 09:26:17AM -0500, Rob Herring wrote:
> >> On Fri, Aug 28, 2015 at 12:23 AM, Matt Porter <mpor...@konsulk
On Tue, Sep 01, 2015 at 10:35:30AM -0700, Frank Rowand wrote:
> On 9/1/2015 10:14 AM, Tim Bird wrote:
> > On Fri, Aug 28, 2015 at 10:13 AM, Matt Porter <mpor...@konsulko.com> wrote:
>
> < snip >
>
> >>
> >> But to answer your question, if we ge
On Tue, Sep 01, 2015 at 10:35:30AM -0700, Frank Rowand wrote:
> On 9/1/2015 10:14 AM, Tim Bird wrote:
> > On Fri, Aug 28, 2015 at 10:13 AM, Matt Porter <mpor...@konsulko.com> wrote:
>
> < snip >
>
> >>
> >> But to answer your question, if we ge
On Tue, Sep 01, 2015 at 10:14:06AM -0700, Tim Bird wrote:
> On Fri, Aug 28, 2015 at 10:13 AM, Matt Porter <mpor...@konsulko.com> wrote:
>
> > Now, I would caution about trying to do too much on Day 1 or we
> > could end up back at the "never doing anything&
On Tue, Sep 01, 2015 at 09:14:24AM -0700, Tim Bird wrote:
> On Thu, Aug 27, 2015 at 10:23 PM, Matt Porter <mpor...@konsulko.com> wrote:
> > During the Device Tree microconference at Linux Plumbers 2015, we had
> > a short discussion about how to improve DT Binding Docume
On Tue, Sep 01, 2015 at 11:03:50AM -0700, Tim Bird wrote:
> On Tue, Sep 1, 2015 at 10:35 AM, Frank Rowand <frowand.l...@gmail.com> wrote:
> > On 9/1/2015 10:14 AM, Tim Bird wrote:
> >> On Fri, Aug 28, 2015 at 10:13 AM, Matt Porter <mpor...@konsulko
On Sun, Aug 30, 2015 at 03:18:19PM -0700, Frank Rowand wrote:
> On 8/28/2015 11:55 AM, Rob Herring wrote:
> > On Fri, Aug 28, 2015 at 12:49 PM, Matt Porter <mpor...@konsulko.com> wrote:
> >> On Fri, Aug 28, 2015 at 09:53:06AM -0500, Rob Herring wrote:
> >>> On
On Tue, Sep 01, 2015 at 10:35:44AM -0700, Tim Bird wrote:
> On Fri, Aug 28, 2015 at 7:53 AM, Rob Herring <robherri...@gmail.com> wrote:
> > On Fri, Aug 28, 2015 at 12:23 AM, Matt Porter <mpor...@konsulko.com> wrote:
> ...
> >> +example:
&g
On Wed, Sep 02, 2015 at 10:45:13AM +0200, Nicolas Ferre wrote:
> Le 01/09/2015 19:35, Tim Bird a écrit :
> > On Fri, Aug 28, 2015 at 7:53 AM, Rob Herring <robherri...@gmail.com> wrote:
> >> On Fri, Aug 28, 2015 at 12:23 AM, Matt Porter <mpor...@konsulko.com>
> >>> On Fri, Aug 28, 2015 at 10:13 AM, Matt Porter <mpor...@konsulko.com>
> >>> wrote:
> >>
> >> < snip >
> >>
> >>>>
> >>>> But to answer your question, if we get a format I'll do
> >>>&
On Tue, Sep 01, 2015 at 10:42:25AM -0700, Tim Bird wrote:
> On Thu, Aug 27, 2015 at 10:23 PM, Matt Porter <mpor...@konsulko.com> wrote:
> > Convert the ti-phy.txt binding to standard YAML DT binding
> > format. This binding references the YAML generic PHY binding.
> &
On Tue, Sep 01, 2015 at 10:42:25AM -0700, Tim Bird wrote:
> On Thu, Aug 27, 2015 at 10:23 PM, Matt Porter <mpor...@konsulko.com> wrote:
> > Convert the ti-phy.txt binding to standard YAML DT binding
> > format. This binding references the YAML generic PHY binding.
> &
On Sun, Aug 30, 2015 at 03:04:33PM -0700, Frank Rowand wrote:
> On 8/27/2015 10:23 PM, Matt Porter wrote:
> > Documentation explaining the syntax and format of the YAML-based DT binding
> > documentation.
> >
> > Signed-off-by: Matt Porter <mpor...@konsulko.co
On Sun, Aug 30, 2015 at 03:04:33PM -0700, Frank Rowand wrote:
> On 8/27/2015 10:23 PM, Matt Porter wrote:
> > Documentation explaining the syntax and format of the YAML-based DT binding
> > documentation.
> >
> > Signed-off-by: Matt Porter <mpor...@konsulko.co
On Fri, Aug 28, 2015 at 01:55:11PM -0500, Rob Herring wrote:
> On Fri, Aug 28, 2015 at 12:49 PM, Matt Porter <mpor...@konsulko.com> wrote:
> > On Fri, Aug 28, 2015 at 09:53:06AM -0500, Rob Herring wrote:
> >> On Fri, Aug 28, 2015 at 12:23 AM, Matt Porter <mpor...@kons
On Fri, Aug 28, 2015 at 01:55:11PM -0500, Rob Herring wrote:
> On Fri, Aug 28, 2015 at 12:49 PM, Matt Porter <mpor...@konsulko.com> wrote:
> > On Fri, Aug 28, 2015 at 09:53:06AM -0500, Rob Herring wrote:
> >> On Fri, Aug 28, 2015 at 12:23 AM, Matt Porter <mpor...@kons
On Sun, Aug 30, 2015 at 03:04:20PM -0700, Frank Rowand wrote:
> On 8/27/2015 10:23 PM, Matt Porter wrote:
> > During the Device Tree microconference at Linux Plumbers 2015, we had
> > a short discussion about how to improve DT Binding Documentation. A
> > number of issu
On Fri, Aug 28, 2015 at 09:26:17AM -0500, Rob Herring wrote:
On Fri, Aug 28, 2015 at 12:23 AM, Matt Porter mpor...@konsulko.com wrote:
During the Device Tree microconference at Linux Plumbers 2015, we had
a short discussion about how to improve DT Binding Documentation. A
number of issues
On Fri, Aug 28, 2015 at 09:53:06AM -0500, Rob Herring wrote:
On Fri, Aug 28, 2015 at 12:23 AM, Matt Porter mpor...@konsulko.com wrote:
Add a skeleton DT binding document that serves as the canonical
example for implementing YAML-based DT bindings documentation.
The skeleton binding
On Fri, Aug 28, 2015 at 09:53:06AM -0500, Rob Herring wrote:
On Fri, Aug 28, 2015 at 12:23 AM, Matt Porter mpor...@konsulko.com wrote:
Add a skeleton DT binding document that serves as the canonical
example for implementing YAML-based DT bindings documentation.
The skeleton binding
Convert the eeprom.txt binding to standard YAML DT
binding format.
Signed-off-by: Matt Porter mpor...@konsulko.com
---
Documentation/devicetree/bindings/eeprom.yaml | 44 +++
1 file changed, 44 insertions(+)
create mode 100644 Documentation/devicetree/bindings
decide on a text markup format that is acceptable, then the
next step is to convert all the bindings. That process would start
with the complete set of generic bindings as they will be referenced
by the actual device bindings.
If the RFC wasn't explicit enough...comments welcome.
-Matt
Matt
Convert the ti-phy.txt binding to standard YAML DT binding
format. This binding references the YAML generic PHY binding.
Signed-off-by: Matt Porter mpor...@konsulko.com
---
Documentation/devicetree/bindings/phy/ti-phy.yaml | 166 ++
1 file changed, 166 insertions(+)
create
Documentation explaining the syntax and format of the YAML-based DT binding
documentation.
Signed-off-by: Matt Porter mpor...@konsulko.com
---
.../devicetree/bindings/dt-binding-format.txt | 106 +
1 file changed, 106 insertions(+)
create mode 100644 Documentation
decide on a text markup format that is acceptable, then the
next step is to convert all the bindings. That process would start
with the complete set of generic bindings as they will be referenced
by the actual device bindings.
If the RFC wasn't explicit enough...comments welcome.
-Matt
Matt
Add a skeleton DT binding document that serves as the canonical
example for implementing YAML-based DT bindings documentation.
The skeleton binding illustrates use of all fields and variations
described in the dt-binding-format.txt documentation.
Signed-off-by: Matt Porter mpor...@konsulko.com
Convert the generic phy-bindings.txt binding to standard YAML
DT binding format.
Signed-off-by: Matt Porter mpor...@konsulko.com
---
.../devicetree/bindings/phy/phy-bindings.yaml | 89 ++
1 file changed, 89 insertions(+)
create mode 100644 Documentation/devicetree
Add a skeleton DT binding document that serves as the canonical
example for implementing YAML-based DT bindings documentation.
The skeleton binding illustrates use of all fields and variations
described in the dt-binding-format.txt documentation.
Signed-off-by: Matt Porter mpor...@konsulko.com
Documentation explaining the syntax and format of the YAML-based DT binding
documentation.
Signed-off-by: Matt Porter mpor...@konsulko.com
---
.../devicetree/bindings/dt-binding-format.txt | 106 +
1 file changed, 106 insertions(+)
create mode 100644 Documentation
Convert the ti-phy.txt binding to standard YAML DT binding
format. This binding references the YAML generic PHY binding.
Signed-off-by: Matt Porter mpor...@konsulko.com
---
Documentation/devicetree/bindings/phy/ti-phy.yaml | 166 ++
1 file changed, 166 insertions(+)
create
On Wed, Aug 05, 2015 at 11:33:25AM +0300, Daniel Baluta wrote:
On Tue, Aug 4, 2015 at 8:34 PM, Matt Porter mpor...@konsulko.com wrote:
On Tue, Aug 04, 2015 at 05:52:17PM +0100, Jonathan Cameron wrote:
On 3 August 2015 21:56:47 BST, Matt Porter mpor...@konsulko.com wrote:
This series
On Wed, Aug 05, 2015 at 12:04:25PM +0530, Vaibhav Hiremath wrote:
On Monday 27 July 2015 07:39 PM, Matt Porter wrote:
On Tue, Jul 21, 2015 at 06:11:02PM +0530, Vaibhav Hiremath wrote:
Driver will now supports enable/disable across msg xfer, which user
can control it by new DT property
On Wed, Aug 05, 2015 at 10:49:18AM +0200, Wolfram Sang wrote:
Yeah, we could start i2c.txt, probably better to have separate new
patch all together.
I will start such a file today as part of the i2c slave framework
update which introduces flags to the reg property. Will post to the i2c
On Tue, Aug 04, 2015 at 11:30:36AM +0200, Paul Bolle wrote:
On ma, 2015-08-03 at 16:56 -0400, Matt Porter wrote:
--- /dev/null
+++ b/drivers/iio/temperature/max6675.c
+static const struct spi_device_id max6675_spi_ids[] = {
+ {max6675, 0},
+ {},
+};
+MODULE_DEVICE_TABLE(spi
On Tue, Aug 04, 2015 at 10:50:32AM +0300, Daniel Baluta wrote:
On Mon, Aug 3, 2015 at 11:56 PM, Matt Porter mpor...@konsulko.com wrote:
Add a driver for the MAX6675 thermocouple converter. This
device interfaces with K-type thermocouples and provides
cold-junction compensated temperature
On Tue, Aug 04, 2015 at 05:52:17PM +0100, Jonathan Cameron wrote:
On 3 August 2015 21:56:47 BST, Matt Porter mpor...@konsulko.com wrote:
This series adds a driver for the MAX6675 SPI thermocouple converter.
The device supports temperature measurements via type-K thermocouples
On Mon, Aug 03, 2015 at 03:39:00PM -0700, Matt Ranostay Matt Ranostay wrote:
On Mon, Aug 3, 2015 at 1:56 PM, Matt Porter mpor...@konsulko.com wrote:
...
+static int max6675_probe(struct spi_device *spi)
+{
+ struct iio_dev *indio_dev;
+ struct max6675_state *st
This series adds a driver for the MAX6675 SPI thermocouple converter.
The device supports temperature measurements via type-K thermocouples
and implements cold-junction compensation within the part. The datasheet
can be found at http://datasheets.maximintegrated.com/en/ds/MAX6675.pdf
Matt Porter
Add a DT binding for the MAX6675 SPI thermocouple converter.
The datasheet for this device may be found at
http://datasheets.maximintegrated.com/en/ds/MAX6675.pdf
Signed-off-by: Matt Porter mpor...@konsulko.com
---
.../devicetree/bindings/iio/temperature/max6675.txt | 19 +++
1
Add myself as the MAX6675 driver maintainer.
Signed-off-by: Matt Porter mpor...@konsulko.com
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index a226416..355cc09 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -6543,6 +6543,13 @@ S
Add a driver for the MAX6675 thermocouple converter. This
device interfaces with K-type thermocouples and provides
cold-junction compensated temperature readings via a
SPI interface.
Signed-off-by: Matt Porter mpor...@konsulko.com
---
drivers/iio/temperature/Kconfig | 11 +++
drivers/iio
On Tue, Jul 28, 2015 at 10:47:28AM +0200, Teresa Remmet wrote:
Hello Igor,
Am Dienstag, den 28.07.2015, 11:29 +0300 schrieb Igor Grinberg:
Hi Matt,
On 07/27/15 17:34, Matt Porter wrote:
On Thu, Jul 16, 2015 at 10:30:48AM +0200, Teresa Remmet wrote:
phyCORE-AM335x is a SoM (System
On Sat, Jul 11, 2015 at 07:28:50PM +0200, Joachim Eastwood wrote:
Signed-off-by: Joachim Eastwood manab...@gmail.com
---
.../devicetree/bindings/rtc/nxp,lpc1788-rtc.txt | 21
+
1 file changed, 21 insertions(+)
create mode 100644
On Tue, Jul 21, 2015 at 06:11:05PM +0530, Vaibhav Hiremath wrote:
With addition of PXA910 family of devices, the TWSI module supports
new feature which allows us to adjust SCLK. i2c-pxa driver takes input
configuration in nsec and converts it to respective bit-fields,
- i2c-sclk-low-time-ns
On Tue, Jul 21, 2015 at 06:11:02PM +0530, Vaibhav Hiremath wrote:
Driver will now supports enable/disable across msg xfer, which user
can control it by new DT property -
i2c-disable-after-xfer : If set, driver will disable I2C module after msg
xfer and enable it back before xfer.
If this
On Thu, Jul 16, 2015 at 10:30:48AM +0200, Teresa Remmet wrote:
phyCORE-AM335x is a SoM (System on Module) containing
a AM335x SOC. The module can be connected to different
carrier boards.
Some hardware parts are configurable on the phyCORE-AM335x.
So they are disabled on default in this som
On Tue, Apr 07, 2015 at 07:03:30PM +0100, Srinivas Kandagatla wrote:
On 07/04/15 18:46, Mark Brown wrote:
On Tue, Apr 07, 2015 at 06:35:49PM +0100, Srinivas Kandagatla wrote:
On 06/04/15 16:04, Matt Porter wrote:
On Mon, Apr 06, 2015 at 09:11:05AM -0500, Rob Herring wrote:
The generic
On Mon, Mar 30, 2015 at 10:57:59PM +0100, Srinivas Kandagatla wrote:
This patch adds bindings for simple eeprom framework which allows eeprom
consumers to talk to eeprom providers to get access to eeprom cell data.
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
[Maxime Ripard:
On Tue, Mar 31, 2015 at 02:59:21PM +0800, Xinwei Kong wrote:
From: kongxinwei kong.kongxin...@hisilicon.com
This adds documentation of device tree bindings for the
thermal sensor controller of hi6220 SoC.
Signed-off-by: Leo Yan leo@linaro.org
Signed-off-by: kongxinwei
On Mon, Apr 06, 2015 at 09:11:05AM -0500, Rob Herring wrote:
On Mon, Apr 6, 2015 at 8:32 AM, Matt Porter mpor...@konsulko.com wrote:
On Mon, Mar 30, 2015 at 10:57:59PM +0100, Srinivas Kandagatla wrote:
This patch adds bindings for simple eeprom framework which allows eeprom
consumers
the clocks/clock-names properties
so document these,the two required ipg and per clocks, and add
add these properties to the example.
Signed-off-by: Matt Porter mpor...@konsulko.com
---
Changes since v1:
- compatible strings include the actual soc and one of the two specific
compatible parts
the clocks/clock-names properties
so document these,the two required ipg and per clocks, and add
add these properties to the example.
Signed-off-by: Matt Porter mpor...@konsulko.com
---
Documentation/devicetree/bindings/pwm/imx-pwm.txt | 11 ++-
1 file changed, 10 insertions(+), 1 deletion
The omap_serial.txt binding documentation lacks a number of properties
that are used in DTS files for platforms incorporating this peripheral.
Fix this by documenting the missing required and optional fields and
add an example.
Signed-off-by: Matt Porter mpor...@konsulko.com
---
.../devicetree
On Fri, Mar 06, 2015 at 09:16:44AM -0600, Rob Herring wrote:
On Fri, Mar 6, 2015 at 9:09 AM, Matt Porter mpor...@konsulko.com wrote:
The imx-pwm binding contains language indicating compatible
strings to be used that is not valid for all supported parts
e.g. Should be fsl,soc-pwm. Fix
The exact steps provided for submitting binding patches can be read
as requiring the bindings to be sent only to the devicetree@vger.kernel.org
list. Since the DT maintainers would like to be Cced on any binding
submissions, make this requirement explicit in step 2.
Signed-off-by: Matt Porter
document these and the two required ipg and per clocks.
Signed-off-by: Matt Porter mpor...@konsulko.com
---
Documentation/devicetree/bindings/spi/fsl-imx-cspi.txt | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/spi/fsl-imx
A clock specifier is required for i.MX I2C and is
provided in all DTS implementations. Add this to the
list of required properties in the binding.
Signed-off-by: Matt Porter mpor...@konsulko.com
---
Documentation/devicetree/bindings/i2c/i2c-imx.txt | 1 +
1 file changed, 1 insertion(+)
diff
On Mon, Mar 02, 2015 at 08:43:26PM +, Russell King wrote:
On Mon, Mar 02, 2015 at 03:25:40PM -0500, Matt Porter wrote:
On Mon, Mar 02, 2015 at 07:49:08PM +, Russell King wrote:
It's a bit like the MMC stuff, I'm still carrying Olof's solution for
the SDIO wifi/bt power and reset
The PCF8523 RTC is populated on the i2eX boards so
enable the i2c1 controller and enable the device on
that bus.
Signed-off-by: Matt Porter mpor...@konsulko.com
---
arch/arm/boot/dts/imx6qdl-hummingboard.dtsi | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/arch/arm/boot
[added Rabeeh]
On Mon, Mar 02, 2015 at 07:06:16PM +, Russell King wrote:
On Mon, Mar 02, 2015 at 07:02:04PM +, Russell King - ARM Linux wrote:
On Mon, Mar 02, 2015 at 01:50:06PM -0500, Matt Porter wrote:
The PCF8523 RTC is populated on the i2eX boards so
enable the i2c1
On Mon, Mar 02, 2015 at 07:49:08PM +, Russell King wrote:
On Mon, Mar 02, 2015 at 02:21:16PM -0500, Matt Porter wrote:
[added Rabeeh]
On Mon, Mar 02, 2015 at 07:06:16PM +, Russell King wrote:
On Mon, Mar 02, 2015 at 07:02:04PM +, Russell King - ARM Linux wrote:
On Mon
-off-by: Matt Porter mpor...@konsulko.com
---
arch/arm/boot/dts/imx27.dtsi | 2 ++
arch/arm/boot/dts/imx28.dtsi | 1 +
arch/arm/boot/dts/imx35.dtsi | 1 +
arch/arm/boot/dts/imx50.dtsi | 3 +++
arch/arm/boot/dts/imx51.dtsi | 3 +++
arch/arm/boot/dts/imx53.dtsi | 3 +++
arch/arm/boot/dts
The omap_serial.txt binding documentation lacks a number of properties
that are used in DTS files for platforms incorporating this peripheral.
Fix this by documenting the missing required and optional fields and
add an example.
Signed-off-by: Matt Porter mpor...@konsulko.com
---
.../devicetree
On Wed, Feb 18, 2015 at 05:53:50PM +0200, Pantelis Antoniou wrote:
Hi Mark,
On Feb 18, 2015, at 17:41 , Mark Rutland mark.rutl...@arm.com wrote:
Hi Pantelis,
On Wed, Feb 18, 2015 at 02:59:34PM +, Pantelis Antoniou wrote:
Implement a method of applying DT quirks early in the
On Fri, Aug 01, 2014 at 12:29:11PM -0700, Florian Fainelli wrote:
Hello,
2014-08-01 7:33 GMT-07:00 Rob Herring robherri...@gmail.com:
On Wed, Jul 30, 2014 at 9:23 PM, Brian Norris
computersforpe...@gmail.com wrote:
Hi Rob,
I appreciate your comments, but where were many of these 5
On Mon, Jun 30, 2014 at 05:09:45PM -0500, Alex Elder wrote:
Broadcom mobile SoCs use a ROM-implemented holding pen for
controlled boot of secondary cores. A special register is
used to communicate to the ROM that a secondary core should
start executing kernel code. This enable method is
On Tue, Jul 22, 2014 at 10:57:17PM +0200, Arnd Bergmann wrote:
On Tuesday 22 July 2014 13:44:31 Brian Norris wrote:
For the platform changes in the first patch, I would prefer to have
Matt pick up the first patch, but we can also apply it directly into
arm-soc if he prefers that.
On Fri, Jun 20, 2014 at 01:59:30AM +0530, Jassi Brar wrote:
On 20 June 2014 00:33, Matt Porter mpor...@linaro.org wrote:
On Thu, Jun 19, 2014 at 07:17:11PM +0100, Sudeep Holla wrote:
+ * After startup and before shutdown any data received on the chan
+ * is passed on to the API via atomic
On Tue, Jun 17, 2014 at 10:09:31AM +0100, Russell King wrote:
On Mon, Jun 16, 2014 at 09:22:50AM -0400, Jason Kridner wrote:
Adding devicetree and linux-arm-kernel lists based on feedback on IRC...
On Tue, Jun 10, 2014 at 12:46 PM, Jason Kridner jkrid...@gmail.com wrote:
I'd like to
On Tue, Jun 03, 2014 at 03:51:55PM +0530, Jassi Brar wrote:
On 3 June 2014 15:05, Sudeep Holla sudeep.ho...@arm.com wrote:
Hi Jassi,
On Mon, Jun 2, 2014 at 6:11 PM, Jassi Brar jassisinghb...@gmail.com wrote:
On Mon, Jun 2, 2014 at 8:44 PM, Matt Porter mpor...@linaro.org wrote:
On Fri
[Adding devicetree list]
On Mon, Jun 02, 2014 at 10:41:44PM +0530, Jassi Brar wrote:
On Mon, Jun 2, 2014 at 8:44 PM, Matt Porter mpor...@linaro.org wrote:
On Fri, May 30, 2014 at 11:01:55AM +0530, Jassi Brar wrote:
Being more specific to your platform, I think you need some server
code
On Wed, Apr 23, 2014 at 07:21:33PM -0400, Matt Porter wrote:
Adds additional nodes to support GPLDO1-6 and VBUS regulators which
are now supported in the bcm590xx regulator driver.
Applied to mach-bcm for-3.16/dt
arch/arm/boot/dts/bcm59056.dtsi | 21 +
1 file changed, 21
The bcm590xx MFD driver now exposes a secondary regmap descriptor
making the registers for regulators on the secondary I2C slave address
available. Add support for GPLDO1-6 and VBUS regulators found within
this register range.
Signed-off-by: Matt Porter mpor...@linaro.org
Acked-by: Mark Brown
Adds additional nodes to support GPLDO1-6 and VBUS regulators which
are now supported in the bcm590xx regulator driver.
Signed-off-by: Matt Porter mpor...@linaro.org
---
arch/arm/boot/dts/bcm59056.dtsi | 21 +
1 file changed, 21 insertions(+)
diff --git a/arch/arm/boot/dts
this secondary i2c slave address space.
Signed-off-by: Matt Porter mpor...@linaro.org
---
drivers/mfd/bcm590xx.c | 60 +---
include/linux/mfd/bcm590xx.h | 9 ---
2 files changed, 52 insertions(+), 17 deletions(-)
diff --git a/drivers/mfd/bcm590xx.c b
On Tue, May 20, 2014 at 08:00:55PM +0100, Mark Brown wrote:
On Tue, May 20, 2014 at 05:11:31PM +0100, Lee Jones wrote:
drivers/mfd/bcm590xx.c | 60
+---
include/linux/mfd/bcm590xx.h | 9 ---
2 files changed, 52
via a secondary I2C slave address.
The MFD driver exposes an additional regmap descriptor for the additional
address space and the regulator implements support for GPLDO1-6 and VBUS
regulators.
Matt Porter (4):
mfd: bcm590xx: update binding with additional BCM59056 regulators
mfd: bcm590xx: add
The BCM59056 supports GPLDO1-6 and VBUS regulators in a secondary
I2C slave address space. Add these regulators to the list of valid
regulator node names for BCM59056.
Signed-off-by: Matt Porter mpor...@linaro.org
---
Documentation/devicetree/bindings/mfd/bcm590xx.txt | 4 +++-
1 file changed, 3
On Tue, May 20, 2014 at 10:44:39PM +0100, Mark Brown wrote:
On Tue, May 20, 2014 at 04:29:23PM -0400, Matt Porter wrote:
Just resent the v2 series.
I looked at that but it seems I already acked the regulator part of the
series and nothing else looked immediately relevant?
The series has
On Thu, May 15, 2014 at 11:03:49AM -0700, Florian Fainelli wrote:
Hi Alex,
2014-05-15 10:58 GMT-07:00 Alex Elder el...@linaro.org:
This patch adds SMP support for BCM281XX and BCM21664 family SoCs.
This feature is controlled with a distinct config option such that a
SMP-enabled
On Thu, May 15, 2014 at 01:17:00PM -0500, Alex Elder wrote:
On 05/15/2014 01:03 PM, Florian Fainelli wrote:
Hi Alex,
2014-05-15 10:58 GMT-07:00 Alex Elder el...@linaro.org:
This patch adds SMP support for BCM281XX and BCM21664 family SoCs.
This feature is controlled with a distinct
On Tue, May 13, 2014 at 04:06:02PM +0200, Javier Martinez Canillas wrote:
On Tue, May 13, 2014 at 2:53 PM, Tom Rini tr...@ti.com wrote:
On 05/12/2014 04:57 PM, Robert Nelson wrote:
Either case if fine with me. As who knows when the dtc overlay will
every truly make it mainline, as the
On Mon, Apr 28, 2014 at 12:56:27PM +0100, Lee Jones wrote:
On Wed, 23 Apr 2014, Matt Porter wrote:
BCM590xx utilizes a secondary I2C slave address to access additional
register space. Add support for the secondary address space by
instantiating a dummy I2C device with the appropriate
On Mon, Apr 28, 2014 at 08:00:39AM -0700, Tim Kryger wrote:
On Mon, Apr 28, 2014 at 4:07 AM, Thierry Reding
thierry.red...@gmail.com wrote:
On Fri, Apr 25, 2014 at 11:31:10AM -0700, Tim Kryger wrote:
This series introduces the driver for the Kona PWM controller found in
Broadcom mobile
On Mon, Apr 21, 2014 at 04:26:27PM -0500, Alex Elder wrote:
Replace the fake fixed-rate clocks used previously for the
bcm21664 family with real ones.
Signed-off-by: Alex Elder el...@linaro.org
Acked-by: Matt Porter mpor...@linaro.org
---
arch/arm/boot/dts/bcm21664.dtsi | 190
On Fri, Apr 25, 2014 at 05:09:15PM -0700, Mike Turquette wrote:
Quoting Alex Elder (2014-04-21 14:26:22)
This is series has two parts. The first two patches are changes
to the existing Broadcom Kona family clock code to prepare for the
addition of support for another SoC, bcm21664.
, and one dts user all implement the phy-names
property as requiring usb2-phy.
Fix the dwc2.txt binding documentation to correctly specify usb2-phy
as the appropriate value for phy-names.
Reported-by: Tomasz Figa t.f...@samsung.com
Signed-off-by: Matt Porter mpor...@linaro.org
---
Documentation
On Tue, Apr 22, 2014 at 09:21:39AM +0100, Lee Jones wrote:
s/regmap/Regmap
It's consistently written regmap in all the documentation and so on :)
Furry muff; but the comments still stand for the acronyms.
addmap{0,1} doesn't quite sit right with me.
REVISIT:
On Wed, Apr 23, 2014 at 06:01:26PM -0400, Matt Porter wrote:
On Tue, Apr 22, 2014 at 09:21:39AM +0100, Lee Jones wrote:
s/regmap/Regmap
It's consistently written regmap in all the documentation and so on :)
Furry muff; but the comments still stand for the acronyms
via a secondary I2C slave address.
The MFD driver exposes an additional regmap descriptor for the additional
address space and the regulator implements support for GPLDO1-6 and VBUS
regulators.
Matt Porter (4):
mfd: bcm590xx: update binding with additional BCM59056 regulators
mfd: bcm590xx: add
The bcm590xx MFD driver now exposes a secondary regmap descriptor
making the registers for regulators on the secondary I2C slave address
available. Add support for GPLDO1-6 and VBUS regulators found within
this register range.
Signed-off-by: Matt Porter mpor...@linaro.org
Acked-by: Mark Brown
Adds additional nodes to support GPLDO1-6 and VBUS regulators which
are now supported in the bcm590xx regulator driver.
Signed-off-by: Matt Porter mpor...@linaro.org
---
arch/arm/boot/dts/bcm59056.dtsi | 21 +
1 file changed, 21 insertions(+)
diff --git a/arch/arm/boot/dts
this secondary i2c slave address space.
Signed-off-by: Matt Porter mpor...@linaro.org
---
drivers/mfd/bcm590xx.c | 60 +---
include/linux/mfd/bcm590xx.h | 9 ---
2 files changed, 52 insertions(+), 17 deletions(-)
diff --git a/drivers/mfd/bcm590xx.c b
The BCM59056 supports GPLDO1-6 and VBUS regulators in a secondary
I2C slave address space. Add these regulators to the list of valid
regulator node names for BCM59056.
Signed-off-by: Matt Porter mpor...@linaro.org
---
Documentation/devicetree/bindings/mfd/bcm590xx.txt | 4 +++-
1 file changed, 3
1 - 100 of 294 matches
Mail list logo
