Preparation for getting the display and sound (ALSA) to work on 3.10 #20
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ering it." This reverts commit e24b69a.
Change-Id: I0785351c510c7ef4121fc5a1bc53f9b8e8ad2561
Change-Id: I571e6c6da328cf046bf193bba8a386e3ea2ec74c
Change-Id: If0e9e8987e6d0ee1a401e28601cb0735957c9b71
This fixed timing problems in 3.0 - the commit there was: bde0636 Change-Id: I46cf4084301ae88a755888c188595fd4089f6426
This fixes commit 998e582. Change-Id: I40d816df10932c20b664e42b43248fb2052028b1
It's enabled on 2.6.32 and 3.0 and seems to have a positive (side) effect on the display communication (stability). Change-Id: Ic9d1637b850b883baca9e730bd187cbebfb0954a
Regulators are optional (they must not exist). On Defy we do not have a
bridge regulator. If a regulator was missing the NULL regulator was
passed to regulator_{enable,disable}, which resulted in a crash.
So check the regulator before enabling it.
Change-Id: Ie4aeba4ed0d9b2cc69d9eb9d7070ff9040db1e01
The main changes are: * We are reading the display's "supplier ID" upon initialization as we need it for the TEAR_SCANLINE value (which depends on the supplier). * Reading the panel ID fails sometimes, so we're ignoring the error. * Changed _minnow_panel_enable_te to match what the 3.0 panel-mapphone driver does. Change-Id: I26b1aeca5111617d347d45bdb91e7acda081ea9f
Change-Id: I00a7825f3f975d72a3e984a135a5a31f2e37a0b3
Change-Id: I66c0d0074e7cf01d61977724b2b7ab7fa14fe3e0
Change-Id: I4dc38ea9a585f2ec088ccff3b80f2396c6f777b7
The cpu_dai_names were not known which caused card registration to fail. After motsnd_dais was registered with the kernel there were still some errors regarding "omap-mcbsp-dai.1" and "omap-mcbsp-dai.2" left. Thus those were converted to use cpu_of_node instead of cpu_dai_name (similar to how it's implemented in sound/soc/omap/omap-twl4030.c). Change-Id: I2a7f8853aff1d48043818016ba5182b27d5712c2
Change-Id: I2d27a733914756fb04fd0926f0402b24e6326119
Change-Id: I3c0c19f8b43633707bc623293843cff636a7c3d7
Change-Id: I35831d228a5c06c933af289b6f07f34b9caa7519
Change-Id: I02b358ac091ad42132b643b6544502092cee08e4
…into 3.10-defy Conflicts: arch/arm/boot/dts/dtb_list Change-Id: Id241520bb4dea264b75d382a8e404ff61a8a390d
Quarx2k
added a commit
that referenced
this pull request
Jan 16, 2015
Preparation for getting the display and sound (ALSA) to work on 3.10
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The ALSA module loads fine, but I have not tested it.
The display still requires some DSS/DSI tweaks (or at least some config changes for the display in panel-mapphone), but after those are done it should work fine as well.