6 Commits

Author	SHA1	Message	Date
Olivier Houchard	cbfebd9a6e	The only remaining offender that used ti_chip() without checking for ... compatibility first was the gpio code, so change that, and re-assert that the TI chip is a known chip	2016-11-19 15:43:22 +00:00
Olivier Houchard	80d2898d0f	Don't panic if it's not a TI chip, this code can be called when it is not.	2016-11-19 15:35:40 +00:00
Olivier Houchard	31a2ddf253	Guess the TI chip based on the PLATFORM infos, instead of relying on the ... kernel config file.	2016-11-18 23:48:20 +00:00
Andrew Turner	56d8b96cbc	Start removing the omap3 support. In base it was only ever a header and a ... few changes to drivers, no kernel config was added. As the SoCs are quite old and the code is unmaintained start the process of removing support by deleting the header file and code that depends on it along with the macro SOC_OMAP3. Other Ti SoCs shouldn't be affected, other than for us to have less code to maintain. Differential Revision: https://reviews.freebsd.org/D936 Reviewed by: rpaulo, loos	2014-10-13 15:35:08 +00:00
Oleksandr Tymoshenko	5c79e1dd7d	- Identify more devices for OMAP4 SoC (up to OMAP4470) ... - Whitespace fixes	2013-01-07 23:30:53 +00:00
Oleksandr Tymoshenko	e53470fee3	Merging of projects/armv6, part 10 ... - Support for Texas Instruments SoCs: - AM335x - OMAP4 - Kernel configs, DTS for Beaglebone and Pandaboard Submitted by: Ben Gray, Damjan Marion	2012-08-15 06:31:32 +00:00