4.4 bbbw dt updates #95

Signed-off-by: Robert Nelson <[email protected]>

… is defined 'owner' member of 'struct mutex' is defined as below in 'include/linux/mutex.h': struct mutex { ... if defined(CONFIG_DEBUG_MUTEXES) || defined(CONFIG_MUTEX_SPIN_ON_OWNER) struct task_struct *owner; endif ... But function au_pin_hdir_set_owner() called owner as below: void au_pin_hdir_set_owner(struct au_pin *p, struct task_struct *task) { if defined(CONFIG_DEBUG_MUTEXES) || defined(CONFIG_SMP) p->hdir->hi_inode->i_mutex.owner = task; endif } So if Kernel doesn't define 'DEBUG_MUTEXES' and 'MUTEX_SPIN_ON_OWNER', but defines SMP, compiler will report the below error: fs/aufs/i_op.c: In function 'au_pin_hdir_set_owner': fs/aufs/i_op.c:593:28: error: 'struct mutex' has no member named 'owner' p->hdir->hi_inode->i_mutex.owner = task; ^ Signed-off-by: Yanjiang Jin <[email protected]> Signed-off-by: Bruce Ashfield <[email protected]>

Signed-off-by: Robert Nelson <[email protected]>

Beyond the warning: drivers/tty/serial/8250/8250.c:1613:6: warning: unused variable ‘pass_counter’ [-Wunused-variable] the solution of just looping infinitely was ugly - up it to 1 million to give it a chance to continue in some really ugly situation. Signed-off-by: Ingo Molnar <[email protected]> Signed-off-by: Thomas Gleixner <[email protected]>

Signed-off-by: Robert Nelson <[email protected]>

Adds support for using a OMAP dual-mode timer with PWM capability as a Linux PWM device. The driver controls the timer by using the dmtimer API. Add a platform_data structure for each pwm-omap-dmtimer nodes containing the dmtimers functions in order to get driver not rely on platform specific functions. Cc: Grant Erickson <[email protected]> Cc: NeilBrown <[email protected]> Cc: Joachim Eastwood <[email protected]> Suggested-by: Tony Lindgren <[email protected]> Signed-off-by: Neil Armstrong <[email protected]> Acked-by: Tony Lindgren <[email protected]> [[email protected]: coding style bikeshed, fix timer leak] Signed-off-by: Thierry Reding <[email protected]>

"omap" is NULL so we can't dereference it. Signed-off-by: Dan Carpenter <[email protected]> Signed-off-by: Thierry Reding <[email protected]>

In order to set the currently platform dependent dmtimer functions pointers as platform data for the pwm-omap-dmtimer platform driver, add it to plat-omap auxdata_lookup table. Suggested-by: Tony Lindgren <[email protected]> Signed-off-by: Neil Armstrong <[email protected]> Signed-off-by: Tony Lindgren <[email protected]>

Fix the calculation of load_value and match_value. Currently they are slightly too low, which produces a noticeably wrong PWM rate with sufficiently short periods (i.e. when 1/period approaches clk_rate/2). Example: clk_rate=32768Hz, period=122070ns, duty_cycle=61035ns (8192Hz/50% PWM) Correct values: load = 0xfffffffc, match = 0xfffffffd Current values: load = 0xfffffffa, match = 0xfffffffc effective PWM: period=183105ns, duty_cycle=91553ns (5461Hz/50% PWM) Fixes: 6604c65 ("pwm: Add PWM driver for OMAP using dual-mode timers") Signed-off-by: David Rivshin <[email protected]> Acked-by: Neil Armstrong <[email protected]> Tested-by: Adam Ford <[email protected]> Signed-off-by: Thierry Reding <[email protected]>

Add sanity checking to ensure that we do not program load or match values that are out of range if a user requests period or duty_cycle values which are not achievable. The match value cannot be less than the load value (but can be equal), and neither can be 0xffffffff. This means that there must be at least one fclk cycle between load and match, and another between match and overflow. Fixes: 6604c65 ("pwm: Add PWM driver for OMAP using dual-mode timers") Signed-off-by: David Rivshin <[email protected]> Acked-by: Neil Armstrong <[email protected]> [[email protected]: minor coding style cleanups] Signed-off-by: Thierry Reding <[email protected]>

When converting period and duty_cycle from nanoseconds to fclk cycles, the error introduced by the integer division can be appreciable, especially in the case of slow fclk or short period. Use DIV_ROUND_CLOSEST_ULL() so that the error is kept to +/- 0.5 clock cycles. Fixes: 6604c65 ("pwm: Add PWM driver for OMAP using dual-mode timers") Signed-off-by: David Rivshin <[email protected]> Acked-by: Neil Armstrong <[email protected]> Signed-off-by: Thierry Reding <[email protected]>

After going through the math and constraints checking to compute load and match values, it is helpful to know what the resultant period and duty cycle are. Signed-off-by: David Rivshin <[email protected]> Acked-by: Neil Armstrong <[email protected]> Signed-off-by: Thierry Reding <[email protected]>

This reverts commit 956b200.

This reverts commit aa01567. Signed-off-by: Robert Nelson <[email protected]>

<zmatt> rcn-ee: btw, I got a small patch that makes 4.1-ti compile in thumb mode again, you want it? (this means TI still compiles in ARM mode? why oh why?) <zmatt> http://pastebin.com/3S3sy8U4 Signed-off-by: Robert Nelson <[email protected]>

Signed-off-by: Robert Nelson <[email protected]>

… there is also a hidden SSID in the scan list Signed-off-by: Robert Nelson <[email protected]>

Signed-off-by: Robert Nelson <[email protected]>

Use kobj_to_dev() instead of open-coding it. Signed-off-by: Geliang Tang <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

Compatible at93xx46 devices from both Microchip and Atmel expect a word-based address, regardless of whether the device is strapped for 8- or 16-bit operation. However, the offset parameter passed in when reading or writing at a specific location is always specified in terms of bytes. This commit fixes 16-bit read and write accesses by shifting the offset parameter to account for this difference between a byte offset and a word-based address. Signed-off-by: Cory Tusar <[email protected]> Tested-by: Chris Healy <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

This commit implements bindings in the eeprom_93xx46 driver allowing device word size and read-only attributes to be specified via devicetree. Signed-off-by: Cory Tusar <[email protected]> Tested-by: Chris Healy <[email protected]> Reviewed-by: Vladimir Zapolskiy <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

Atmel devices in this family have some quirks not found in other similar chips - they do not support a sequential read of the entire EEPROM contents, and the control word sent at the start of each operation varies in bit length. This commit adds quirk support to the driver and modifies the read implementation to support non-sequential reads for consistency with other misc/eeprom drivers. Tested on a custom Freescale VF610-based platform, with an AT93C46D device attached via dspi2. The spi-gpio driver was used to allow the necessary non-byte-sized transfers. Signed-off-by: Cory Tusar <[email protected]> Tested-by: Chris Healy <[email protected]> Reviewed-by: Vladimir Zapolskiy <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

This commit adds support to the eeprom_93x46 driver allowing a GPIO line to function as a 'select' or 'enable' signal prior to accessing the EEPROM. Signed-off-by: Cory Tusar <[email protected]> Tested-by: Chris Healy <[email protected]> Reviewed-by: Vladimir Zapolskiy <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

Legacy AT24, AT25 EEPROMs are exported in sys so that only root can read the contents. The EEPROMs may contain sensitive information. Add a flag so the provide can indicate that NVMEM should also restrict access to root only. Signed-off-by: Andrew Lunn <[email protected]> Acked-by: Srinivas Kandagatla <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

Older drivers made an 'eeprom' file available in the /sys device directory. Have the NVMEM core provide this to retain backwards compatibility. Signed-off-by: Andrew Lunn <[email protected]> Acked-by: Srinivas Kandagatla <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

Add a regmap for accessing the EEPROM, and then use that with the NVMEM framework. Set the NVMEM config structure to enable backward, so that the 'eeprom' file in sys is provided by the framework. Signed-off-by: Andrew Lunn <[email protected]> Acked-by: Srinivas Kandagatla <[email protected]> Tested-by: Bartosz Golaszewski <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

The setup() callback is not used by any in kernel code. Remove it. Any new code which requires access to the eeprom can use the NVMEM API. Signed-off-by: Andrew Lunn <[email protected]> Acked-by: Srinivas Kandagatla <[email protected]> Acked-by: Wolfram Sang <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

Add a regmap for accessing the EEPROM, and then use that with the NVMEM framework. Enable backwards compatibility in the NVMEM config, so that the 'eeprom' file in sys is provided by the framework. Signed-off-by: Andrew Lunn <[email protected]> Acked-by: Srinivas Kandagatla <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

Add a regmap for accessing the EEPROM, and then use that with the NVMEM framework. Enable backward compatibility in the NVMEM config structure, so that the 'eeprom' file in sys is provided by the framework. Signed-off-by: Andrew Lunn <[email protected]> Acked-by: Srinivas Kandagatla <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

Now that the AT24 uses the NVMEM framework, replace the memory_accessor in the setup() callback with nvmem API calls. Signed-off-by: Andrew Lunn <[email protected]> Acked-by: Srinivas Kandagatla <[email protected]> Tested-by: Sekhar Nori <[email protected]> Acked-by: Wolfram Sang <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

ConfigFS lacked binary attributes up until now. This patch introduces support for binary attributes in a somewhat similar manner of sysfs binary attributes albeit with changes that fit the configfs usage model. Problems that configfs binary attributes fix are everything that requires a binary blob as part of the configuration of a resource, such as bitstream loading for FPGAs, DTBs for dynamically created devices etc. Look at Documentation/filesystems/configfs/configfs.txt for internals and howto use them. This patch is against linux-next as of today that contains Christoph's configfs rework. Signed-off-by: Pantelis Antoniou <[email protected]> [hch: folded a fix from Geert Uytterhoeven <[email protected]>] [hch: a few tiny updates based on review feedback] Signed-off-by: Christoph Hellwig <[email protected]>

The PowerNV PCI hotplug driver is going to use the OF changeset to manage the changed device sub-tree. This exports those OF changeset functions for that. Signed-off-by: Gavin Shan <[email protected]> Acked-by: Wolfram Sang <[email protected]> Tested-by: Wolfram Sang <[email protected]> Signed-off-by: Rob Herring <[email protected]>

If a driver PM runtime is disabled via sysfs, and the module is unloaded, PM runtime can't do anything to disable the device. Let's let the interconnect disable the device on BUS_NOTIFY_UNBOUND_DRIVER. Otherwise omap_device will produce and error on the following module reload. This can be easily tested with something like: # modprobe omap_hsmmc # echo on > /sys/devices/platform/68000000.ocp/4809c000.mmc/power/control # rmmod omap_hsmmc # modprobe omap_hsmmc Cc: Alan Stern <[email protected]> Cc: Nishanth Menon <[email protected]> Cc: Rafael J. Wysocki <[email protected]> Cc: Tero Kristo <[email protected]> Reported-by: Ulf Hansson <[email protected]> Acked-by: Kevin Hilman <[email protected]> Acked-by: Ulf Hansson <[email protected]> Signed-off-by: Tony Lindgren <[email protected]>

Add a runtime interface to using configfs for generic device tree overlay usage. With it its possible to use device tree overlays without having to use a per-platform overlay manager. Please see Documentation/devicetree/configfs-overlays.txt for more info. Changes since v5: - New style configfs. Changes since v4: - Loading fix for multiple overlays as found out by Geert Uytterhoeven <[email protected]> Changes since v3: - Fixed compilation on SPARC & Xtensa Changes since v2: - Removed ifdef CONFIG_OF_OVERLAY (since for now it's required) - Created a documentation entry - Slight rewording in Kconfig Changes since v1: - of_resolve() -> of_resolve_phandles(). Signed-off-by: Pantelis Antoniou <[email protected]> cfs-of

Signed-off-by: Pantelis Antoniou <[email protected]>

When disabling an omap device (not when removing the driver), the device is removed but the hwmod's linger. Fix the resource leak and the crash when calling omap_device_idle() after the device's omap data have been removed. Signed-off-by: Pantelis Antoniou <[email protected]>

Having an omap serial device without a serial aliases doesn't work. For now fallback to using the hwmod instance. Signed-off-by: Pantelis Antoniou <[email protected]>

When using DT the driver devm_kalloc's platform data and assigns them directly to the pdev->dev.platform variable. This is wrong since device de-registration expects the data to be kmalloc'ed instead, resulting in a crash. Fix by copying the platform data to a kmalloc buffer. Signed-off-by: Pantelis Antoniou <[email protected]>

90% of the usage of device node's full_name is printing it out in a kernel message. Preparing for the eventual delayed allocation introduce a custom printk format specifier that is both more compact and more pleasant to the eye. For instance typical use is: pr_info("Frobbing node %s\n", node->full_name); Which can be written now as: pr_info("Frobbing node %pO\n", node); More fine-grained control of formatting includes printing the name, flag, path-spec name, reference count and others, explained in the documentation entry. Signed-off-by: Pantelis Antoniou <[email protected]>

We are going to need the overlays to appear on sysfs with runtime global properties (like master enable) so turn them into kobjects. They have to be in sysfs so that people can have information about the overlays applied in the system, i.e. where their targets are and whether removal is possible. In a future more attributes can be added in a backwards compatible manner. Signed-off-by: Pantelis Antoniou <[email protected]>

A throw once master enable switch to protect against any further overlay applications if the administrator desires so. A kernel command line option is provided as well. Signed-off-by: Pantelis Antoniou <[email protected]>

Documentation ABI entry for overlays sysfs entries. Signed-off-by: Pantelis Antoniou <[email protected]>

Document the of_overlay_disable parameter. Signed-off-by: Pantelis Antoniou <[email protected]>

* A per overlay can_remove sysfs attribute that reports whether the overlay can be removed or not due to another overlapping overlay. * A target sysfs attribute listing the target of each fragment, in a group named after the name of the fragment. Signed-off-by: Pantelis Antoniou <[email protected]>

Documentation for the per-overlay attributes. Signed-off-by: Pantelis Antoniou <[email protected]>

A cape loader based on DT overlays and DT objects. This is the beaglebone cape manager which allows capes to be automatically probed and instantiated via means of a device tree overlay deduced from the part-number and version contained on the cape's EEPROM. The reference manual contains information about the specification and the contents of the EEPROM. http://beagleboard.org/static/beaglebone/latest/Docs/Hardware/BONE_SRM.pdf Documentation about the workings of the cape manager is located in Documentation/misc-devices/bone_capemgr.txt This driver is using the nvmem framework interface to retrieve the data stored on the baseboard and cape EEPROMs. Signed-off-by: Pantelis Antoniou <[email protected]>

Add beaglebone capemanager documentation entry. Signed-off-by: Pantelis Antoniou <[email protected]>

Bindings document for the beaglebone cape manager. Signed-off-by: Pantelis Antoniou <[email protected]>

Document the beaglebone's capemgr sysfs API Signed-off-by: Pantelis Antoniou <[email protected]>

Add me as the capemanager maintainer. Signed-off-by: Pantelis Antoniou <[email protected]>

Enable the cape manager on the beaglebone family of boards. Signed-off-by: Pantelis Antoniou <[email protected]>

Some applications require applying the same overlay to a different target according to some external condition (for instance depending on the slot a card has been inserted, the overlay target is different). The indirect target use requires using the new of_overlay_create_indirect() API which uses a text selector. The format requires the use of a target-indirect node as follows: fragment@0 { target-indirect { foo { target = <&foo_target>; }; bar { target = <&bar_target>; }; }; }; Calling of_overlay_create_indirect() with a "foo" argument selects the foo_target and so on. Signed-off-by: Pantelis Antoniou <[email protected]>

Add a unittest for the indirect overlay target case. Signed-off-by: Pantelis Antoniou <[email protected]>

Add a description of the indirect overlay method to the overlay documention file. Signed-off-by: Pantelis Antoniou <[email protected]>

The target facility of an overlay allows the target to be any point in the live kernel tree, since it usually that's required when creating overlays for internal SoC devices. The target ends up to be a single node in the tree. However when we're dealing with probeable busses this is a problem since the target node differs according to the bus the plugged device lies. Using an overlay creating method using a target root node allows us to use a single overlay for those cases. Signed-off-by: Pantelis Antoniou <[email protected]>

Add unittests for target-root based overlays. Signed-off-by: Pantelis Antoniou <[email protected]>

Add a description of the target root overlay method to the overlay documention file. Signed-off-by: Pantelis Antoniou <[email protected]>

Add an __of_node_dupv() private method and make __of_node_dup() use it. This is required for the subsequent changeset accessors which will make use of it. Signed-off-by: Pantelis Antoniou <[email protected]>

Changesets are very powerful, but the lack of a helper API makes using them cumbersome. Introduce a simple copy based API that makes things considerably easier. To wit, adding a property using the raw API. struct property *prop; prop = kzalloc(sizeof(*prop)), GFP_KERNEL); prop->name = kstrdup("compatible"); prop->value = kstrdup("foo,bar"); prop->length = strlen(prop->value) + 1; of_changeset_add_property(ocs, np, prop); while using the helper API of_changeset_add_property_string(ocs, np, "compatible", "foo,bar"); Signed-off-by: Pantelis Antoniou <[email protected]>

This probably misplaced (in drivers/misc) patch allows use of device tree overlays on the two kinds of probeable busses that count nowadays, PCI & USB. It does so by dynamically creating device nodes for the busses & devices that are probed and according to user-configuration applying an overlay when they appear. It is still a WIP but it's coming along nicely. Issues: Only PCI works for now, the generated bindings are not correct according to the openfirmware spec. Signed-off-by: Pantelis Antoniou <[email protected]>

Signed-off-by: Pantelis Antoniou <[email protected]>

https://groups.google.com/d/msg/beagleboard/634Xm1m3XA8/B028x1FzAyAJ Reported-by: Mark A. Yoder <[email protected]> Signed-off-by: Robert Nelson <[email protected]>

Added pin mux definitions for collision and carrier sense errors coming from the ethernet phy. Without these two signals the MAC ends up ignoring the errors detected by the PHY which end up causing a lower throughput problem when the phy is in half duplex mode such as connected through a hub. Fixes: 2ba3549 (ARM: dts: am335x-bone*: add DT for BeagleBone Black) Cc: Koen Kooi <[email protected]> Cc: Tom Rini <[email protected]> Cc: Kevin Hilman <[email protected]> Cc: <[email protected]> # v3.13+ Signed-off-by: Schuyler Patton <[email protected]> Signed-off-by: Felipe Balbi <[email protected]>

This is an adaption to v3.14.x of the original patch by Andrew Bradford <[email protected]> Some minor devm_* changes and DT support done by Pantelis Antoniou <[email protected]> for 3.8.x Signed-off-by: Robert Nelson <[email protected]>

Signed-off-by: Robert Nelson <[email protected]>

This patch was derived from 2 commits, but I removed the non-pinmux-helper portions and added the helper to the bb.org_defconfig: capemgr: Capemgr makefiles and Kconfig fragments. Introduce a cape loader using DT overlays and dynamic DT objects. Makefile and Kconfig fragments. Signed-off-by: Pantelis Antoniou <[email protected]> Conflicts: arch/arm/mach-omap2/Kconfig drivers/misc/Kconfig drivers/misc/Makefile And: Pinmux helper driver. That's just a hack to get a pinmux helper driver working. Define in the DT helper { compatible = "bone-pinmux-helper"; pinctrl-names = "default"; pinctrl-0 = <&helper_pins>; status = "okay"; };

Pinctrl already supports multiple states. Just make them visible.

devm_kfree warned out... why? no idea.

A gpio OF helper driver that allows configuration to be done via DT.

Signed-off-by: Charles Steinkuehler <[email protected]>

Signed-off-by: Jason Kridner <[email protected]>

This adds gpio and pinmux helpers to the majority of available expansion header pins based on the cape-universal work from Charles Steinkuehler making them userspace configurable. This is not a substitute for Capemgr as it doesn't perform the configuration based on cape detection, nor does it enable dynamic configuration of all types of peripherals that could be on a cape. It does, however, enable many developers to rapidly experiment with a lesser degree of complexity. Derived from: https://github.com/cdsteinkuehler/beaglebone-universal-io/blob/52461b52ef3203e648399c16c7e160c848a04b5c$ Signed-off-by: Jason Kridner <[email protected]> Cc: Charles Steinkuehler <[email protected]> Signed-off-by: Robert Nelson <[email protected]>

…new mode parameter is used to set the initial pinmux mode to something other than "default" or NULL, which is what happens currently. This allows enabling SoC hardware via device-tree which requires specific pinmux settings to function on boot, but still leaves the pinmux register under control of the bone-pinmux- helper driver meaning the pinmux setting can be changed at run time via user-mode access to sysfs. Signed-off-by: Charles Steinkuehler <[email protected]>

Signed-off-by: Robert Nelson <[email protected]>

BeagleBone DTS : Enable run-time pinmux for HDMI Add cape-universal-hdmi pin info to am335x-bone-common-universal.dtsi Edit hdmi dtsi include files to use new mode= setting to set HDMI mode at startup, leaving pinmux configurable at runtime. Signed-off-by: Charles Steinkuehler <[email protected]> Signed-off-by: Robert Nelson <[email protected]>

Signed-off-by: Adrian Remonda <[email protected]> Signed-off-by: Robert Nelson <[email protected]>

…FIG_EXPERIMENTAL has been removed with 3.9 Signed-off-by: Tobias MÃ¼ller <[email protected]>

Signed-off-by: Robert Nelson <[email protected]>

…SoCs Signed-off-by: Nathaniel Lewis <[email protected]>

Signed-off-by: Robert Nelson <[email protected]>

*) linux tree compatible formatting and commenting style. *) adds two additional count up/down modes. *) allows not hooking the interrupt handler, useful for frequency usage. Signed-off-by: Dick Hollenbeck <[email protected]>

