Added CTAG face2|4 Audio Card support for BeagleBoard-X15 #97

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]>

This reverts commit 956b200.

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

This adds support for the Vitesse VSC8601 PHY. Generic functions are used for everything except interrupt handling. Signed-off-by: Mans Rullgard <[email protected]> Reviewed-by: Florian Fainelli <[email protected]> Signed-off-by: David S. Miller <[email protected]>

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

It's a common operation for device drivers to retrive the data member from of_device_id struct in their probe function. Most driver end up doing: const struct of_device_id *match; match = of_match_device(driver_of_match, &pdev->dev); driver->data = match->data; With the of_device_get_match_data helper function all this can done in one go. Signed-off-by: Joachim Eastwood <[email protected]> [robh: add missing inline to dummmy declaration] Signed-off-by: Rob Herring <[email protected]>

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]>

https://github.com/rcn-ee/meta-processor-sdk/blob/master/recipes-kernel/linux/files/dra7xx/cmem.dtsi Signed-off-by: Robert Nelson <[email protected]>

PRU IRAM addresses need to be masked before being handled to remoteproc. This is due to PRU Binutils' lack of separate address spaces for IRAM and DRAM. Signed-off-by: Dimitar Dimitrov <[email protected]>

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

This patch introduces regmap_get_max_register() function which would be used by the infrastructures like nvmem framework built on top of regmap. Signed-off-by: Srinivas Kandagatla <[email protected]> Signed-off-by: Mark Brown <[email protected]>

This patch introduces regmap_get_reg_stride() function which would be used by the infrastructures like nvmem framework built on top of regmap. Mostly this function would be used for sanity checks on inputs within such infrastructure. Signed-off-by: Srinivas Kandagatla <[email protected]> Signed-off-by: Mark Brown <[email protected]>

The beaglebone family of boards contain two I2C busses enabled. The first one with a baseboard identification EEPROM and a cape I2C bus. Signed-off-by: Pantelis Antoniou <[email protected]> Signed-off-by: Tony Lindgren <[email protected]>

Mark (and unmark) device nodes with the POPULATE flag as appropriate. This is required to avoid multi probing when using I2C and device overlays containing a mux. This patch is also more careful with the release of the adapter device which caused a deadlock with muxes, and does not break the build on !OF since the node flag accessors are not defined then. Signed-off-by: Pantelis Antoniou <[email protected]> Signed-off-by: Wolfram Sang <[email protected]>

This patch adds just providers part of the framework just to enable easy review. Up until now, NVMEM drivers like eeprom were stored in drivers/misc, where they all had to duplicate pretty much the same code to register a sysfs file, allow in-kernel users to access the content of the devices they were driving, etc. This was also a problem as far as other in-kernel users were involved, since the solutions used were pretty much different from on driver to another, there was a rather big abstraction leak. This introduction of this framework aims at solving this. It also introduces DT representation for consumer devices to go get the data they require (MAC Addresses, SoC/Revision ID, part numbers, and so on) from the nvmems. Having regmap interface to this framework would give much better abstraction for nvmems on different buses. Signed-off-by: Maxime Ripard <[email protected]> [Maxime Ripard: intial version of eeprom framework] Signed-off-by: Srinivas Kandagatla <[email protected]> Tested-by: Stefan Wahren <[email protected]> Tested-by: Philipp Zabel <[email protected]> Tested-by: Rajendra Nayak <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

This patch adds just consumers part of the framework just to enable easy review. Up until now, nvmem drivers were stored in drivers/misc, where they all had to duplicate pretty much the same code to register a sysfs file, allow in-kernel users to access the content of the devices they were driving, etc. This was also a problem as far as other in-kernel users were involved, since the solutions used were pretty much different from on driver to another, there was a rather big abstraction leak. This introduction of this framework aims at solving this. It also introduces DT representation for consumer devices to go get the data they require (MAC Addresses, SoC/Revision ID, part numbers, and so on) from the nvmems. Having regmap interface to this framework would give much better abstraction for nvmems on different buses. Signed-off-by: Maxime Ripard <[email protected]> [Maxime Ripard: intial version of the framework] Signed-off-by: Srinivas Kandagatla <[email protected]> Tested-by: Stefan Wahren <[email protected]> Tested-by: Philipp Zabel <[email protected]> Tested-by: Rajendra Nayak <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

