On 24 November 2014 at 14:04, Amit Daniel Kachhap
wrote:
> This patch adds supports for parent power domain. This will ensure
> invoking of parent/child power domain on/off in a correct sequence.
> In exynos7 SOC's, power domain controllers have parent and child
> hierarchy.
>
> Cc: Kukjin Kim
>
Hi Mike,
Am Montag, den 24.11.2014, 23:07 -0800 schrieb Mike Turquette:
> Quoting Philipp Zabel (2014-11-03 01:31:18)
> > Some board designers, when running out of clock output pads, decide to
> > (mis)use PWM output pads to provide a clock to external components.
> > This driver supports this pra
On 24 November 2014 at 14:04, Amit Daniel Kachhap
wrote:
> This API may be needed to set the power domain parent/child relationship
> in the power domain platform driver. The parent relationship is
> generally set after the child power domain is registered with the power
> domain subsystem. In thi
This suspend patch is only support cut off the power of cpu and some external
devices, since we still lack power_domain driver, so the other power rail
of rk3288 need keep power on.
I have tested it on rk3288-evb board, atop next-20141124. goto suspend by type
"echo mem > /sys/pow
add pmu sram node for suspend, add global_pwroff pinctrl.
The pmu sram is used to store the resume code.
global_pwroff is held low level at work, it would be pull to high
when entering suspend. reference this in the board DTS file since
some boards need it.
Signed-off-by: Tony Xie
Signed-off-by:
The pmu-sram is used to store resume code, suspend/resume need get the
address of it. Therefore add a binding and documentation for it.
Signed-off-by: Tony Xie
Signed-off-by: Chris Zhong
Reviewed-by: Doug Anderson
---
Changes in v9: None
Changes in v8: None
Changes in v7: None
Changes in v6:
Add suspend-voltages and necessary pin-states for suspend on
rk3288-evb-rk808 boards. global_pwroff would be pulled high when
RK3288 entering suspend, this pin is a sleep signal for RK808, so
RK808 could goto sleep mode, and some regulators would be disable.
Signed-off-by: Chris Zhong
---
Chang
On 24 November 2014 at 14:04, Amit Daniel Kachhap
wrote:
> This patch uses the restructuring done in PD handlers and adds PD
> on/off/status handlers for exynos7. In this SoC, some extra settings
> need to be done prior to turning on/off power domains. Some of those
> settings are also different f
> The ACTMON block can monitor several counters, providing averaging and firing
> interrupts based on watermarking configuration. This implementation monitors
> the MCALL and MCCPU counters to choose an appropriate frequency for the
> external memory clock.
>
> This patch is based on work by Alex
From: Gyungoh Yoo
Signed-off-by: Gyungoh Yoo
Acked-by: Lee Jones
---
Changes v8:
Nothing
Changes v7:
Modified licensing text to GPLv2
Changes v6:
Added new line character at the end of line of dev_err()
Changes v5:
Move sky81452-backlight.h to include/linux/platform_data
Changes v4:
Removed
Quoting Philipp Zabel (2014-11-03 01:31:18)
> Some board designers, when running out of clock output pads, decide to
> (mis)use PWM output pads to provide a clock to external components.
> This driver supports this practice by providing an adapter between the
> PWM and clock bindings in the device
From: Gyungoh Yoo
Signed-off-by: Gyungoh Yoo
---
Changes v8:
Renamed property names for backlight with vendor prefix
Modified gpio-enable property to generic property for GPIO
Changes v7:
Modified licensing text to GPLv2
Changes v6:
Added new line character at the end of line of dev_err()
Cha
From: Gyungoh Yoo
Signed-off-by: Gyungoh Yoo
---
Changes v8:
Renamed property names for backlight with vendor prefix
Modified gpio-enable property to generic property for GPIO
Made up the example for backlight DT
Changes v7:
Nothing
Changes v6:
Nothing
Changes v5:
Nothing
Changes v4:
Nothing
From: Gyungoh Yoo
Signed-off-by: Gyungoh Yoo
---
Changes v8:
Made up the example for backlight DT
Changes v7:
Nothing
Changes v6:
Nothing
Changes v5:
Changed DT for regulator : 'lout' node should be defined under 'regulator'
Removed compatible string from sky81452-regulator driver
Changes v4
From: Gyungoh Yoo
Signed-off-by: Gyungoh Yoo
---
Changes v8:
Nothing
Changes v7:
Nothing
Changes v6:
Nothing
Changes v5:
Nothing
Changes v4:
Nothing
Changes v3:
Nothing
Changes v2:
Added vendor prefix for Skyworks Solutions, Inc.
Documentation/devicetree/bindings/vendor-prefixes.txt | 1
From: Gyungoh Yoo
Signed-off-by: Gyungoh Yoo
---
Changes v8:
Changed the DT parsing of regulator using regulator_node and of_match
Changes v7:
Modified licensing text to GPLv2
Splitted Kconfig renaming from DT patch
Changes v6:
Added new line character at the end of line of dev_err()
Changes
From: Gyungoh Yoo
Signed-off-by: Gyungoh Yoo
---
Changes v8:
Nothing
Changes v7:
Nothing
Changes v6:
Nothing
Changes v5:
Nothing
Changes v4:
Nothing
Changes v3:
Nothing
Changes v2:
Add SKY81452 to the Trivial Devices list
Documentation/devicetree/bindings/i2c/trivial-devices.txt | 1 +
1
From: Gyungoh Yoo
Signed-off-by: Gyungoh Yoo
---
Changes v8:
Nothing
Changes v7:
Nothing
Changes v6:
Nothing
Changes v5:
Changed DT for regulator : 'lout' node should be defined under 'regulator'
Removed compatible string from sky81452-regulator driver
Changes v4:
Nothing
Changes v3:
Nothin
From: Gyungoh Yoo
This patch set includes regulator and backlight driver for SKY81452.
Also it includes documents for device tree and module.
The initial version of sky81452-regulator was applied. Fo this, incremental
patches are included.
v8:
Renamed property names for backlight with vendor pre
Dear Andrew Lunn,
On Sun, 23 Nov 2014 04:36:03 +0100, Andrew Lunn wrote:
> > No, it is not the BootROM that does this. It is the binary header,
> > which is something different.
>
> O.K, so this definitely needs documenting somewhere, since it is not
> obvious. I'm not sure if it is sufficient t
On Tue, Nov 25, 2014 at 12:00:16AM +0100, Andrew Lunn wrote:
> On Mon, Nov 24, 2014 at 10:23:58PM +, Leif Lindholm wrote:
> > Support specifying console options (like with console=ttyXN,)
> > by appending them to the stdout-path property after a separating ':'.
> >
> > Example:
> > stdout-
Mike,
On Mon, 24 Nov 2014 22:07:00 -0800, Mike Turquette wrote:
> Quoting Thomas Petazzoni (2014-11-21 08:00:05)
> > This commit adds suspend/resume support for the gatable clock driver
> > used on Marvell EBU platforms. When getting out of suspend, the
> > Marvell EBU platforms go through the boo
Quoting Arnd Bergmann (2014-11-24 02:50:28)
> On Friday 21 November 2014 20:58:01 Grygorii Strashko wrote:
> > Hi Kevin,
> > On 11/21/2014 10:06 AM, Geert Uytterhoeven wrote:
> > > On Fri, Nov 21, 2014 at 2:30 AM, Kevin Hilman wrote:
> > >> Geert Uytterhoeven writes:
> > >>
> > >> So now I'm conf
Hi, Jaehoon
On 2014/11/20 18:01, Jaehoon Chung wrote:
Hi, Addy.
On 11/20/2014 06:33 PM, addy ke wrote:
Hi, Jaehoon
On 2014/11/19 13:56, addy ke wrote:
Hi Jaehoon
On 2014/11/19 09:22, Jaehoon Chung Wrote:
Hi, Addy.
On 11/18/2014 09:32 AM, Addy wrote:
On 2014年11月14日 21:18, Jaehoon Chung wr
Quoting Thomas Petazzoni (2014-11-21 08:00:05)
> This commit adds suspend/resume support for the gatable clock driver
> used on Marvell EBU platforms. When getting out of suspend, the
> Marvell EBU platforms go through the bootloader, which re-enables all
> gatable clocks. However, upon resume, the
Addy,
On Mon, Nov 24, 2014 at 6:38 PM, Addy wrote:
>> In worst case scenario, VDD = 3.6V and VIO = 2.7V. That gives as the
>> factor of 0.75, thus we are inside spec but without margins.
>
> * From eMMC4.5 spec:
> 1. (VDDF)vcc: Supply voltage for flash memory, which is 2.7v -- 3.3v
> 2. (VD
Ulf,
On Mon, Nov 24, 2014 at 5:29 AM, Ulf Hansson wrote:
>> 2. Several people I've talked to have expressed concerns that our
>> minimum value is 2.7V. Apparently that's really on the edge and makes
>> EEs a little nervous. The quick sample of cards sitting on my desk
>> shows that they seem to
Hi Paul,
On Thursday 20 November 2014 10:26 PM, Paul Walmsley wrote:
> On Thu, 20 Nov 2014, Lokesh Vutla wrote:
>
>> On Monday 17 November 2014 10:13 AM, Lokesh Vutla wrote:
>>> RTC IP have kicker feature which prevents spurious writes to its registers.
>>> In order to write into any of the RTC re
Hi,
On 2014/11/22 5:23, Ganapatrao Kulkarni wrote:
> DT bindings for numa map for memory, cores to node and
> proximity distance matrix of nodes to each other.
>
> Signed-off-by: Ganapatrao Kulkarni
> ---
> Documentation/devicetree/bindings/arm/numa.txt | 103
> +
> 1 f
On Fri, Nov 24, 2014 at 9:29 PM, Ulf Hansson
wrote:
On 21 November 2014 at 22:04, Doug Anderson wrote:
Hi,
On Fri, Nov 21, 2014 at 9:42 AM, Doug Anderson wrote:
Ulf,
On Fri, Nov 21, 2014 at 4:06 AM, Ulf Hansson wrote:
[...]
Sure
If the first card is sd2.0 since startup, dw_mci_swit
Quoting Geert Uytterhoeven (2014-11-20 23:38:26)
> Hi Magnus,
>
> On Fri, Nov 21, 2014 at 6:54 AM, Magnus Damm wrote:
> >>> From my side this series "[PATCH v7 0/2] clk: shmobile: DIV6 clock
> >>> variable parent support" looks quite finalized. Would it be possible
> >>
> >> Does this mean I can
On Mon, Nov 17, 2014 at 12:23:33PM +, Lee Jones wrote:
> On Mon, 17 Nov 2014, gyun...@gmail.com wrote:
>
> > From: Gyungoh Yoo
> >
> > Signed-off-by: Gyungoh Yoo
> > ---
> > Changes v7:
> > Nothing
> >
> > Changes v6:
> > Nothing
> >
> > Changes v5:
> > Nothing
> >
> > Changes v4:
> > No
Heiko,
在 2014年11月25日 07:39, Heiko Stübner 写道:
Hi Caesar,
Am Montag, 24. November 2014, 16:18:12 schrieb Eduardo Valentin:
Hello Caesar,
On Mon, Nov 24, 2014 at 12:58:57PM +0800, Caesar Wang wrote:
This series patchs tested on rk3288 SDK board and pinky-v1,v2 board.
I believe the driver can b
On Fri, Nov 14, 2014 at 09:04:29AM +0100, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Fri, Nov 14, 2014 at 4:02 AM, Simon Horman wrote:
> > On Thu, Oct 30, 2014 at 12:03:22PM +0100, Geert Uytterhoeven wrote:
> >> On Thu, Oct 30, 2014 at 11:44 AM, Laurent Pinchart
> >> wrote:
> >> > On Wednesday
The mailbox controller's channel ops ought to be read-only.
Signed-off-by: Andrew Bresticker
---
No changes from v5.
New for v5.
---
include/linux/mailbox_controller.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/mailbox_controller.h
b/include/linux/mailbox_
xhci_gen_setup() sets the hcd_priv field for the primary HCD, but not
for the shared HCD, requiring xHCI host-controller drivers to set it
between usb_create_shared_hcd() and usb_add_hcd(). There's no reason
xhci_gen_setup() can't set the shared HCD's hcd_priv as well, so move
that bit out of the
From: Benson Leung
mbox_request_channel() currently returns EBUSY in the event the controller
is not present or if of_xlate() fails, but in neither case is EBUSY really
appropriate. Return EPROBE_DEFER if the controller is not yet present
and change of_xlate() to return an ERR_PTR instead of NUL
Add device-tree bindings for the Tegra XUSB mailbox which will be used
for communication between the Tegra xHCI controller's firmware and the
host processor.
Signed-off-by: Andrew Bresticker
Reviewed-by: Stephen Warren
Acked-by: Jassi Brar
---
No changes from v3/v4/v5.
Changes from v2:
- Dropp
The Tegra xHCI controller's firmware communicates requests to the host
processor through a mailbox interface. While there is only a single
physical channel, messages sent by the controller can be divided
into two groups: those intended for the PHY driver and those intended
for the host-controller
Add device-tree binding documentation for the xHCI controller present
on Tegra124 and later SoCs.
Signed-off-by: Andrew Bresticker
Reviewed-by: Stephen Warren
---
No changes from v5.
Changes from v4:
- Updated regulator names, as suggested by Thierry.
No changes from v3.
Changes from v2:
- Add
Add new bindings used for USB support by the Tegra XUSB pad controller.
This includes additional PHY types, USB-specific pinconfig properties, etc.
Signed-off-by: Andrew Bresticker
Acked-by: Linus Walleij
Reviewed-by: Stephen Warren
---
No changes from v5.
Changes from v4:
- nvidia,usb2-port-n
Assign ports previously owned by the EHCI controllers to the xHCI
controller. There are two external USB ports (UTMI ports 0/2 and
USB3 ports 0/1) and an internal USB port (UTMI port 1). PCIe lanes
0 and 1 are used by the USB3 ports.
Signed-off-by: Andrew Bresticker
Reviewed-by: Stephen Warren
In addition to the PCIe and SATA PHYs, the XUSB pad controller also
supports 3 UTMI, 2 HSIC, and 2 USB3 PHYs. Each USB3 PHY uses a single
PCIe or SATA lane and is mapped to one of the three UTMI ports.
The xHCI controller will also send messages intended for the PHY driver,
so request and listen
Add support for the on-chip xHCI host controller present on Tegra SoCs.
The controller requires external firmware which must be loaded before
using the controller. This driver loads the firmware, starts the
controller, and is able to service host-specific messages sent by
the controller's firmware
Assign USB ports previously owned by the EHCI controllers to the xHCI
controller. There is a mini-PCIe USB port (UTMI port 1) and a USB A
connector (UTMI port 2, USB3 port 0). PCIe lane 0 is used for USB3
port 0.
Signed-off-by: Andrew Bresticker
Reviewed-by: Stephen Warren
---
No changes from
Add nodes for the Tegra XUSB mailbox and Tegra xHCI controller and
add the PHY mailbox channel to the XUSB padctl node.
Signed-off-by: Andrew Bresticker
Reviewed-by: Stephen Warren
---
No changes from v3/v4/v5.
Changes from v2:
- Dropped channel specifier from mailbox bindings.
- Added mbox-na
This series adds support for xHCI on NVIDIA Tegra SoCs. This includes:
- patches 1, 2, and 3: minor cleanups for mailbox framework and xHCI,
- patches 4 and 5: adding a driver for the mailbox used to communicate
with the xHCI controller's firmware,
- patches 6 and 7: extending the XUSB pad c
On Tue, Nov 25, 2014 at 12:00:16AM +0100, Andrew Lunn wrote:
> On Mon, Nov 24, 2014 at 10:23:58PM +, Leif Lindholm wrote:
> > Support specifying console options (like with console=ttyXN,)
> > by appending them to the stdout-path property after a separating ':'.
> >
> > Example:
> > stdout-
On 11/24/2014 03:36 PM, Kevin Cernekee wrote:
> My last submission attempted to work around serial driver coexistence
> problems on multiplatform kernels. Since there are still questions
> surrounding the best way to solve that problem, this patch series
> will focus on the narrower topic of big e
On Mon, 2014-11-24 at 05:07 -0600, Emil Medve wrote:
> From: Kumar Gala
>
> Change-Id: If643fa5ba0a903aef8f5056a2c90ebecc995b760
> Signed-off-by: Kumar Gala
> Signed-off-by: Geoff Thorpe
> Signed-off-by: Hai-Ying Wang
> Signed-off-by: Chunhe Lan
> Signed-off-by: Poonam Aggrwal
> [Emil Medve:
SoC peripherals can come in several different flavors:
- little-endian: registers always need to be accessed in LE mode (so the
kernel should perform a swap if the CPU is running BE)
- big-endian: registers always need to be accessed in BE mode (so the
kernel should perform a swap if the
Provide a libfdt-based equivalent for of_device_is_big_endian(), suitable
for use in the early_init_* functions.
Signed-off-by: Kevin Cernekee
---
drivers/of/fdt.c | 19 +++
include/linux/of_fdt.h | 2 ++
2 files changed, 21 insertions(+)
diff --git a/drivers/of/fdt.c b/d
If the device node has a "big-endian" property and 32-bit registers, tell
the serial driver to use UPIO_MEM32BE instead of UPIO_MEM32.
Signed-off-by: Kevin Cernekee
---
drivers/tty/serial/of_serial.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/tty/serial/of_seri
These apply to newly converted drivers, like serial8250/libahci/...
The examples were adapted from the regmap bindings document.
Signed-off-by: Kevin Cernekee
---
.../devicetree/bindings/common-properties.txt | 60 ++
1 file changed, 60 insertions(+)
create mode 100644
Since most drivers interpret UPIO_MEM32 to mean "little-endian" and use
readl/writel to access the registers, add a parallel UPIO_MEM32BE to
request the use of big-endian MMIO accessors (ioread32be/iowrite32be).
Signed-off-by: Kevin Cernekee
---
drivers/tty/serial/serial_core.c | 2 ++
include/
Add cases for UPIO_MEM32BE wherever there are currently cases handling
UPIO_MEM32.
Signed-off-by: Kevin Cernekee
---
drivers/tty/serial/8250/8250_core.c | 20
drivers/tty/serial/8250/8250_early.c | 5 +
2 files changed, 25 insertions(+)
diff --git a/drivers/tty/serial
My last submission attempted to work around serial driver coexistence
problems on multiplatform kernels. Since there are still questions
surrounding the best way to solve that problem, this patch series
will focus on the narrower topic of big endian MMIO support on serial.
V2->V3:
- Document t
If an earlycon (stdout-path) node is being used, check for "big-endian"
or "native-endian" properties and pass the appropriate iotype to the
driver.
Note that LE sets UPIO_MEM (8-bit) but BE sets UPIO_MEM32BE (32-bit). The
big-endian property only really makes sense in the context of 32-bit
regis
Hi Caesar,
Am Montag, 24. November 2014, 16:18:12 schrieb Eduardo Valentin:
> Hello Caesar,
>
> On Mon, Nov 24, 2014 at 12:58:57PM +0800, Caesar Wang wrote:
> > This series patchs tested on rk3288 SDK board and pinky-v1,v2 board.
> > I believe the driver can be used on the rk3288-evb board.
> >
Hi Jassi,
On 11/24/2014 03:54 AM, Jassi Brar wrote:
> On 4 November 2014 at 04:35, Suman Anna wrote:
>> The OMAP mailbox driver and its existing clients (remoteproc
>> for OMAP4+) are adapted to use the generic mailbox framework.
>>
>> The main changes for the adaptation are:
>> - The tasklet u
On Mon, Nov 24, 2014 at 10:23:58PM +, Leif Lindholm wrote:
> Support specifying console options (like with console=ttyXN,)
> by appending them to the stdout-path property after a separating ':'.
>
> Example:
> stdout-path = "uart0:115200";
>
> This patch also modifies of_find_node_by_pa
Am Freitag, 21. November 2014, 10:06:47 schrieb James Hogan:
> On Thu, Nov 20, 2014 at 01:56:24PM +0100, Heiko Stübner wrote:
> > I don't know enough about your clock structure, but it looks quite a bit
> > like Mike's mail from May [0] may apply here too.
> >
> > The register layout also suggests
Hi Chris,
The subject above should reflect the pinctrl settings, something like:
"ARM: dts: rockchip: add suspend settings for rk3288-evb-rk808"
Same for the description:
Add suspend-voltages and necessary pin-states for suspend on
rk3288-evb-rk808 boards. global_pwroff would be pulled high whe
On Fri 2014-11-21 09:15:31, Jacek Anaszewski wrote:
> Hi Pavel,
>
> On 11/20/2014 09:52 PM, Pavel Machek wrote:
> >On Thu 2014-11-20 15:48:26, Jacek Anaszewski wrote:
> >>On 11/20/2014 02:38 PM, Jacek Anaszewski wrote:
> >>>Hi Pavel,
> >>>
> >>>On 11/20/2014 02:17 PM, Pavel Machek wrote:
>
>
iatly again. But as it wakes at all, I'm quite happy :-) .
I remember this being mentioned before, but I don't remember what was
responsible for that. Was it because we only enter the light suspend mode
instead of the deep one or some interrupt somewhere?
I've been runni
From: Pantelis Antoniou
The original resolver format is way too cryptic, switch
to using a tree based format that gets rid of repetitions,
is more compact and readable.
At the same time, update the selftests to using the new local fixups
format.
Signed-off-by: Pantelis Antoniou
[grant.likely:
From: Pantelis Antoniou
Introduce of_reconfig_get_state_change() which allows an of notifier
to query about device state changes.
Signed-off-by: Pantelis Antoniou
Signed-off-by: Grant Likely
---
drivers/of/dynamic.c | 96
include/linux/of.h
The overlay code needs to construct a new full_name from the parent name
and the node name, but the current method has to allocate and then free
an temporary string which is wasteful. Fix this problem by using vargs
to pass in a format and arguments into __of_node_alloc().
At the same time remove
Add a node argument to __of_node_alloc() and rename it to
__of_node_dup() so that it can also be used to duplicate a node with
its properties. This is important for the overlay code so that it can
create new nodes without using separate changeset items for every single
property.
At the same time r
The OF_RECONFIG notifier callback uses a different structure depending
on whether it is a node change or a property change. This is silly, and
not very safe. Rework the code to use the same data structure regardless
of the type of notifier.
Signed-off-by: Grant Likely
Cc: Benjamin Herrenschmidt
To simplify subsystem setup code, make empty stubs for the
of_reconfig_*() methods. This is particularly useful for registering and
unregistering the notifiers so that it doesn't impact the flow of the
subsystem setup code.
Signed-off-by: Grant Likely
---
include/linux/of.h | 29
Add some additional debug output to cover OF_RECONFIG notifier activity.
At the same time, refactor the changeset debug output to use the same
strings as the notifier debug output.
Signed-off-by: Grant Likely
---
drivers/of/dynamic.c | 48
1 file
From: Pantelis Antoniou
Add OF notifier handler needed for creating/destroying platform devices
according to dynamic runtime changes in the DT live tree.
Signed-off-by: Pantelis Antoniou
Signed-off-by: Grant Likely
---
drivers/base/platform.c | 1 +
drivers/of/platform.c | 55 +
From: Pantelis Antoniou
Add unittests for OF overlays.
It tests overlay device addition/removal and whether
the apply revert sequence is correct.
Changes since V1:
* Added local fixups entries.
Signed-off-by: Pantelis Antoniou
Signed-off-by: Grant Likely
---
Documentation/devicetree/binding
From: Pantelis Antoniou
CONFIG_OF_DYNAMIC enables runtime changes to the device tree which in
turn may trigger addition or removal of devices from Linux. Add an
OF_RECONFIG notifier handler to receive tree change events and to
creating or destroy i2c devices as required.
Signed-off-by: Pantelis
From: Pantelis Antoniou
Overlays are a method to dynamically modify part of the kernel's
device tree with dynamically loaded data. Add the core functionality to
parse, apply and remove an overlay changeset. The core functionality
takes care of managing the overlay data format and performing the a
From: Pantelis Antoniou
Add OF notifier handler needed for creating/destroying spi devices
according to dynamic runtime changes in the DT live tree. This code is
enabled when CONFIG_OF_DYNAMIC is selected.
Signed-off-by: Pantelis Antoniou
Signed-off-by: Grant Likely
Cc: Mark Brown
Cc:
---
d
From: Pantelis Antoniou
Dynamically inserting spi device nodes requires the use of a single
device registration method. Refactor the existing
of_register_spi_devices() to split out the core functionality for a
single device into a separate function; of_register_spi_device(). This
function will be
From: Pantelis Antoniou
Dynamically inserting i2c client device nodes requires the use
of a single device registration method. Factor out the loop body of
of_i2c_register_devices() so that it can be called for individual
device_nodes instead of for all the children of a node.
Note: The diff of t
This is the second time I've posted the Devicetree Overlay patch series
with the intention of merging for v3.19. I'm reposting the entire series
again because I've done some mild rework and reordered a number of
things to make a bit more sense. Most notable changes are:
patch 04/14: Change the retu
On Fri, Nov 21, 2014 at 1:43 AM, Joe Perches wrote:
> On Fri, 2014-11-21 at 01:35 +, Grant Likely wrote:
>> The overlay code needs to construct a new full_name from the parent name
>> and the node name, but the current method has to allocate and then free
>> an temporary string which is wastef
Support specifying console options (like with console=ttyXN,)
by appending them to the stdout-path property after a separating ':'.
Example:
stdout-path = "uart0:115200";
This patch also modifies of_find_node_by_path() to match only the
portion of the path before a ':'.
Signed-off-by: Le
On Fri, Nov 21, 2014 at 10:13:10AM +0100, Hans de Goede wrote:
> Hi,
>
> On 11/21/2014 09:49 AM, Maxime Ripard wrote:
> > Hi,
> >
> > On Thu, Nov 20, 2014 at 04:55:22PM +0100, Hans de Goede wrote:
> >> Add a driver for mod0 clocks found in the prcm. Currently there is only
> >> one mod0 clocks in
On Mon, Nov 24, 2014 at 10:11 PM, Sergei Shtylyov
wrote:
>> Also rename the node's name from "lan9220" to "ethernet", to confirm to
>
>s/confirm/comply/, you mean?
Sorry, conform.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
On Monday 24 November 2014 13:07:46 Kevin Cernekee wrote:
> On Mon, Nov 24, 2014 at 6:00 AM, Arnd Bergmann wrote:
> > It mihgt be good to split this into multiple patches
>
> OK. For V4 I could submit the arch/mips/bmips code changes in one
> patch, and then add the DTS files in the next patch?
Hello.
On 11/24/2014 11:10 PM, Geert Uytterhoeven wrote:
Move the Ethernet node from the root of the device tree to the BSC node,
as it is connected to the Bus State Controller. This allows the system
to know the right position of the Ethernet node in the clock and PM
domain hierarchy.
Also
On Mon, Nov 24, 2014 at 6:00 AM, Arnd Bergmann wrote:
> It mihgt be good to split this into multiple patches
OK. For V4 I could submit the arch/mips/bmips code changes in one
patch, and then add the DTS files in the next patch?
>> --- /dev/null
>> +++ b/arch/mips/bmips/Kconfig
>> @@ -0,0 +1,50
On Mon, Nov 24, 2014 at 8:01 AM, Alban Bedel
wrote:
> Signed-off-by: Alban Bedel
> ---
> .../devicetree/bindings/gpio/gpio-level-shifter.txt | 15
> +++
> 1 file changed, 15 insertions(+)
> create mode 100644
> Documentation/devicetree/bindings/gpio/gpio-level-shifter.txt
>
Hi Arnd,
On Mon, Nov 24, 2014 at 9:15 PM, Arnd Bergmann wrote:
> On Monday 24 November 2014 21:10:05 Geert Uytterhoeven wrote:
>> As this minimal BSC driver isn't hardware-specific at all, I'm wondering
>> if there's a simpler way to do this?
>> - Should the driver be renamed to "simple-bus", a
Hello Caesar,
On Mon, Nov 24, 2014 at 12:58:57PM +0800, Caesar Wang wrote:
> This series patchs tested on rk3288 SDK board and pinky-v1,v2 board.
> I believe the driver can be used on the rk3288-evb board.
>
> Add this driver, The system will shutdown when
> the thermal temperture over 100C.If fo
On Monday 24 November 2014 21:10:05 Geert Uytterhoeven wrote:
> As this minimal BSC driver isn't hardware-specific at all, I'm wondering
> if there's a simpler way to do this?
> - Should the driver be renamed to "simple-bus", and match "simple-bus"?
> - Should this be moved to core code, withou
Hi all,
The Renesas Bus State Controller (BSC) provides an external bus for
connecting multiple external devices to an SoC, driving several chip
select lines, for e.g. NOR FLASH, Ethernet and USB.
On the kzm9g development board, an smsc9220 Ethernet controller is
connnected to the BSC of t
Add a node for the Bus State Controller (BSC) on sh73a0, to which
multiple external devices can be connected.
The BSC is driven by the ZB clock, and located in PM domain A4S.
For now no device tree bindings have been defined yet. All of its
properties follow standard conventions.
Signed-off-by:
Add a driver for the Renesas Bus State Controller (BSC, sometimes called
"LBSC within Bus Bridge", or "External Bus Interface") found on several
Renesas ARM SoCs.
The sole purpose of this driver is to enable its clock and PM domain (if
exist(s)), which are specified in the DT and managed from plat
Move the Ethernet node from the root of the device tree to the BSC node,
as it is connected to the Bus State Controller. This allows the system
to know the right position of the Ethernet node in the clock and PM
domain hierarchy.
Also rename the node's name from "lan9220" to "ethernet", to confir
On Mon, Nov 24, 2014 at 11:29 AM, Andrew Bresticker wrote:
>> diff --git a/arch/mips/bmips/setup.c b/arch/mips/bmips/setup.c
>
>> +void __init plat_time_init(void)
>> +{
>> + struct device_node *np;
>> + u32 freq;
>> +
>> + np = of_find_node_by_name(NULL, "cpus");
>> + if (
Signed-off-by: Nikolaus Schulz
---
.../devicetree/bindings/iio/dac/ti-dac8554.txt | 22 ++
1 file changed, 22 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/dac/ti-dac8554.txt
diff --git a/Documentation/devicetree/bindings/iio/dac/ti-dac8554.txt
The TI DAC8554 is a quad-channel Digital-to-Analog Converter with an SPI
interface.
Changes in v2:
* Use DMA-safe buffer for SPI transfer
* Normalize powerdown_mode name "hi-z" to "three_state" as per
ABI/testing/sysfs-bus-iio
* Register device late in probe function
* Avoid powerdown broadcast
On Fri, Nov 14, 2014 at 02:07:15PM -0800, Frank Rowand wrote:
> From: Frank Rowand
>
> Update devicetree binding for msm_serial to reflect msm_serial_probe()
> getting line id (port number) from the serialN alias.
>
> Signed-off-by: Frank Rowand
> ---
> Documentation/devicetree/bindings/serial
> diff --git a/arch/mips/bmips/setup.c b/arch/mips/bmips/setup.c
> +void __init plat_time_init(void)
> +{
> + struct device_node *np;
> + u32 freq;
> +
> + np = of_find_node_by_name(NULL, "cpus");
> + if (!np)
> + panic("missing 'cpus' DT node");
> + if
1 - 100 of 222 matches
Mail list logo