Signed-off-by: Robert Nelson <[email protected]>

Hacked driver that has audio support. Use this temporarily until audio support can be added to the upstream adv7511 driver. Signed-off-by: Jason Kridner <[email protected]> [Remove slave hacks and use adv75xx compatible strings] Signed-off-by: Matt Porter <[email protected]>

Convert the driver over the the device model component framework, making use of the drm encoder/connector helpers. This allows adihdmi to be dynamically selected as an external encoder for drm drivers like tilcdc that support the DT graph binding which defines ports and remote-endpoints to attach external encoders. Also, this driver was modified by another developer to support audio and tweak some settings. Along the way it seems to have been reformatted to 4 space tabs which is hard to work with alongside the standard 8 space tabs in the kernel coding standard. As such, this is reformatted to standard 8 space tabs so it's a bit more readable. The component and audio support should be merged into the upstream driver so this adihdmi driver can be removed. Signed-off-by: Matt Porter <[email protected]>

Signed-off-by: Robert Nelson <[email protected]>

Adds a dts file for the Arrow BeagleBone Black Industrial board. This BBB variant differs in that it uses an industrial temp rated ADV7511W HDMI encoder rather than the NXP HDMI encoder on the tradtional BBB. Signed-off-by: Matt Porter <[email protected]>