This patch adds read/write apis which are based on nvmem_device. It is common that the drivers like omap cape manager or qcom cpr driver to access bytes directly at particular offset in the eeprom and not from nvmem cell info in DT. These driver would need to get access to the nvmem directly, which is what these new APIS provide. These wrapper apis would help such users to avoid code duplication in there drivers and also avoid them reading a big eeprom blob and parsing it internally in there driver. Signed-off-by: Srinivas Kandagatla <[email protected]> Tested-by: Stefan Wahren <[email protected]> Tested-by: Philipp Zabel <[email protected]> Tested-by: Rajendra Nayak <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

This patch adds bindings for simple nvmem framework which allows nvmem consumers to talk to nvmem providers to get access to nvmem cell data. Signed-off-by: Maxime Ripard <[email protected]> [Maxime Ripard: intial version of eeprom framework] Signed-off-by: Srinivas Kandagatla <[email protected]> Tested-by: Philipp Zabel <[email protected]> Tested-by: Rajendra Nayak <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

This patch add basic how-to and api summary documentation for simple NVMEM framework. Signed-off-by: Srinivas Kandagatla <[email protected]> Tested-by: Philipp Zabel <[email protected]> Tested-by: Rajendra Nayak <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

This patch adds QFPROM support driver which is used by other drivers like thermal sensor and cpufreq. On MSM parts there are some efuses (called qfprom) these fuses store things like calibration data, speed bins.. etc. Drivers like cpufreq, thermal sensors would read out this data for configuring the driver. Signed-off-by: Srinivas Kandagatla <[email protected]> Reviewed-by: Stephen Boyd <[email protected]> Tested-by: Philipp Zabel <[email protected]> Tested-by: Rajendra Nayak <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

This patch adds bindings for qfprom found in QCOM SOCs. QFPROM driver is based on simple nvmem framework. Signed-off-by: Srinivas Kandagatla <[email protected]> Reviewed-by: Stephen Boyd <[email protected]> Tested-by: Philipp Zabel <[email protected]> Tested-by: Rajendra Nayak <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

Now that we have the nvmem framework, we can consolidate the common driver code. Move the driver to the framework, and hopefully, it will fix the sysfs file creation race. Signed-off-by: Maxime Ripard <[email protected]> [srinivas.kandagatla: Moved to regmap based EEPROM framework] Signed-off-by: Srinivas Kandagatla <[email protected]> Tested-by: Philipp Zabel <[email protected]> Tested-by: Rajendra Nayak <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

Add the devicetree bindings for the Freescale Vybrid On-Chip OTP driver. Signed-off-by: Sanchayan Maity <[email protected]> Acked-by: Srinivas Kandagatla <[email protected]> Signed-off-by: Srinivas Kandagatla <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

The patch adds support for the On Chip One Time Programmable Peripheral (OCOTP) on the Vybrid platform. Signed-off-by: Sanchayan Maity <[email protected]> Acked-by: Srinivas Kandagatla <[email protected]> Signed-off-by: Srinivas Kandagatla <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

This patch documents the i.MX6 OCOTP device tree binding. Signed-off-by: Philipp Zabel <[email protected]> Signed-off-by: Srinivas Kandagatla <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

This driver handles the i.MX On-Chip OTP Controller found in i.MX6Q/D, i.MX6S/DL, i.MX6SL, and i.MX6SX SoCs. Currently it just returns the values stored in the shadow registers. Signed-off-by: Philipp Zabel <[email protected]> Acked-by: Srinivas Kandagatla <[email protected]> Signed-off-by: Srinivas Kandagatla <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

This patch adds the devicetree bindings for the Freescale MXS On Chip OTP driver. Signed-off-by: Stefan Wahren <[email protected]> Signed-off-by: Srinivas Kandagatla <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

