No description
  • C 96.9%
  • Assembly 0.9%
  • Rust 0.6%
  • Shell 0.6%
  • Python 0.5%
  • Other 0.3%
Find a file
Olof Johansson 9604ff923c Start using ti-sysc with device tree data for omap4 l4 devices
With ti-sysc driver working for most use cases, we can start converting
 the omap variant SoCs to use device tree data for the interconnect target
 modules instead of the legacy hwmod platform data.
 
 We start with omap4 l4 devices excluding the ones that still depend on
 a reset controller driver like DSP MMU. And we don't yet convert the l4
 ABE instance as that needs a bit more work.
 
 We also add a proper interconnect hierarchy for the devices while at it
 to make further work on genpd easier and to avoid most deferred probe
 issues.
 
 At this point we are not dropping any platform data, and we initially
 still use it to validate the dts data. Then in later merge cycles we
 can start dropping the related platform data.
 -----BEGIN PGP SIGNATURE-----
 
 iQJFBAABCAAvFiEEkgNvrZJU/QSQYIcQG9Q+yVyrpXMFAltS0McRHHRvbnlAYXRv
 bWlkZS5jb20ACgkQG9Q+yVyrpXPzMRAAzU9qSt0HLJfP8P+8iHX3Lm6TJgslDNqP
 tOkifKoL1ELfieiJhcNfMTHhXwgwzYLhjHV+YuVyBKwMdiaJmkP9P7V3SGTEwX3c
 shAdK/+OsFJLpqXSZZqi2VApfGCjHJULICiDtalbNRYUyrZ6q9fm0C5nFxa6gH9z
 ZIrURQClfHYlPFUIQW+LBvv3oUkV5JxTn8DksOlF1MvqMqxgVYSbcZ032mEowuNG
 4j1mUk6ZMcKHmWhKpR2iGj3DGhDjvJGJ1J45WZViN7/Vbct41YLeJ9lSNLY+60R7
 6KdxoBM1G/G01t73wcoQrSReIuk7NV4lx2H1z1KxuWYMnATCBOgPg1Ug82PdkGdP
 EBMilB30rPhi/RQFKmhVYymHSn7falnUrE3CfErOGshyhdywdzdHCohSQZjizdjc
 npW46R0XhQjBkY8+JQjAliPNa6JvMlilDd9dKFaucL5pFd35QDn/6NQ7rQu8EIWM
 QpANfOEU2yLQ2m6GFUVz5JOwLojyD3LEKv5HkZRLXd5CzLrn2uW/TyrICIBp8/Pv
 bNQhtYaMm6T8407zMjUWGyCqiY0rDuAr6mLtY8JpHgbBMTL8hssmpfSFQW69o0KI
 ciWOu/KYVetl8nUodVobWY3rkpirHv2WqOU+9AjeiXqO+147HqzUteHV9ZpYRHS0
 tSU6+383Jkc=
 =ATsi
 -----END PGP SIGNATURE-----

Merge tag 'omap-for-v4.19/dt-pt3-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into next/dt

Start using ti-sysc with device tree data for omap4 l4 devices

With ti-sysc driver working for most use cases, we can start converting
the omap variant SoCs to use device tree data for the interconnect target
modules instead of the legacy hwmod platform data.

We start with omap4 l4 devices excluding the ones that still depend on
a reset controller driver like DSP MMU. And we don't yet convert the l4
ABE instance as that needs a bit more work.

We also add a proper interconnect hierarchy for the devices while at it
to make further work on genpd easier and to avoid most deferred probe
issues.

At this point we are not dropping any platform data, and we initially
still use it to validate the dts data. Then in later merge cycles we
can start dropping the related platform data.

* tag 'omap-for-v4.19/dt-pt3-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap:
  ARM: dts: omap4: Add l4 ranges for 4460
  ARM: dts: omap4: Move l4 child devices to probe them with ti-sysc
  ARM: dts: omap4: Probe watchdog 3 with ti-sysc
  ARM: dts: omap4: Add l4 interconnect hierarchy and ti-sysc data
  dt-bindings: Update omap l4 binding for optional registers

Signed-off-by: Olof Johansson <olof@lixom.net>
History 2018-07-25 23:54:31 -07:00
arch
block
certs
crypto
Documentation
drivers
firmware
fs
include
init
ipc
kernel
lib
LICENSES
mm
net
samples
scripts
security
sound
tools
usr
virt
.clang-format
.cocciconfig
.get_maintainer.ignore
.gitattributes
.gitignore
.mailmap
COPYING
CREDITS
Kbuild
Kconfig
MAINTAINERS
Makefile
README

Linux kernel
============

There are several guides for kernel developers and users. These guides can
be rendered in a number of formats, like HTML and PDF. Please read
Documentation/admin-guide/README.rst first.

In order to build the documentation, use ``make htmldocs`` or
``make pdfdocs``.  The formatted documentation can also be read online at:

    https://www.kernel.org/doc/html/latest/

There are various text files in the Documentation/ subdirectory,
several of them using the Restructured Text markup notation.
See Documentation/00-INDEX for a list of what is contained in each file.

Please read the Documentation/process/changes.rst file, as it contains the
requirements for building and running the kernel, and information about
the problems which may result by upgrading your kernel.