Add a dts file for Olimex AM3352-SOM board. The board does not use the PMIC tps65217 and does not have many peripherals present in beaglebone. Thus, a specific dtsi file (am335x-som-common.dtsi) is needed. rcn-ee: drop ti,am335x-bone due to: davinci_mdio: dt: updated phy_id[0] from phy_mask[fffffffc] davinci_mdio: dt: updated phy_id[1] from phy_mask[fffffffc] #4.5.0-rc0 Use: olimex,am335x-olimex-som tps65217.dtsi gone Signed-off-by: Dimitar Gamishev <[email protected]> Signed-off-by: Vinicius Maciel <[email protected]>

Good news, BBGW born out.

Signed-off-by: Robert Nelson <[email protected]>

Rewritten using includes, v3.16.1 Signed-off-by: Dave Lambert <[email protected]> Signed-off-by: Robert Nelson <[email protected]>

Add support for the WL1835MOD cape. This cape conflicts with the eMMC and HDMI on board the BeagleBone Black. This change requires that the board be booted from the SD card slot by holding the user/boot button down at power on and reset. Signed-off-by: Eyal Reizer <[email protected]>

Signed-off-by: Robert Nelson <[email protected]>

Introduce serial8250_out_MCR() and serial8250_in_MCR() routines, that replace following calls: serial_out(port, UART_MCR, val) serial_port_out(up, UART_MCR, val) serial_in(port, UART_MCR) This patch is needed in order to integrate reading/writing of MCR signals via SERIAL_MCTRL_GPIO infrastructure later. CC: Peter Hurley <[email protected]> Signed-off-by: Yegor Yefremov <[email protected]>

