Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

When compiling a kernel without CONFIG_MULTI_CACHE enabled the
dma access functions end up not being exported. Fix it.

Signed-off-by: Pantelis Antoniou <panto@antoniou-consulting.com>

Add the node into the am33xx.dtsi file for the SGX GPU
that is found in some variants of the SoC.

Signed-off-by: Darren Etheridge <detheridge@ti.com>

Use pdata_quirks to provide platform data to the sgx driver.
The data that is provided includes:

1) Function pointers for the driver to use to reset the h/w block.
2) The reset name that matches with what is used in hwmod.

Signed-off-by: Darren Etheridge <detheridge@ti.com>

Update the DMA pointers during the pan display ioctl.  Borrowed from
da8xx_fb.c update the scanout buffers immediately so the DMA ping/pong
doesn't end up out of sync with what we really want it to DMA.

Signed-off-by: Darren Etheridge <detheridge@ti.com>

Add a vsync callback registration API that is identical to what was done
for da8xx-fb.c.

Need to find if there is a better way using the DRM infrastructure from
kernel space.  Either that or change the userspace window manager stuff in
the gpu libraries to make use of the DRM provided syncronization
mechanisms.

Signed-off-by: Darren Etheridge <detheridge@ti.com>

Increase the size of the buffer that is created in the fbdev emulation
helpers.  And fill in the var structure with the amount that was allocated.

Signed-off-by: Darren Etheridge <detheridge@ti.com>

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

todo: we shouldn't update both phy_id's as this could be breaking dual ethernet am335x devices

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

The cpsw device runs at 100/10mbits. Deferring a read for 96k
wipes out the dcache thrice over. It is better to take more interrupts
as they come, at 100mbit.

IoT devices such as the beaglebone black come with a default PHY
that can only do 100Mbit, and a fairly large tx ring. BQL moderates
the effect of that considerably when saturating the network at that
speed.

Tested on a beaglebone black.

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

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 <eyalr@ti.com>

rcn-ee: v4.1-rc4: dropped: system-power-controller

Rewritten using includes, v3.16.1

Signed-off-by: Dave Lambert <dave@lambsys.com>
Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

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: 2ba35493

 (ARM: dts: am335x-bone*: add DT for BeagleBone Black)
Cc: Koen Kooi <koen@dominion.thruhere.net>
Cc: Tom Rini <trini@ti.com>
Cc: Kevin Hilman <khilman@linaro.org>
Cc: <stable@vger.kernel.org> # v3.13+
Signed-off-by: Schuyler Patton <spatton@ti.com>
Signed-off-by: Felipe Balbi <balbi@ti.com>

https://groups.google.com/d/msg/beagleboard/634Xm1m3XA8/B028x1FzAyAJ



Reported-by: Mark A. Yoder <mark.a.yoder@gmail.com>
Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

Fixes: http://bugs.elinux.org/issues/143



Entering RTC-only sleep is only properly supported on early prototypes series
(pre-A6) of the BeagleBone Black.  Since rev (A6A), which include all production
versions, it is not support at due to.

(rev A6) enable of the 3v3b regulator moved from LDO2 to LDO4 (3v3a)
side-effect: 3v3b rail remains on in sleep-mode (also in off-mode when battery-powered)

(rev A6A) am335x vdds supply moved from LDO3 to LDO1
side-effect: vdds remains supplied in sleep-mode

Reported-by: Matthijs van Duin <matthijsvanduin@gmail.com>
Tested-by: Matthijs van Duin <matthijsvanduin@gmail.com>
Signed-off-by: Robert Nelson <robertcnelson@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>
Cc: Felipe Balbi <balbi@ti.com>
Cc: Johan Hovold <johan@kernel.org>

Enable the cape manager on the beaglebone family of boards.

Signed-off-by: Pantelis Antoniou <pantelis.antoniou@konsulko.com>

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 <pantelis.antoniou@konsulko.com>

Document the beaglebone's capemgr sysfs API

Signed-off-by: Pantelis Antoniou <pantelis.antoniou@konsulko.com>

Bindings document for the beaglebone cape manager.

Signed-off-by: Pantelis Antoniou <pantelis.antoniou@konsulko.com>

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

Signed-off-by: Pantelis Antoniou <pantelis.antoniou@konsulko.com>

In kernel users need to access the EEPROM using the i2c_client
interface. Extend at24 to use it via the command interface.

Signed-off-by: Pantelis Antoniou <pantelis.antoniou@konsulko.com>

We need those to be visible even when compiling with CONFIG_OF
disabled, since even the empty of_node_*_flag() method use the
flag.

Signed-off-by: Pantelis Antoniou <pantelis.antoniou@konsulko.com>

Documentation ABI entry for overlays sysfs entries.

Signed-off-by: Pantelis Antoniou <pantelis.antoniou@konsulko.com>

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 <pantelis.antoniou@konsulko.com>

A throw once master enable switch to protect against any
further overlay applications if the administrator desires so.

Signed-off-by: Pantelis Antoniou <pantelis.antoniou@konsulko.com>

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 <pantelis.antoniou@konsulko.com>

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 <pantelis.antoniou@konsulko.com>

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 <pantelis.antoniou@konsulko.com>

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 <pantelis.antoniou@konsulko.com>

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 <pantelis.antoniou@konsulko.com>