This patch brings read-only support for the On-Chip OTP cells in the i.MX23 and i.MX28 processor. The driver implements the new NVMEM provider API. Signed-off-by: Stefan Wahren <[email protected]> Reviewed-by: Marek Vasut <[email protected]> Signed-off-by: Srinivas Kandagatla <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

This patch add the bindings document of rockchip eFuse driver. Cc: Srinivas Kandagatla <[email protected]> Cc: Heiko Stuebner <[email protected]> Signed-off-by: ZhengShunQian <[email protected]> Signed-off-by: Srinivas Kandagatla <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

There are some SoC specified values store in eFuse, such as the cpu_leakage and cpu_version, this driver can expose these values to /sys base on nvmem. Signed-off-by: Caesar Wang <[email protected]> Signed-off-by: ZhengShunQian <[email protected]> Acked-by: Srinivas Kandagatla <[email protected]> Signed-off-by: Srinivas Kandagatla <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

Signed-off-by: Fengguang Wu <[email protected]> Acked-by: Srinivas Kandagatla <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

The position to read/write must be less than max register size. Signed-off-by: ZhengShunQian <[email protected]> Acked-by: Srinivas Kandagatla <[email protected]> Signed-off-by: Srinivas Kandagatla <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

It's pointless to test (cell->bit_offset || cell->bit_offset). nvmem_shift_read_buffer_in_place() should be called when (cell->bit_offset || cell->nbits). Signed-off-by: Axel Lin <[email protected]> Signed-off-by: Srinivas Kandagatla <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

A tmp buffer is allocated if cell->bit_offset || cell->nbits. So the tmp buffer needs to be freed at the same condition to avoid leak. Signed-off-by: Axel Lin <[email protected]> Signed-off-by: Srinivas Kandagatla <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

The sunxi_sid driver doesn't check for kmalloc return status before derefencing the returned pointer, which could lead to a NULL pointer dereference if kmalloc failed. Check for its return code to make sure it deosn't happen. Reported-by: Dan Carpenter <[email protected]> Signed-off-by: Maxime Ripard <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

As required by many providers like at24/at25/mxs-ocotp/qfprom and may be other providers would want to allow root-only to read the nvmem content. So making the defaults to be root-only access would address the request and also provide flexibility to providers to specify there own permissions on top of the root-only using the perm flag in nvmem_config. Making this dynamic did cut down lot of static binary attributes in the code. Signed-off-by: Srinivas Kandagatla <[email protected]>

This patch sets the actual size of binary file to the nvmem size. Previously this was not possible as the core was using the static global data structures for attributes. Signed-off-by: Srinivas Kandagatla <[email protected]>

This patch adds perm variable to nvmem_config structure which will allow providers to specify the permissions required for the sysfs binary file. This permission is applied on top of root-only access permissions set by the core. Signed-off-by: Srinivas Kandagatla <[email protected]>

Hi Robert, Srinivas, With the current -bone kernels and my own dtb I found these weird perms: ---------x 1 root root 4097 Oct 5 03:25 /sys/bus/nvmem/devices/at24-0/nvmem I traced the problem to a bug in nvmem triggered by the fact I had marked the EEPROM readonly (since it is). Patch attached. -- >8 -- Signed-off-by: Matthijs van Duin <[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. Changes since V3: * Rebase against 4.0-rc Changes since V2: * Spelling checkpatch fixes. Changes since V1: * Uses vmalloc instead of kmalloc. * Renamed bin_attribute members. * Implemented maximum limit of attribute. * Cosmetic, whitespace & checkpatch fixes. Signed-off-by: Pantelis Antoniou <[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 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]>

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

Removing any omap device always resulted in a crash; turns out BUS_NOTIFY_DEL_DEVICE is not the last notifier event sent in the course of removing the device, the correct event is BUS_NOTIFY_UNBOUND_DRIVER, which still is not the right place to perform the cleanup. 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. 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. Signed-off-by: Pantelis Antoniou <[email protected]>

The two default overlay attributes are: * A targets sysfs attribute listing the targets of the installed overlay. The targets list the path on the kernel's device tree where each overlay fragment is applied to * A per overlay can_remove sysfs attribute that reports whether the overlay can be removed or not due to another overlapping overlay. Signed-off-by: Pantelis Antoniou <[email protected]>

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

For DT and in-kernel users there is no interface to the at24 EEPROMs so provide an NVMEM framework interface. This allows us to use AT24 based EEPROMs and reference them from within the DT tree. 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 EEPROM 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: Robert Nelson <[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]>

Signed-off-by: Robert Nelson <[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]>

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

updated dtb to work with cape manager

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]>

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]>