mctrl_gpio_get_outputs() returns the state of following signals: RTS, DTR, OUT1, OUT2 Signed-off-by: Yegor Yefremov <[email protected]>

uart_handle_cts_change() should be called in IRQ locked state, hence use port->lock to disable interrupts. CC: Uwe Kleine-König <[email protected]> Signed-off-by: Yegor Yefremov <[email protected]>

Signed-off-by: Robert Nelson <[email protected]>

I have encountered the same issue(s) on A6A boards. I couldn't find a patch, so I wrote this patch to update the device tree in the davinci_mdio driver in the 3.15.1 tree, it seems to correct it. I would welcome any input on a different approach. https://groups.google.com/d/msg/beagleboard/9mctrG26Mc8/SRlnumt0LoMJ v4.1-rcX: added hack around CONFIG_OF_OVERLAY v4.2-rc3+: added if (of_machine_is_compatible("ti,am335x-bone")) so we do not break dual ethernet am335x devices Signed-off-by: Robert Nelson <[email protected]>

Signed-off-by: Robert Nelson <[email protected]>

4.4 TI Delta: RobertCNelson/ti-linux-kernel@98fcb19...ee87bb1 Signed-off-by: Robert Nelson <[email protected]>

Commits on Jul 15, 2016

dts: am335x-boneblack-wireless.dts: working

jadonk committed Jul 15, 2016

Configuration menu

View commit details

Copy full SHA for a13593c

Browse repository at this point

Copy the full SHA

a13593c View commit details

Browse the repository at this point in the history

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

4.4 bbbw dt updates #95

4.4 bbbw dt updates #95

Commits on May 5, 2016

Commits on Jul 15, 2016