Remove tilcdc slave support for tda998x driver. The tilcdc slave support would conflicts with componentized use of tda998x. Signed-off-by: Jyri Sarha <[email protected]> Acked-by: Tomi Valkeinen <[email protected]>

Add support for an external compontised DRM encoder. The external encoder can be connected to tilcdc trough device tree graph binding. The binding document for tilcdc has been updated. The current implementation supports only tda998x encoder. To be able to filter out the unsupported video modes the tilcdc driver needs to hijack the external connectors helper functions. The tilcdc installes new helper functions that are otherwise identical to orignals, but the mode_valid() call-back check the mode first localy, before calling the original call-back. The tilcdc dirver restores the original helper functions before it is unbound from the external device. I got the idea and some lines of code from Jean-Francois Moine's "drm/tilcdc: Change the interface with the tda998x driver"-patch. Signed-off-by: Jyri Sarha <[email protected]> Acked-by: Tomi Valkeinen <[email protected]>

…upport Adds a CONFIG_DRM_TILCDC_SLAVE_COMPAT module for "ti,tilcdc,slave" node conversion. The implementation is in tilcdc_slave_compat.c and it uses tilcdc_slave_compat.dts as a basis for creating a DTS overlay. The DTS overlay adds an external tda998x encoder to tilcdc that corresponds to the old tda998x based slave encoder. Signed-off-by: Jyri Sarha <[email protected]> Acked-by: Tomi Valkeinen <[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]>

Use new binding for the external tda19988 HDMI encoder. Signed-off-by: Jyri Sarha <[email protected]> Signed-off-by: Tony Lindgren <[email protected]> [Resolved conflicts merging into beagleboard kernel] Signed-off-by: Matt Porter <[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] Signed-off-by: Dimitar Gamishev <[email protected]> Signed-off-by: Vinicius Maciel <[email protected]>

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

Good news, BBGW born out.

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

distinguish BBG and BBGW

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

* Removed btaudio * BT_EN moved from GPIO1_28 to GPIO0_28 * WL_IRQ moved from GPIO0_27 to GPIO0_29 * WL_EN moved from GPIO0_26 to GPIO3_9 * Cape_Buffer_EN moved from GPIO1_29 to GPIO3_10 * Moved MMC2 to different pins (recovered from MII

…e Tree IDs for AD193X SPI

… files

…rates in i2s mode.

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]>

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

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

4.1 TI Delta: RobertCNelson/ti-linux-kernel@5b7dbf2...c6b46b7 Signed-off-by: Robert Nelson <[email protected]>

Commits on Oct 3, 2016

Added support for BeagleBoard-X15

henrix committed Oct 3, 2016

Configuration menu

View commit details

Copy full SHA for b9d7dd7

Browse repository at this point

Copy the full SHA

b9d7dd7 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

Added CTAG face2|4 Audio Card support for BeagleBoard-X15 #97

Added CTAG face2|4 Audio Card support for BeagleBoard-X15 #97

Commits on Aug 10, 2016

Commits on Oct 3, 2016

Added CTAG face2|4 Audio Card support for BeagleBoard-X15 #97

Are you sure you want to change the base?

Added CTAG face2|4 Audio Card support for BeagleBoard-X15 #97

Commits on Aug 10, 2016

Commits on Oct 3, 2016