* Multiple issues with omap4 panda es in linux next
@ 2013-04-19 17:13 Tony Lindgren
2013-04-19 17:41 ` Santosh Shilimkar
` (4 more replies)
0 siblings, 5 replies; 27+ messages in thread
From: Tony Lindgren @ 2013-04-19 17:13 UTC (permalink / raw)
To: linux-arm-kernel
Hi all,
Here's a list of breakage I've noticed so far while trying to
use linux next on my pandaboard es. Probably similar issues exist
on other boards as well.
Ideally we would not have any breakage by the merge window, so
let's try to get these fixed ASAP:
1. Serial console broken on panda es booting with DT
The symptoms are dmesg output stopping after few lines
and only continuing after pressing a key. Does not seem to
happen on blaze with DT for some reason. And does not happen
on panda es with legacy booting.
2. MUSB fails with legacy booting and DT on panda es
With both legacy and DT booting I get something like:
HS USB OTG: no transceiver configured
musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517
3. DSS fails with DT booting
Works with legacy booting but fails with DT. I'm almost certain
the DT booting was working last week or so?
This is what I now get with DT booting:
omapdss DSI error: can't get VDDS_DSI regulator
omapdss HDMI error: can't get VDDA_HDMI_DAC regulator
omapdss HDMI error: device hdmi init failed: -517
omapdss CORE error: driver probe failed: -22
...
4. WLAN with wl12xx fails with both legacy and DT booting
No real output here with the legacy mode, just the usual
using pinctrl dummy state warning.
Regards,
Tony
^ permalink raw reply [flat|nested] 27+ messages in thread* Multiple issues with omap4 panda es in linux next 2013-04-19 17:13 Multiple issues with omap4 panda es in linux next Tony Lindgren @ 2013-04-19 17:41 ` Santosh Shilimkar 2013-04-19 17:44 ` Tony Lindgren 2013-04-22 7:49 ` Felipe Balbi ` (3 subsequent siblings) 4 siblings, 1 reply; 27+ messages in thread From: Santosh Shilimkar @ 2013-04-19 17:41 UTC (permalink / raw) To: linux-arm-kernel On Friday 19 April 2013 10:43 PM, Tony Lindgren wrote: > Hi all, > > Here's a list of breakage I've noticed so far while trying to > use linux next on my pandaboard es. Probably similar issues exist > on other boards as well. > > Ideally we would not have any breakage by the merge window, so > let's try to get these fixed ASAP: > > 1. Serial console broken on panda es booting with DT > > The symptoms are dmesg output stopping after few lines > and only continuing after pressing a key. Does not seem to > happen on blaze with DT for some reason. And does not happen > on panda es with legacy booting. > This one is known and reported on list along with fix patches and later pull request [1]. Unfortunately with all the testing and everything and patches have been on the list for quite some time, feedback on one of the patch received was after pull request and then there was no further clarification. That series address the same exact issue you have mentioned above. Regards, Santosh [1] http://patchwork.ozlabs.org/patch/229269/ ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-19 17:41 ` Santosh Shilimkar @ 2013-04-19 17:44 ` Tony Lindgren 2013-04-19 17:53 ` Santosh Shilimkar 0 siblings, 1 reply; 27+ messages in thread From: Tony Lindgren @ 2013-04-19 17:44 UTC (permalink / raw) To: linux-arm-kernel * Santosh Shilimkar <santosh.shilimkar@ti.com> [130419 10:43]: > On Friday 19 April 2013 10:43 PM, Tony Lindgren wrote: > > Hi all, > > > > Here's a list of breakage I've noticed so far while trying to > > use linux next on my pandaboard es. Probably similar issues exist > > on other boards as well. > > > > Ideally we would not have any breakage by the merge window, so > > let's try to get these fixed ASAP: > > > > 1. Serial console broken on panda es booting with DT > > > > The symptoms are dmesg output stopping after few lines > > and only continuing after pressing a key. Does not seem to > > happen on blaze with DT for some reason. And does not happen > > on panda es with legacy booting. > > > This one is known and reported on list along with fix patches and > later pull request [1]. > > Unfortunately with all the testing and everything and patches have > been on the list for quite some time, feedback on one of the patch > received was after pull request and then there was no further > clarification. That series address the same exact issue you have > mentioned above. OK thanks. I think Paul picked some of those and the plan was to update the branch? Which one(s) should go into v3.10 as fixes? Regards, Tony > [1] http://patchwork.ozlabs.org/patch/229269/ ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-19 17:44 ` Tony Lindgren @ 2013-04-19 17:53 ` Santosh Shilimkar 2013-04-19 18:18 ` Tony Lindgren 0 siblings, 1 reply; 27+ messages in thread From: Santosh Shilimkar @ 2013-04-19 17:53 UTC (permalink / raw) To: linux-arm-kernel On Friday 19 April 2013 11:14 PM, Tony Lindgren wrote: > * Santosh Shilimkar <santosh.shilimkar@ti.com> [130419 10:43]: >> On Friday 19 April 2013 10:43 PM, Tony Lindgren wrote: >>> Hi all, >>> >>> Here's a list of breakage I've noticed so far while trying to >>> use linux next on my pandaboard es. Probably similar issues exist >>> on other boards as well. >>> >>> Ideally we would not have any breakage by the merge window, so >>> let's try to get these fixed ASAP: >>> >>> 1. Serial console broken on panda es booting with DT >>> >>> The symptoms are dmesg output stopping after few lines >>> and only continuing after pressing a key. Does not seem to >>> happen on blaze with DT for some reason. And does not happen >>> on panda es with legacy booting. >>> >> This one is known and reported on list along with fix patches and >> later pull request [1]. >> >> Unfortunately with all the testing and everything and patches have >> been on the list for quite some time, feedback on one of the patch >> received was after pull request and then there was no further >> clarification. That series address the same exact issue you have >> mentioned above. > > OK thanks. I think Paul picked some of those and the plan was > to update the branch? Which one(s) should go into v3.10 as fixes? > Main in that series was to handle driver sysc handling withing hwmod layer and that is where the series got stuck [2]. Without that support other patches won't fix the issue. > >> [1] http://patchwork.ozlabs.org/patch/229269/ [2] https://patchwork.kernel.org/patch/2166931/ ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-19 17:53 ` Santosh Shilimkar @ 2013-04-19 18:18 ` Tony Lindgren 2013-04-25 13:58 ` Kevin Hilman 0 siblings, 1 reply; 27+ messages in thread From: Tony Lindgren @ 2013-04-19 18:18 UTC (permalink / raw) To: linux-arm-kernel * Santosh Shilimkar <santosh.shilimkar@ti.com> [130419 10:56]: > On Friday 19 April 2013 11:14 PM, Tony Lindgren wrote: > > * Santosh Shilimkar <santosh.shilimkar@ti.com> [130419 10:43]: > >> On Friday 19 April 2013 10:43 PM, Tony Lindgren wrote: > >>> Hi all, > >>> > >>> Here's a list of breakage I've noticed so far while trying to > >>> use linux next on my pandaboard es. Probably similar issues exist > >>> on other boards as well. > >>> > >>> Ideally we would not have any breakage by the merge window, so > >>> let's try to get these fixed ASAP: > >>> > >>> 1. Serial console broken on panda es booting with DT > >>> > >>> The symptoms are dmesg output stopping after few lines > >>> and only continuing after pressing a key. Does not seem to > >>> happen on blaze with DT for some reason. And does not happen > >>> on panda es with legacy booting. > >>> > >> This one is known and reported on list along with fix patches and > >> later pull request [1]. > >> > >> Unfortunately with all the testing and everything and patches have > >> been on the list for quite some time, feedback on one of the patch > >> received was after pull request and then there was no further > >> clarification. That series address the same exact issue you have > >> mentioned above. > > > > OK thanks. I think Paul picked some of those and the plan was > > to update the branch? Which one(s) should go into v3.10 as fixes? > > > Main in that series was to handle driver sysc handling withing hwmod > layer and that is where the series got stuck [2]. Without that support > other patches won't fix the issue. OK it seems that that is still ongoing discussion. For v3.10 we should probably just disable PM for omap4 for DT booting so people can use it for DT related development. Regards, Tony > >> [1] http://patchwork.ozlabs.org/patch/229269/ > > [2] https://patchwork.kernel.org/patch/2166931/ > ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-19 18:18 ` Tony Lindgren @ 2013-04-25 13:58 ` Kevin Hilman 2013-04-26 8:40 ` Santosh Shilimkar 0 siblings, 1 reply; 27+ messages in thread From: Kevin Hilman @ 2013-04-25 13:58 UTC (permalink / raw) To: linux-arm-kernel Tony Lindgren <tony@atomide.com> writes: > * Santosh Shilimkar <santosh.shilimkar@ti.com> [130419 10:56]: >> On Friday 19 April 2013 11:14 PM, Tony Lindgren wrote: >> > * Santosh Shilimkar <santosh.shilimkar@ti.com> [130419 10:43]: >> >> On Friday 19 April 2013 10:43 PM, Tony Lindgren wrote: >> >>> Hi all, >> >>> >> >>> Here's a list of breakage I've noticed so far while trying to >> >>> use linux next on my pandaboard es. Probably similar issues exist >> >>> on other boards as well. >> >>> >> >>> Ideally we would not have any breakage by the merge window, so >> >>> let's try to get these fixed ASAP: >> >>> >> >>> 1. Serial console broken on panda es booting with DT >> >>> >> >>> The symptoms are dmesg output stopping after few lines >> >>> and only continuing after pressing a key. Does not seem to >> >>> happen on blaze with DT for some reason. And does not happen >> >>> on panda es with legacy booting. >> >>> >> >> This one is known and reported on list along with fix patches and >> >> later pull request [1]. >> >> >> >> Unfortunately with all the testing and everything and patches have >> >> been on the list for quite some time, feedback on one of the patch >> >> received was after pull request and then there was no further >> >> clarification. That series address the same exact issue you have >> >> mentioned above. >> > >> > OK thanks. I think Paul picked some of those and the plan was >> > to update the branch? Which one(s) should go into v3.10 as fixes? >> > >> Main in that series was to handle driver sysc handling withing hwmod >> layer and that is where the series got stuck [2]. Without that support >> other patches won't fix the issue. > > OK it seems that that is still ongoing discussion. For v3.10 we should > probably just disable PM for omap4 for DT booting so people can use > it for DT related development. Disabling PM (and even avoiding WFI using 'nohlt') will not fix this problem, since it's related to the idle-mode of the IP block itself. What fixes the problem is the series from Santosh for the SYSC removal. Santosh, it seems that series combined a fix for this problem with some cleanup of the hwmod code that Paul had some concerns with. Is there any chance you can split up that series into a fix targetted at the DT-boot UART problem and a feature cleanup for hwmod? Then we hopefully get this fix into v3.10-rc and work on the hwmod changes/cleanup for the following merge window. Kevin ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-25 13:58 ` Kevin Hilman @ 2013-04-26 8:40 ` Santosh Shilimkar 0 siblings, 0 replies; 27+ messages in thread From: Santosh Shilimkar @ 2013-04-26 8:40 UTC (permalink / raw) To: linux-arm-kernel On Thursday 25 April 2013 07:28 PM, Kevin Hilman wrote: > Tony Lindgren <tony@atomide.com> writes: > >> * Santosh Shilimkar <santosh.shilimkar@ti.com> [130419 10:56]: >>> On Friday 19 April 2013 11:14 PM, Tony Lindgren wrote: >>>> * Santosh Shilimkar <santosh.shilimkar@ti.com> [130419 10:43]: >>>>> On Friday 19 April 2013 10:43 PM, Tony Lindgren wrote: >>>>>> Hi all, >>>>>> >>>>>> Here's a list of breakage I've noticed so far while trying to >>>>>> use linux next on my pandaboard es. Probably similar issues exist >>>>>> on other boards as well. >>>>>> >>>>>> Ideally we would not have any breakage by the merge window, so >>>>>> let's try to get these fixed ASAP: >>>>>> >>>>>> 1. Serial console broken on panda es booting with DT >>>>>> >>>>>> The symptoms are dmesg output stopping after few lines >>>>>> and only continuing after pressing a key. Does not seem to >>>>>> happen on blaze with DT for some reason. And does not happen >>>>>> on panda es with legacy booting. >>>>>> >>>>> This one is known and reported on list along with fix patches and >>>>> later pull request [1]. >>>>> >>>>> Unfortunately with all the testing and everything and patches have >>>>> been on the list for quite some time, feedback on one of the patch >>>>> received was after pull request and then there was no further >>>>> clarification. That series address the same exact issue you have >>>>> mentioned above. >>>> >>>> OK thanks. I think Paul picked some of those and the plan was >>>> to update the branch? Which one(s) should go into v3.10 as fixes? >>>> >>> Main in that series was to handle driver sysc handling withing hwmod >>> layer and that is where the series got stuck [2]. Without that support >>> other patches won't fix the issue. >> >> OK it seems that that is still ongoing discussion. For v3.10 we should >> probably just disable PM for omap4 for DT booting so people can use >> it for DT related development. > > Disabling PM (and even avoiding WFI using 'nohlt') will not fix this > problem, since it's related to the idle-mode of the IP block itself. > > What fixes the problem is the series from Santosh for the SYSC removal. > > Santosh, it seems that series combined a fix for this problem with some > cleanup of the hwmod code that Paul had some concerns with. Is there > any chance you can split up that series into a fix targetted at the > DT-boot UART problem and a feature cleanup for hwmod? > > Then we hopefully get this fix into v3.10-rc and work on the hwmod > changes/cleanup for the following merge window. > That was just one patch which was added so that UART async wakeup works. Rajendra is cleaning up that patch and post an updated series which hopefully make the console issue go away. Regards, Santosh ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-19 17:13 Multiple issues with omap4 panda es in linux next Tony Lindgren 2013-04-19 17:41 ` Santosh Shilimkar @ 2013-04-22 7:49 ` Felipe Balbi 2013-04-22 8:41 ` Kishon Vijay Abraham I ` (2 subsequent siblings) 4 siblings, 0 replies; 27+ messages in thread From: Felipe Balbi @ 2013-04-22 7:49 UTC (permalink / raw) To: linux-arm-kernel Hi, On Fri, Apr 19, 2013 at 10:13:19AM -0700, Tony Lindgren wrote: > 2. MUSB fails with legacy booting and DT on panda es > > With both legacy and DT booting I get something like: > > HS USB OTG: no transceiver configured > musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517 well, enable a transceiver :-p -- balbi -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130422/a4fac839/attachment.sig> ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-19 17:13 Multiple issues with omap4 panda es in linux next Tony Lindgren 2013-04-19 17:41 ` Santosh Shilimkar 2013-04-22 7:49 ` Felipe Balbi @ 2013-04-22 8:41 ` Kishon Vijay Abraham I 2013-04-22 18:03 ` Tony Lindgren 2013-04-22 9:08 ` Tomi Valkeinen 2013-04-24 19:44 ` Tony Lindgren 4 siblings, 1 reply; 27+ messages in thread From: Kishon Vijay Abraham I @ 2013-04-22 8:41 UTC (permalink / raw) To: linux-arm-kernel Hi, On Friday 19 April 2013 10:43 PM, Tony Lindgren wrote: > Hi all, > > Here's a list of breakage I've noticed so far while trying to > use linux next on my pandaboard es. Probably similar issues exist > on other boards as well. > > Ideally we would not have any breakage by the merge window, so > let's try to get these fixed ASAP: > > 1. Serial console broken on panda es booting with DT > > The symptoms are dmesg output stopping after few lines > and only continuing after pressing a key. Does not seem to > happen on blaze with DT for some reason. And does not happen > on panda es with legacy booting. > > 2. MUSB fails with legacy booting and DT on panda es > > With both legacy and DT booting I get something like: > > HS USB OTG: no transceiver configured > musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517 The dt should work fine with https://patchwork.kernel.org/patch/2423061/. But non-dt has got a real issue. We were using usb_bind_phy() for binding the controller with the PHY (we use device names). But in linux-next the device names have changed because of using PLATFORM_DEVID_AUTO. We can modify the usb_bind_phy() calls to use the new device names, But I suspect the device names can change again. Not sure what we can do here :-( Thanks Kishon ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-22 8:41 ` Kishon Vijay Abraham I @ 2013-04-22 18:03 ` Tony Lindgren 2013-04-23 15:10 ` Kishon Vijay Abraham I 0 siblings, 1 reply; 27+ messages in thread From: Tony Lindgren @ 2013-04-22 18:03 UTC (permalink / raw) To: linux-arm-kernel * Kishon Vijay Abraham I <kishon@ti.com> [130422 01:46]: > Hi, > > On Friday 19 April 2013 10:43 PM, Tony Lindgren wrote: > >Hi all, > > > >Here's a list of breakage I've noticed so far while trying to > >use linux next on my pandaboard es. Probably similar issues exist > >on other boards as well. > > > >Ideally we would not have any breakage by the merge window, so > >let's try to get these fixed ASAP: > > > >1. Serial console broken on panda es booting with DT > > > >The symptoms are dmesg output stopping after few lines > >and only continuing after pressing a key. Does not seem to > >happen on blaze with DT for some reason. And does not happen > >on panda es with legacy booting. > > > >2. MUSB fails with legacy booting and DT on panda es > > > >With both legacy and DT booting I get something like: > > > >HS USB OTG: no transceiver configured > >musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517 > > The dt should work fine with https://patchwork.kernel.org/patch/2423061/. OK thanks for checking that. > But non-dt has got a real issue. We were using usb_bind_phy() for > binding the controller with the PHY (we use device names). But in > linux-next the device names have changed because of using > PLATFORM_DEVID_AUTO. We can modify the usb_bind_phy() calls to use > the new device names, But I suspect the device names can change > again. Not sure what we can do here :-( Let's do a minimal fix for v3.10. Then we'll make omap4 DT only for v3.11 and that problem is solved for good. Regards, Tony ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-22 18:03 ` Tony Lindgren @ 2013-04-23 15:10 ` Kishon Vijay Abraham I 2013-04-23 17:23 ` Tony Lindgren 0 siblings, 1 reply; 27+ messages in thread From: Kishon Vijay Abraham I @ 2013-04-23 15:10 UTC (permalink / raw) To: linux-arm-kernel Hi Tony, On Monday 22 April 2013 11:33 PM, Tony Lindgren wrote: > * Kishon Vijay Abraham I <kishon@ti.com> [130422 01:46]: >> Hi, >> >> On Friday 19 April 2013 10:43 PM, Tony Lindgren wrote: >>> Hi all, >>> >>> Here's a list of breakage I've noticed so far while trying to >>> use linux next on my pandaboard es. Probably similar issues exist >>> on other boards as well. >>> >>> Ideally we would not have any breakage by the merge window, so >>> let's try to get these fixed ASAP: >>> >>> 1. Serial console broken on panda es booting with DT >>> >>> The symptoms are dmesg output stopping after few lines >>> and only continuing after pressing a key. Does not seem to >>> happen on blaze with DT for some reason. And does not happen >>> on panda es with legacy booting. >>> >>> 2. MUSB fails with legacy booting and DT on panda es >>> >>> With both legacy and DT booting I get something like: >>> >>> HS USB OTG: no transceiver configured >>> musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517 >> >> The dt should work fine with https://patchwork.kernel.org/patch/2423061/. > > OK thanks for checking that. > >> But non-dt has got a real issue. We were using usb_bind_phy() for >> binding the controller with the PHY (we use device names). But in >> linux-next the device names have changed because of using >> PLATFORM_DEVID_AUTO. We can modify the usb_bind_phy() calls to use >> the new device names, But I suspect the device names can change >> again. Not sure what we can do here :-( > > Let's do a minimal fix for v3.10. Then we'll make omap4 DT only for > v3.11 and that problem is solved for good. Have posted a patch https://patchwork.kernel.org/patch/2475521/ for getting MUSB functional in omap4 panda. Thanks Kishon ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-23 15:10 ` Kishon Vijay Abraham I @ 2013-04-23 17:23 ` Tony Lindgren 2013-04-23 21:31 ` Tony Lindgren 0 siblings, 1 reply; 27+ messages in thread From: Tony Lindgren @ 2013-04-23 17:23 UTC (permalink / raw) To: linux-arm-kernel * Kishon Vijay Abraham I <kishon@ti.com> [130423 08:15]: > >>>2. MUSB fails with legacy booting and DT on panda es > >>> > >>>With both legacy and DT booting I get something like: > >>> > >>>HS USB OTG: no transceiver configured > >>>musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517 > >> > >>The dt should work fine with https://patchwork.kernel.org/patch/2423061/. > > > >OK thanks for checking that. > > > >>But non-dt has got a real issue. We were using usb_bind_phy() for > >>binding the controller with the PHY (we use device names). But in > >>linux-next the device names have changed because of using > >>PLATFORM_DEVID_AUTO. We can modify the usb_bind_phy() calls to use > >>the new device names, But I suspect the device names can change > >>again. Not sure what we can do here :-( > > > >Let's do a minimal fix for v3.10. Then we'll make omap4 DT only for > >v3.11 and that problem is solved for good. > > Have posted a patch https://patchwork.kernel.org/patch/2475521/ for > getting MUSB functional in omap4 panda. OK thanks. Paul it seems that this patch is still queued in one of your branches? Let me know if you want me to pick that one up for fixes for the merge window, or if you have multiple patches to pull. Regards, Tony ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-23 17:23 ` Tony Lindgren @ 2013-04-23 21:31 ` Tony Lindgren 2013-04-23 23:16 ` Tony Lindgren 0 siblings, 1 reply; 27+ messages in thread From: Tony Lindgren @ 2013-04-23 21:31 UTC (permalink / raw) To: linux-arm-kernel * Tony Lindgren <tony@atomide.com> [130423 10:28]: > * Kishon Vijay Abraham I <kishon@ti.com> [130423 08:15]: > > >>>2. MUSB fails with legacy booting and DT on panda es > > >>> > > >>>With both legacy and DT booting I get something like: > > >>> > > >>>HS USB OTG: no transceiver configured > > >>>musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517 > > >> > > >>The dt should work fine with https://patchwork.kernel.org/patch/2423061/. > > > > > >OK thanks for checking that. > > > > > >>But non-dt has got a real issue. We were using usb_bind_phy() for > > >>binding the controller with the PHY (we use device names). But in > > >>linux-next the device names have changed because of using > > >>PLATFORM_DEVID_AUTO. We can modify the usb_bind_phy() calls to use > > >>the new device names, But I suspect the device names can change > > >>again. Not sure what we can do here :-( > > > > > >Let's do a minimal fix for v3.10. Then we'll make omap4 DT only for > > >v3.11 and that problem is solved for good. > > > > Have posted a patch https://patchwork.kernel.org/patch/2475521/ for > > getting MUSB functional in omap4 panda. > > OK thanks. Paul it seems that this patch is still queued in one of > your branches? > > Let me know if you want me to pick that one up for fixes for the > merge window, or if you have multiple patches to pull. Oops this I already have sitting in omap-for-v3.9-rc6/fixes.. Let's see if that can still get merged. Looks like I forgot to send off that one, sorry about that. Regards, Tony ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-23 21:31 ` Tony Lindgren @ 2013-04-23 23:16 ` Tony Lindgren 2013-04-24 5:41 ` Kishon Vijay Abraham I 0 siblings, 1 reply; 27+ messages in thread From: Tony Lindgren @ 2013-04-23 23:16 UTC (permalink / raw) To: linux-arm-kernel * Tony Lindgren <tony@atomide.com> [130423 14:37]: > * Tony Lindgren <tony@atomide.com> [130423 10:28]: > > * Kishon Vijay Abraham I <kishon@ti.com> [130423 08:15]: > > > >>>2. MUSB fails with legacy booting and DT on panda es > > > >>> > > > >>>With both legacy and DT booting I get something like: > > > >>> > > > >>>HS USB OTG: no transceiver configured > > > >>>musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517 > > > >> > > > >>The dt should work fine with https://patchwork.kernel.org/patch/2423061/. > > > > > > > >OK thanks for checking that. Kishon, I think there's also some other issue remaining in linux next with MUSB and DT. I'm still getting the "HS USB OTG: no transceiver configured" although the nop xceiv is compiled in. Maybe give it a try against linux next? Regards, Tony ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-23 23:16 ` Tony Lindgren @ 2013-04-24 5:41 ` Kishon Vijay Abraham I 2013-04-24 19:08 ` Tony Lindgren 0 siblings, 1 reply; 27+ messages in thread From: Kishon Vijay Abraham I @ 2013-04-24 5:41 UTC (permalink / raw) To: linux-arm-kernel Hi Tony, On Wednesday 24 April 2013 04:46 AM, Tony Lindgren wrote: > * Tony Lindgren <tony@atomide.com> [130423 14:37]: >> * Tony Lindgren <tony@atomide.com> [130423 10:28]: >>> * Kishon Vijay Abraham I <kishon@ti.com> [130423 08:15]: >>>>>>> 2. MUSB fails with legacy booting and DT on panda es >>>>>>> >>>>>>> With both legacy and DT booting I get something like: >>>>>>> >>>>>>> HS USB OTG: no transceiver configured >>>>>>> musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517 >>>>>> >>>>>> The dt should work fine with https://patchwork.kernel.org/patch/2423061/. >>>>> >>>>> OK thanks for checking that. > > Kishon, I think there's also some other issue remaining > in linux next with MUSB and DT. I'm still getting the > "HS USB OTG: no transceiver configured" although the nop > xceiv is compiled in. Maybe give it a try against linux > next? For OMAP4 MUSB, you'll need omap-usb2 phy. I've attached my .config. Thanks Kishon -------------- next part -------------- # # Automatically generated file; DO NOT EDIT. # Linux/arm 3.9.0-rc7 Kernel Configuration # CONFIG_ARM=y CONFIG_SYS_SUPPORTS_APM_EMULATION=y CONFIG_HAVE_PROC_CPU=y CONFIG_NO_IOPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_TRACE_IRQFLAGS_SUPPORT=y CONFIG_RWSEM_GENERIC_SPINLOCK=y CONFIG_ARCH_HAS_CPUFREQ=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_NEED_DMA_MAP_STATE=y CONFIG_VECTORS_BASE=0xffff0000 CONFIG_ARM_PATCH_PHYS_VIRT=y CONFIG_GENERIC_BUG=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" CONFIG_IRQ_WORK=y CONFIG_BUILDTIME_EXTABLE_SORT=y # # General setup # CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_CROSS_COMPILE="" CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_LZMA=y CONFIG_HAVE_KERNEL_XZ=y CONFIG_HAVE_KERNEL_LZO=y CONFIG_HAVE_KERNEL_LZ4=y CONFIG_KERNEL_GZIP=y # CONFIG_KERNEL_LZMA is not set # CONFIG_KERNEL_XZ is not set # CONFIG_KERNEL_LZO is not set # CONFIG_KERNEL_LZ4 is not set CONFIG_DEFAULT_HOSTNAME="(none)" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_POSIX_MQUEUE_SYSCTL=y # CONFIG_FHANDLE is not set # CONFIG_AUDIT is not set CONFIG_HAVE_GENERIC_HARDIRQS=y # # IRQ subsystem # CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_IRQ_SHOW=y CONFIG_HARDIRQS_SW_RESEND=y CONFIG_GENERIC_IRQ_CHIP=y CONFIG_IRQ_DOMAIN=y # CONFIG_IRQ_DOMAIN_DEBUG is not set CONFIG_SPARSE_IRQ=y # CONFIG_ALWAYS_USE_PERSISTENT_CLOCK is not set CONFIG_KTIME_SCALAR=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_ARCH_HAS_TICK_BROADCAST=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y # # Timers subsystem # CONFIG_TICK_ONESHOT=y CONFIG_PERIODIC_HZ=y # CONFIG_NO_HZ_IDLE is not set CONFIG_HIGH_RES_TIMERS=y # # CPU/Task time and stats accounting # CONFIG_TICK_CPU_ACCOUNTING=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set # CONFIG_TASKSTATS is not set # # RCU Subsystem # CONFIG_TREE_RCU=y # CONFIG_PREEMPT_RCU is not set CONFIG_RCU_STALL_COMMON=y # CONFIG_RCU_USER_QS is not set CONFIG_RCU_FANOUT=32 CONFIG_RCU_FANOUT_LEAF=16 # CONFIG_RCU_FANOUT_EXACT is not set # CONFIG_TREE_RCU_TRACE is not set # CONFIG_RCU_NOCB_CPU is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=16 # CONFIG_CGROUPS is not set # CONFIG_CHECKPOINT_RESTORE is not set # CONFIG_NAMESPACES is not set CONFIG_UIDGID_CONVERTED=y # CONFIG_UIDGID_STRICT_TYPE_CHECKS is not set # CONFIG_SCHED_AUTOGROUP is not set # CONFIG_SYSFS_DEPRECATED is not set # CONFIG_RELAY is not set CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="/nfs/newfs" CONFIG_INITRAMFS_ROOT_UID=0 CONFIG_INITRAMFS_ROOT_GID=0 CONFIG_RD_GZIP=y # CONFIG_RD_BZIP2 is not set # CONFIG_RD_LZMA is not set # CONFIG_RD_XZ is not set # CONFIG_RD_LZO is not set # CONFIG_RD_LZ4 is not set CONFIG_INITRAMFS_COMPRESSION_NONE=y # CONFIG_INITRAMFS_COMPRESSION_GZIP is not set # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_ANON_INODES=y CONFIG_EXPERT=y CONFIG_HAVE_UID16=y CONFIG_UID16=y # CONFIG_SYSCTL_SYSCALL is not set CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_AIO=y # CONFIG_EMBEDDED is not set CONFIG_HAVE_PERF_EVENTS=y CONFIG_PERF_USE_VMALLOC=y # # Kernel Performance Events And Counters # CONFIG_PERF_EVENTS=y # CONFIG_DEBUG_PERF_USE_VMALLOC is not set CONFIG_VM_EVENT_COUNTERS=y CONFIG_COMPAT_BRK=y CONFIG_SLAB=y # CONFIG_SLUB is not set # CONFIG_SLOB is not set CONFIG_PROFILING=y CONFIG_TRACEPOINTS=y CONFIG_OPROFILE=y CONFIG_HAVE_OPROFILE=y CONFIG_KPROBES=y # CONFIG_JUMP_LABEL is not set # CONFIG_HAVE_64BIT_ALIGNED_ACCESS is not set CONFIG_KRETPROBES=y CONFIG_HAVE_KPROBES=y CONFIG_HAVE_KRETPROBES=y CONFIG_HAVE_ARCH_TRACEHOOK=y CONFIG_HAVE_DMA_ATTRS=y CONFIG_HAVE_DMA_CONTIGUOUS=y CONFIG_USE_GENERIC_SMP_HELPERS=y CONFIG_GENERIC_SMP_IDLE_THREAD=y CONFIG_GENERIC_IDLE_LOOP=y CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y CONFIG_HAVE_CLK=y CONFIG_HAVE_DMA_API_DEBUG=y CONFIG_HAVE_HW_BREAKPOINT=y CONFIG_HAVE_ARCH_JUMP_LABEL=y CONFIG_ARCH_WANT_IPC_PARSE_VERSION=y CONFIG_HAVE_ARCH_SECCOMP_FILTER=y CONFIG_HAVE_CONTEXT_TRACKING=y CONFIG_HAVE_MOD_ARCH_SPECIFIC=y CONFIG_MODULES_USE_ELF_REL=y CONFIG_CLONE_BACKWARDS=y CONFIG_OLD_SIGSUSPEND3=y CONFIG_OLD_SIGACTION=y # # GCOV-based kernel profiling # # CONFIG_GCOV_KERNEL is not set CONFIG_HAVE_GENERIC_DMA_COHERENT=y CONFIG_SLABINFO=y CONFIG_RT_MUTEXES=y CONFIG_BASE_SMALL=0 CONFIG_MODULES=y CONFIG_MODULE_FORCE_LOAD=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y CONFIG_MODVERSIONS=y CONFIG_MODULE_SRCVERSION_ALL=y # CONFIG_MODULE_SIG is not set CONFIG_STOP_MACHINE=y CONFIG_BLOCK=y CONFIG_LBDAF=y # CONFIG_BLK_DEV_BSG is not set # CONFIG_BLK_DEV_BSGLIB is not set # CONFIG_BLK_DEV_INTEGRITY is not set # # Partition Types # CONFIG_PARTITION_ADVANCED=y # CONFIG_ACORN_PARTITION is not set # CONFIG_OSF_PARTITION is not set # CONFIG_AMIGA_PARTITION is not set # CONFIG_ATARI_PARTITION is not set # CONFIG_MAC_PARTITION is not set CONFIG_MSDOS_PARTITION=y # CONFIG_BSD_DISKLABEL is not set # CONFIG_MINIX_SUBPARTITION is not set # CONFIG_SOLARIS_X86_PARTITION is not set # CONFIG_UNIXWARE_DISKLABEL is not set # CONFIG_LDM_PARTITION is not set # CONFIG_SGI_PARTITION is not set # CONFIG_ULTRIX_PARTITION is not set # CONFIG_SUN_PARTITION is not set # CONFIG_KARMA_PARTITION is not set CONFIG_EFI_PARTITION=y # CONFIG_SYSV68_PARTITION is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="cfq" CONFIG_UNINLINE_SPIN_UNLOCK=y CONFIG_FREEZER=y # # System Type # CONFIG_MMU=y CONFIG_ARCH_MULTIPLATFORM=y # CONFIG_ARCH_INTEGRATOR is not set # CONFIG_ARCH_REALVIEW is not set # CONFIG_ARCH_VERSATILE is not set # CONFIG_ARCH_AT91 is not set # CONFIG_ARCH_CLPS711X is not set # CONFIG_ARCH_GEMINI is not set # CONFIG_ARCH_EBSA110 is not set # CONFIG_ARCH_EP93XX is not set # CONFIG_ARCH_FOOTBRIDGE is not set # CONFIG_ARCH_NETX is not set # CONFIG_ARCH_IOP13XX is not set # CONFIG_ARCH_IOP32X is not set # CONFIG_ARCH_IOP33X is not set # CONFIG_ARCH_IXP4XX is not set # CONFIG_ARCH_DOVE is not set # CONFIG_ARCH_KIRKWOOD is not set # CONFIG_ARCH_MV78XX0 is not set # CONFIG_ARCH_ORION5X is not set # CONFIG_ARCH_MMP is not set # CONFIG_ARCH_KS8695 is not set # CONFIG_ARCH_W90X900 is not set # CONFIG_ARCH_LPC32XX is not set # CONFIG_ARCH_PXA is not set # CONFIG_ARCH_MSM is not set # CONFIG_ARCH_SHMOBILE is not set # CONFIG_ARCH_RPC is not set # CONFIG_ARCH_SA1100 is not set # CONFIG_ARCH_S3C24XX is not set # CONFIG_ARCH_S3C64XX is not set # CONFIG_ARCH_S5P64X0 is not set # CONFIG_ARCH_S5PC100 is not set # CONFIG_ARCH_S5PV210 is not set # CONFIG_ARCH_EXYNOS is not set # CONFIG_ARCH_SHARK is not set # CONFIG_ARCH_U300 is not set # CONFIG_ARCH_DAVINCI is not set # CONFIG_ARCH_OMAP1 is not set # # Multiple platform selection # # # CPU Core family selection # # CONFIG_ARCH_MULTI_V6 is not set CONFIG_ARCH_MULTI_V7=y CONFIG_ARCH_MULTI_V6_V7=y # CONFIG_ARCH_MULTI_CPU_AUTO is not set # CONFIG_ARCH_MVEBU is not set # CONFIG_ARCH_BCM is not set # CONFIG_GPIO_PCA953X is not set # CONFIG_KEYBOARD_GPIO_POLLED is not set # CONFIG_ARCH_HIGHBANK is not set # CONFIG_ARCH_MXC is not set # # TI OMAP Common Features # # # OMAP Feature Selections # CONFIG_OMAP_DEBUG_DEVICES=y CONFIG_OMAP_DEBUG_LEDS=y CONFIG_OMAP_RESET_CLOCKS=y CONFIG_OMAP_MUX=y CONFIG_OMAP_MUX_DEBUG=y CONFIG_OMAP_MUX_WARNINGS=y CONFIG_OMAP_32K_TIMER=y # CONFIG_OMAP3_L2_AUX_SECURE_SAVE_RESTORE is not set CONFIG_OMAP_DM_TIMER=y CONFIG_OMAP_PM_NOOP=y CONFIG_MACH_OMAP_GENERIC=y CONFIG_ARCH_OMAP=y CONFIG_ARCH_OMAP2PLUS=y # # TI OMAP2/3/4 Specific Features # CONFIG_ARCH_OMAP2PLUS_TYPICAL=y CONFIG_SOC_HAS_OMAP2_SDRC=y CONFIG_SOC_HAS_REALTIME_COUNTER=y CONFIG_ARCH_OMAP2=y CONFIG_ARCH_OMAP3=y CONFIG_ARCH_OMAP4=y CONFIG_SOC_OMAP5=y # # OMAP Core Type # CONFIG_SOC_OMAP2420=y CONFIG_SOC_OMAP2430=y CONFIG_SOC_OMAP3430=y CONFIG_SOC_TI81XX=y CONFIG_SOC_AM33XX=y CONFIG_OMAP_PACKAGE_ZAF=y CONFIG_OMAP_PACKAGE_ZAC=y CONFIG_OMAP_PACKAGE_CBB=y CONFIG_OMAP_PACKAGE_CUS=y CONFIG_OMAP_PACKAGE_CBP=y CONFIG_OMAP_PACKAGE_CBL=y CONFIG_OMAP_PACKAGE_CBS=y # # OMAP Board Type # CONFIG_MACH_OMAP2_TUSB6010=y CONFIG_MACH_OMAP_H4=y CONFIG_MACH_OMAP_2430SDP=y CONFIG_MACH_OMAP3_BEAGLE=y CONFIG_MACH_DEVKIT8000=y CONFIG_MACH_OMAP_LDP=y CONFIG_MACH_OMAP3530_LV_SOM=y CONFIG_MACH_OMAP3_TORPEDO=y CONFIG_MACH_OVERO=y CONFIG_MACH_OMAP3EVM=y CONFIG_MACH_OMAP3517EVM=y # CONFIG_MACH_CRANEBOARD is not set CONFIG_MACH_OMAP3_PANDORA=y CONFIG_MACH_TOUCHBOOK=y CONFIG_MACH_OMAP_3430SDP=y CONFIG_MACH_NOKIA_N800=y CONFIG_MACH_NOKIA_N810=y CONFIG_MACH_NOKIA_N810_WIMAX=y CONFIG_MACH_NOKIA_N8X0=y CONFIG_MACH_NOKIA_RM680=y CONFIG_MACH_NOKIA_RX51=y CONFIG_MACH_OMAP_ZOOM2=y CONFIG_MACH_OMAP_ZOOM3=y CONFIG_MACH_CM_T35=y CONFIG_MACH_CM_T3517=y CONFIG_MACH_CM_T3730=y CONFIG_MACH_IGEP0020=y CONFIG_MACH_IGEP0030=y CONFIG_MACH_SBC3530=y CONFIG_MACH_OMAP_3630SDP=y CONFIG_MACH_TI8168EVM=y CONFIG_MACH_TI8148EVM=y CONFIG_MACH_OMAP_4430SDP=y CONFIG_MACH_OMAP4_PANDA=y # CONFIG_OMAP3_EMU is not set # CONFIG_OMAP3_SDRC_AC_TIMING is not set # CONFIG_ARCH_SOCFPGA is not set # CONFIG_PLAT_SPEAR is not set # CONFIG_ARCH_SUNXI is not set # CONFIG_ARCH_SIRF is not set # CONFIG_ARCH_TEGRA is not set # CONFIG_ARCH_U8500 is not set CONFIG_ARCH_VEXPRESS=y # # Versatile Express platform type # CONFIG_ARCH_VEXPRESS_CORTEX_A5_A9_ERRATA=y CONFIG_ARCH_VEXPRESS_CA9X4=y CONFIG_PLAT_VERSATILE_CLCD=y CONFIG_PLAT_VERSATILE_SCHED_CLOCK=y # CONFIG_ARCH_VIRT is not set # CONFIG_ARCH_WM8850 is not set # CONFIG_ARCH_ZYNQ is not set CONFIG_PLAT_VERSATILE=y CONFIG_ARM_TIMER_SP804=y # # Processor Type # CONFIG_CPU_V6=y CONFIG_CPU_V7=y CONFIG_CPU_32v6=y CONFIG_CPU_32v6K=y CONFIG_CPU_32v7=y CONFIG_CPU_ABRT_EV6=y CONFIG_CPU_ABRT_EV7=y CONFIG_CPU_PABRT_V6=y CONFIG_CPU_PABRT_V7=y CONFIG_CPU_CACHE_V6=y CONFIG_CPU_CACHE_V7=y CONFIG_CPU_CACHE_VIPT=y CONFIG_CPU_COPY_V6=y CONFIG_CPU_TLB_V6=y CONFIG_CPU_TLB_V7=y CONFIG_CPU_HAS_ASID=y CONFIG_CPU_CP15=y CONFIG_CPU_CP15_MMU=y CONFIG_CPU_USE_DOMAINS=y # # Processor Features # # CONFIG_ARCH_PHYS_ADDR_T_64BIT is not set CONFIG_ARM_THUMB=y CONFIG_ARM_THUMBEE=y CONFIG_ARM_VIRT_EXT=y # CONFIG_CPU_ICACHE_DISABLE is not set # CONFIG_CPU_DCACHE_DISABLE is not set # CONFIG_CPU_BPREDICT_DISABLE is not set CONFIG_OUTER_CACHE=y CONFIG_OUTER_CACHE_SYNC=y CONFIG_MIGHT_HAVE_CACHE_L2X0=y CONFIG_CACHE_L2X0=y CONFIG_ARM_L1_CACHE_SHIFT_6=y CONFIG_ARM_L1_CACHE_SHIFT=6 CONFIG_ARM_DMA_MEM_BUFFERABLE=y CONFIG_ARM_NR_BANKS=8 CONFIG_MULTI_IRQ_HANDLER=y # CONFIG_ARM_ERRATA_326103 is not set CONFIG_ARM_ERRATA_411920=y # CONFIG_ARM_ERRATA_430973 is not set CONFIG_PL310_ERRATA_588369=y CONFIG_ARM_ERRATA_720789=y CONFIG_PL310_ERRATA_727915=y CONFIG_ARM_ERRATA_754322=y # CONFIG_ARM_ERRATA_754327 is not set # CONFIG_ARM_ERRATA_764369 is not set # CONFIG_PL310_ERRATA_769419 is not set CONFIG_ARM_ERRATA_775420=y # CONFIG_ARM_ERRATA_798181 is not set CONFIG_ICST=y # # Bus support # CONFIG_ARM_AMBA=y # CONFIG_PCI_SYSCALL is not set # CONFIG_PCCARD is not set # # Kernel Features # CONFIG_HAVE_SMP=y CONFIG_SMP=y CONFIG_SMP_ON_UP=y CONFIG_ARM_CPU_TOPOLOGY=y # CONFIG_SCHED_MC is not set # CONFIG_SCHED_SMT is not set CONFIG_HAVE_ARM_SCU=y CONFIG_HAVE_ARM_ARCH_TIMER=y CONFIG_HAVE_ARM_TWD=y CONFIG_VMSPLIT_3G=y # CONFIG_VMSPLIT_2G is not set # CONFIG_VMSPLIT_1G is not set CONFIG_PAGE_OFFSET=0xC0000000 CONFIG_NR_CPUS=2 CONFIG_HOTPLUG_CPU=y # CONFIG_ARM_PSCI is not set CONFIG_LOCAL_TIMERS=y CONFIG_ARCH_NR_GPIO=512 CONFIG_PREEMPT_NONE=y # CONFIG_PREEMPT_VOLUNTARY is not set # CONFIG_PREEMPT is not set CONFIG_HZ=100 CONFIG_SCHED_HRTICK=y CONFIG_AEABI=y CONFIG_OABI_COMPAT=y CONFIG_ARCH_HAS_HOLES_MEMORYMODEL=y # CONFIG_ARCH_SPARSEMEM_DEFAULT is not set # CONFIG_ARCH_SELECT_MEMORY_MODEL is not set CONFIG_HAVE_ARCH_PFN_VALID=y CONFIG_HIGHMEM=y # CONFIG_HIGHPTE is not set CONFIG_HW_PERF_EVENTS=y CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y CONFIG_HAVE_MEMBLOCK=y CONFIG_MEMORY_ISOLATION=y # CONFIG_HAVE_BOOTMEM_INFO_NODE is not set CONFIG_PAGEFLAGS_EXTENDED=y CONFIG_SPLIT_PTLOCK_CPUS=999999 CONFIG_COMPACTION=y CONFIG_MIGRATION=y # CONFIG_PHYS_ADDR_T_64BIT is not set CONFIG_ZONE_DMA_FLAG=0 CONFIG_BOUNCE=y # CONFIG_KSM is not set CONFIG_DEFAULT_MMAP_MIN_ADDR=4096 CONFIG_CROSS_MEMORY_ATTACH=y # CONFIG_CLEANCACHE is not set # CONFIG_FRONTSWAP is not set CONFIG_FORCE_MAX_ZONEORDER=12 CONFIG_ALIGNMENT_TRAP=y # CONFIG_UACCESS_WITH_MEMCPY is not set # CONFIG_SECCOMP is not set # CONFIG_CC_STACKPROTECTOR is not set # # Boot options # CONFIG_USE_OF=y CONFIG_ATAGS=y # CONFIG_DEPRECATED_PARAM_STRUCT is not set CONFIG_ZBOOT_ROM_TEXT=0x0 CONFIG_ZBOOT_ROM_BSS=0x0 CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER=y # CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_EXTEND is not set CONFIG_CMDLINE="root=/dev/mmcblk0p2 rootwait console=ttyO2,115200" CONFIG_CMDLINE_FROM_BOOTLOADER=y # CONFIG_CMDLINE_EXTEND is not set # CONFIG_CMDLINE_FORCE is not set CONFIG_KEXEC=y CONFIG_ATAGS_PROC=y # CONFIG_CRASH_DUMP is not set CONFIG_AUTO_ZRELADDR=y # # CPU Power Management # # # CPU Frequency scaling # # CONFIG_CPU_FREQ is not set # CONFIG_CPU_IDLE is not set CONFIG_ARCH_NEEDS_CPU_IDLE_COUPLED=y # # Floating point emulation # # # At least one emulation must be selected # CONFIG_FPE_NWFPE=y # CONFIG_FPE_NWFPE_XP is not set # CONFIG_FPE_FASTFPE is not set CONFIG_VFP=y CONFIG_VFPv3=y CONFIG_NEON=y # # Userspace binary formats # CONFIG_BINFMT_ELF=y CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE=y CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y CONFIG_BINFMT_SCRIPT=y CONFIG_HAVE_AOUT=y # CONFIG_BINFMT_AOUT is not set CONFIG_BINFMT_MISC=y CONFIG_COREDUMP=y # # Power management options # CONFIG_SUSPEND=y CONFIG_SUSPEND_FREEZER=y CONFIG_PM_SLEEP=y CONFIG_PM_SLEEP_SMP=y # CONFIG_PM_AUTOSLEEP is not set # CONFIG_PM_WAKELOCKS is not set CONFIG_PM_RUNTIME=y CONFIG_PM=y CONFIG_PM_DEBUG=y # CONFIG_PM_ADVANCED_DEBUG is not set # CONFIG_PM_TEST_SUSPEND is not set CONFIG_PM_SLEEP_DEBUG=y # CONFIG_APM_EMULATION is not set CONFIG_ARCH_HAS_OPP=y CONFIG_PM_OPP=y CONFIG_PM_CLK=y CONFIG_CPU_PM=y CONFIG_ARCH_SUSPEND_POSSIBLE=y CONFIG_ARM_CPU_SUSPEND=y CONFIG_NET=y # # Networking options # CONFIG_PACKET=y # CONFIG_PACKET_DIAG is not set CONFIG_UNIX=y # CONFIG_UNIX_DIAG is not set CONFIG_XFRM=y CONFIG_XFRM_ALGO=y CONFIG_XFRM_USER=y # CONFIG_XFRM_SUB_POLICY is not set CONFIG_XFRM_MIGRATE=y # CONFIG_XFRM_STATISTICS is not set CONFIG_NET_KEY=y CONFIG_NET_KEY_MIGRATE=y CONFIG_INET=y CONFIG_IP_MULTICAST=y # CONFIG_IP_ADVANCED_ROUTER is not set CONFIG_IP_PNP=y CONFIG_IP_PNP_DHCP=y CONFIG_IP_PNP_BOOTP=y CONFIG_IP_PNP_RARP=y # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE_DEMUX is not set # CONFIG_NET_IP_TUNNEL is not set # CONFIG_IP_MROUTE is not set # CONFIG_ARPD is not set # CONFIG_SYN_COOKIES is not set # CONFIG_NET_IPVTI is not set # CONFIG_INET_AH is not set # CONFIG_INET_ESP is not set # CONFIG_INET_IPCOMP is not set # CONFIG_INET_XFRM_TUNNEL is not set # CONFIG_INET_TUNNEL is not set CONFIG_INET_XFRM_MODE_TRANSPORT=y CONFIG_INET_XFRM_MODE_TUNNEL=y CONFIG_INET_XFRM_MODE_BEET=y # CONFIG_INET_LRO is not set CONFIG_INET_DIAG=y CONFIG_INET_TCP_DIAG=y # CONFIG_INET_UDP_DIAG is not set # CONFIG_TCP_CONG_ADVANCED is not set CONFIG_TCP_CONG_CUBIC=y CONFIG_DEFAULT_TCP_CONG="cubic" # CONFIG_TCP_MD5SIG is not set # CONFIG_IPV6 is not set # CONFIG_NETLABEL is not set # CONFIG_NETWORK_SECMARK is not set # CONFIG_NETWORK_PHY_TIMESTAMPING is not set CONFIG_NETFILTER=y # CONFIG_NETFILTER_DEBUG is not set CONFIG_NETFILTER_ADVANCED=y # # Core Netfilter Configuration # # CONFIG_NETFILTER_NETLINK_ACCT is not set # CONFIG_NETFILTER_NETLINK_QUEUE is not set # CONFIG_NETFILTER_NETLINK_LOG is not set # CONFIG_NF_CONNTRACK is not set # CONFIG_NETFILTER_XTABLES is not set # CONFIG_IP_VS is not set # # IP: Netfilter Configuration # # CONFIG_NF_DEFRAG_IPV4 is not set # CONFIG_IP_NF_IPTABLES is not set # CONFIG_IP_NF_ARPTABLES is not set # CONFIG_IP_DCCP is not set # CONFIG_IP_SCTP is not set # CONFIG_RDS is not set # CONFIG_TIPC is not set # CONFIG_ATM is not set # CONFIG_L2TP is not set # CONFIG_BRIDGE is not set CONFIG_HAVE_NET_DSA=y # CONFIG_VLAN_8021Q is not set # CONFIG_DECNET is not set # CONFIG_LLC2 is not set # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_PHONET is not set # CONFIG_IEEE802154 is not set # CONFIG_NET_SCHED is not set # CONFIG_DCB is not set CONFIG_DNS_RESOLVER=y # CONFIG_BATMAN_ADV is not set # CONFIG_OPENVSWITCH is not set # CONFIG_VSOCKETS is not set # CONFIG_NETLINK_DIAG is not set CONFIG_RPS=y CONFIG_RFS_ACCEL=y CONFIG_XPS=y CONFIG_BQL=y # CONFIG_BPF_JIT is not set # # Network testing # # CONFIG_NET_PKTGEN is not set # CONFIG_NET_TCPPROBE is not set # CONFIG_NET_DROP_MONITOR is not set # CONFIG_HAMRADIO is not set CONFIG_CAN=m CONFIG_CAN_RAW=m CONFIG_CAN_BCM=m CONFIG_CAN_GW=m # # CAN Device Drivers # # CONFIG_CAN_VCAN is not set # CONFIG_CAN_SLCAN is not set CONFIG_CAN_DEV=m CONFIG_CAN_CALC_BITTIMING=y # CONFIG_CAN_LEDS is not set # CONFIG_CAN_AT91 is not set # CONFIG_CAN_TI_HECC is not set # CONFIG_CAN_MCP251X is not set # CONFIG_CAN_GRCAN is not set # CONFIG_CAN_SJA1000 is not set CONFIG_CAN_C_CAN=m CONFIG_CAN_C_CAN_PLATFORM=m # CONFIG_CAN_CC770 is not set # # CAN USB interfaces # # CONFIG_CAN_EMS_USB is not set # CONFIG_CAN_ESD_USB2 is not set # CONFIG_CAN_KVASER_USB is not set # CONFIG_CAN_PEAK_USB is not set # CONFIG_CAN_8DEV_USB is not set # CONFIG_CAN_SOFTING is not set # CONFIG_CAN_DEBUG_DEVICES is not set # CONFIG_IRDA is not set CONFIG_BT=m # CONFIG_BT_RFCOMM is not set # CONFIG_BT_BNEP is not set # CONFIG_BT_HIDP is not set # # Bluetooth device drivers # # CONFIG_BT_HCIBTUSB is not set # CONFIG_BT_HCIBTSDIO is not set CONFIG_BT_HCIUART=m CONFIG_BT_HCIUART_H4=y CONFIG_BT_HCIUART_BCSP=y # CONFIG_BT_HCIUART_ATH3K is not set CONFIG_BT_HCIUART_LL=y # CONFIG_BT_HCIUART_3WIRE is not set CONFIG_BT_HCIBCM203X=m CONFIG_BT_HCIBPA10X=m # CONFIG_BT_HCIBFUSB is not set # CONFIG_BT_HCIVHCI is not set # CONFIG_BT_MRVL is not set # CONFIG_AF_RXRPC is not set CONFIG_WIRELESS=y CONFIG_WIRELESS_EXT=y CONFIG_WEXT_CORE=y CONFIG_WEXT_PROC=y CONFIG_WEXT_SPY=y CONFIG_CFG80211=m # CONFIG_NL80211_TESTMODE is not set # CONFIG_CFG80211_DEVELOPER_WARNINGS is not set # CONFIG_CFG80211_REG_DEBUG is not set # CONFIG_CFG80211_CERTIFICATION_ONUS is not set CONFIG_CFG80211_DEFAULT_PS=y # CONFIG_CFG80211_DEBUGFS is not set # CONFIG_CFG80211_INTERNAL_REGDB is not set # CONFIG_CFG80211_WEXT is not set CONFIG_LIB80211=m # CONFIG_LIB80211_DEBUG is not set CONFIG_MAC80211=m CONFIG_MAC80211_HAS_RC=y CONFIG_MAC80211_RC_PID=y CONFIG_MAC80211_RC_MINSTREL=y CONFIG_MAC80211_RC_MINSTREL_HT=y CONFIG_MAC80211_RC_DEFAULT_PID=y # CONFIG_MAC80211_RC_DEFAULT_MINSTREL is not set CONFIG_MAC80211_RC_DEFAULT="pid" # CONFIG_MAC80211_MESH is not set # CONFIG_MAC80211_LEDS is not set # CONFIG_MAC80211_DEBUGFS is not set # CONFIG_MAC80211_MESSAGE_TRACING is not set # CONFIG_MAC80211_DEBUG_MENU is not set # CONFIG_WIMAX is not set # CONFIG_RFKILL is not set # CONFIG_RFKILL_REGULATOR is not set # CONFIG_NET_9P is not set # CONFIG_CAIF is not set # CONFIG_CEPH_LIB is not set # CONFIG_NFC is not set CONFIG_HAVE_BPF_JIT=y # # Device Drivers # # # Generic Driver Options # CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug" CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_FW_LOADER=y CONFIG_FIRMWARE_IN_KERNEL=y CONFIG_EXTRA_FIRMWARE="" CONFIG_FW_LOADER_USER_HELPER=y # CONFIG_DEBUG_DRIVER is not set # CONFIG_DEBUG_DEVRES is not set # CONFIG_SYS_HYPERVISOR is not set # CONFIG_GENERIC_CPU_DEVICES is not set CONFIG_SOC_BUS=y CONFIG_REGMAP=y CONFIG_REGMAP_I2C=y CONFIG_REGMAP_SPI=m CONFIG_REGMAP_IRQ=y # CONFIG_DMA_SHARED_BUFFER is not set CONFIG_CMA=y # CONFIG_CMA_DEBUG is not set # # Default contiguous memory area size: # CONFIG_CMA_SIZE_MBYTES=16 CONFIG_CMA_SIZE_SEL_MBYTES=y # CONFIG_CMA_SIZE_SEL_PERCENTAGE is not set # CONFIG_CMA_SIZE_SEL_MIN is not set # CONFIG_CMA_SIZE_SEL_MAX is not set CONFIG_CMA_ALIGNMENT=8 CONFIG_CMA_AREAS=7 # # Bus devices # CONFIG_OMAP_OCP2SCP=y CONFIG_OMAP_INTERCONNECT=y CONFIG_CONNECTOR=y CONFIG_PROC_EVENTS=y CONFIG_MTD=y # CONFIG_MTD_TESTS is not set # CONFIG_MTD_REDBOOT_PARTS is not set CONFIG_MTD_CMDLINE_PARTS=y # CONFIG_MTD_AFS_PARTS is not set CONFIG_MTD_OF_PARTS=y # CONFIG_MTD_AR7_PARTS is not set # # User Modules And Translation Layers # CONFIG_MTD_BLKDEVS=y CONFIG_MTD_BLOCK=y # CONFIG_FTL is not set # CONFIG_NFTL is not set # CONFIG_INFTL is not set # CONFIG_RFD_FTL is not set # CONFIG_SSFDC is not set # CONFIG_SM_FTL is not set CONFIG_MTD_OOPS=y # CONFIG_MTD_SWAP is not set # # RAM/ROM/Flash chip drivers # CONFIG_MTD_CFI=y # CONFIG_MTD_JEDECPROBE is not set CONFIG_MTD_GEN_PROBE=y # CONFIG_MTD_CFI_ADV_OPTIONS is not set CONFIG_MTD_MAP_BANK_WIDTH_1=y CONFIG_MTD_MAP_BANK_WIDTH_2=y CONFIG_MTD_MAP_BANK_WIDTH_4=y # CONFIG_MTD_MAP_BANK_WIDTH_8 is not set # CONFIG_MTD_MAP_BANK_WIDTH_16 is not set # CONFIG_MTD_MAP_BANK_WIDTH_32 is not set CONFIG_MTD_CFI_I1=y CONFIG_MTD_CFI_I2=y # CONFIG_MTD_CFI_I4 is not set # CONFIG_MTD_CFI_I8 is not set CONFIG_MTD_CFI_INTELEXT=y # CONFIG_MTD_CFI_AMDSTD is not set # CONFIG_MTD_CFI_STAA is not set CONFIG_MTD_CFI_UTIL=y # CONFIG_MTD_RAM is not set # CONFIG_MTD_ROM is not set # CONFIG_MTD_ABSENT is not set # # Mapping drivers for chip access # # CONFIG_MTD_COMPLEX_MAPPINGS is not set # CONFIG_MTD_PHYSMAP is not set # CONFIG_MTD_PHYSMAP_OF is not set # CONFIG_MTD_PLATRAM is not set # # Self-contained MTD device drivers # # CONFIG_MTD_DATAFLASH is not set # CONFIG_MTD_M25P80 is not set # CONFIG_MTD_SST25L is not set # CONFIG_MTD_SLRAM is not set # CONFIG_MTD_PHRAM is not set # CONFIG_MTD_MTDRAM is not set # CONFIG_MTD_BLOCK2MTD is not set # # Disk-On-Chip Device Drivers # # CONFIG_MTD_DOCG3 is not set CONFIG_MTD_NAND_ECC=y # CONFIG_MTD_NAND_ECC_SMC is not set CONFIG_MTD_NAND=y # CONFIG_MTD_NAND_ECC_BCH is not set # CONFIG_MTD_SM_COMMON is not set # CONFIG_MTD_NAND_DENALI is not set # CONFIG_MTD_NAND_GPIO is not set CONFIG_MTD_NAND_OMAP2=y # CONFIG_MTD_NAND_OMAP_BCH is not set CONFIG_MTD_NAND_IDS=y # CONFIG_MTD_NAND_DISKONCHIP is not set # CONFIG_MTD_NAND_DOCG4 is not set # CONFIG_MTD_NAND_NANDSIM is not set # CONFIG_MTD_NAND_PLATFORM is not set # CONFIG_MTD_ALAUDA is not set CONFIG_MTD_ONENAND=y CONFIG_MTD_ONENAND_VERIFY_WRITE=y # CONFIG_MTD_ONENAND_GENERIC is not set CONFIG_MTD_ONENAND_OMAP2=y # CONFIG_MTD_ONENAND_OTP is not set # CONFIG_MTD_ONENAND_2X_PROGRAM is not set # # LPDDR flash memory drivers # # CONFIG_MTD_LPDDR is not set CONFIG_MTD_UBI=y CONFIG_MTD_UBI_WL_THRESHOLD=4096 CONFIG_MTD_UBI_BEB_LIMIT=20 # CONFIG_MTD_UBI_FASTMAP is not set # CONFIG_MTD_UBI_GLUEBI is not set CONFIG_DTC=y CONFIG_OF=y # # Device Tree and Open Firmware support # CONFIG_PROC_DEVICETREE=y # CONFIG_OF_SELFTEST is not set CONFIG_OF_FLATTREE=y CONFIG_OF_EARLY_FLATTREE=y CONFIG_OF_ADDRESS=y CONFIG_OF_IRQ=y CONFIG_OF_DEVICE=y CONFIG_OF_I2C=y CONFIG_OF_NET=y CONFIG_OF_MDIO=y CONFIG_OF_MTD=y # CONFIG_PARPORT is not set CONFIG_BLK_DEV=y # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_LOOP_MIN_COUNT=8 # CONFIG_BLK_DEV_CRYPTOLOOP is not set # CONFIG_BLK_DEV_DRBD is not set # CONFIG_BLK_DEV_NBD is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=16384 # CONFIG_BLK_DEV_XIP is not set # CONFIG_CDROM_PKTCDVD is not set # CONFIG_ATA_OVER_ETH is not set # CONFIG_MG_DISK is not set # CONFIG_BLK_DEV_RBD is not set # CONFIG_BLOCKCONSOLE is not set # # Misc devices # CONFIG_SENSORS_LIS3LV02D=m # CONFIG_AD525X_DPOT is not set # CONFIG_ATMEL_PWM is not set # CONFIG_DUMMY_IRQ is not set # CONFIG_ICS932S401 is not set # CONFIG_ATMEL_SSC is not set # CONFIG_ENCLOSURE_SERVICES is not set # CONFIG_APDS9802ALS is not set # CONFIG_ISL29003 is not set # CONFIG_ISL29020 is not set CONFIG_SENSORS_TSL2550=m # CONFIG_SENSORS_BH1780 is not set # CONFIG_SENSORS_BH1770 is not set # CONFIG_SENSORS_APDS990X is not set # CONFIG_HMC6352 is not set # CONFIG_DS1682 is not set # CONFIG_TI_DAC7512 is not set # CONFIG_ARM_CHARLCD is not set CONFIG_BMP085=y CONFIG_BMP085_I2C=m # CONFIG_BMP085_SPI is not set # CONFIG_USB_SWITCH_FSA9480 is not set # CONFIG_LATTICE_ECP3_CONFIG is not set # CONFIG_SRAM is not set # CONFIG_C2PORT is not set # # EEPROM support # # CONFIG_EEPROM_AT24 is not set # CONFIG_EEPROM_AT25 is not set # CONFIG_EEPROM_LEGACY is not set # CONFIG_EEPROM_MAX6875 is not set CONFIG_EEPROM_93CX6=y # CONFIG_EEPROM_93XX46 is not set # # Texas Instruments shared transport line discipline # # CONFIG_TI_ST is not set # CONFIG_SENSORS_LIS3_SPI is not set CONFIG_SENSORS_LIS3_I2C=m # # Altera FPGA firmware download module # # CONFIG_ALTERA_STAPL is not set # # SCSI device support # CONFIG_SCSI_MOD=y # CONFIG_RAID_ATTRS is not set CONFIG_SCSI=y CONFIG_SCSI_DMA=y # CONFIG_SCSI_TGT is not set # CONFIG_SCSI_NETLINK is not set CONFIG_SCSI_PROC_FS=y # # SCSI support type (disk, tape, CD-ROM) # CONFIG_BLK_DEV_SD=y # CONFIG_CHR_DEV_ST is not set # CONFIG_CHR_DEV_OSST is not set # CONFIG_BLK_DEV_SR is not set # CONFIG_CHR_DEV_SG is not set # CONFIG_CHR_DEV_SCH is not set CONFIG_SCSI_MULTI_LUN=y # CONFIG_SCSI_CONSTANTS is not set # CONFIG_SCSI_LOGGING is not set CONFIG_SCSI_SCAN_ASYNC=y # # SCSI Transports # # CONFIG_SCSI_SPI_ATTRS is not set # CONFIG_SCSI_FC_ATTRS is not set # CONFIG_SCSI_ISCSI_ATTRS is not set # CONFIG_SCSI_SAS_ATTRS is not set # CONFIG_SCSI_SAS_LIBSAS is not set # CONFIG_SCSI_SRP_ATTRS is not set CONFIG_SCSI_LOWLEVEL=y # CONFIG_ISCSI_TCP is not set # CONFIG_ISCSI_BOOT_SYSFS is not set # CONFIG_SCSI_UFSHCD is not set # CONFIG_LIBFC is not set # CONFIG_LIBFCOE is not set # CONFIG_SCSI_DEBUG is not set # CONFIG_SCSI_DH is not set # CONFIG_SCSI_OSD_INITIATOR is not set CONFIG_HAVE_PATA_PLATFORM=y # CONFIG_ATA is not set CONFIG_MD=y # CONFIG_BLK_DEV_MD is not set # CONFIG_BCACHE is not set # CONFIG_BLK_DEV_DM is not set # CONFIG_TARGET_CORE is not set CONFIG_NETDEVICES=y CONFIG_NET_CORE=y # CONFIG_BONDING is not set # CONFIG_DUMMY is not set # CONFIG_EQUALIZER is not set CONFIG_MII=y # CONFIG_NET_TEAM is not set # CONFIG_MACVLAN is not set # CONFIG_VXLAN is not set # CONFIG_NETCONSOLE is not set # CONFIG_NETPOLL is not set # CONFIG_NET_POLL_CONTROLLER is not set # CONFIG_TUN is not set # CONFIG_VETH is not set # # CAIF transport drivers # # # Distributed Switch Architecture drivers # # CONFIG_NET_DSA_MV88E6XXX is not set # CONFIG_NET_DSA_MV88E6060 is not set # CONFIG_NET_DSA_MV88E6XXX_NEED_PPU is not set # CONFIG_NET_DSA_MV88E6131 is not set # CONFIG_NET_DSA_MV88E6123_61_65 is not set CONFIG_ETHERNET=y CONFIG_NET_CADENCE=y # CONFIG_ARM_AT91_ETHER is not set # CONFIG_MACB is not set CONFIG_NET_VENDOR_BROADCOM=y # CONFIG_B44 is not set # CONFIG_NET_CALXEDA_XGMAC is not set CONFIG_NET_VENDOR_CIRRUS=y # CONFIG_CS89x0 is not set # CONFIG_DM9000 is not set # CONFIG_DNET is not set CONFIG_NET_VENDOR_FARADAY=y # CONFIG_FTMAC100 is not set # CONFIG_FTGMAC100 is not set CONFIG_NET_VENDOR_INTEL=y CONFIG_NET_VENDOR_I825XX=y CONFIG_NET_VENDOR_MARVELL=y # CONFIG_MVMDIO is not set CONFIG_NET_VENDOR_MICREL=y # CONFIG_KS8842 is not set CONFIG_KS8851=y CONFIG_KS8851_MLL=y CONFIG_NET_VENDOR_MICROCHIP=y # CONFIG_ENC28J60 is not set CONFIG_NET_VENDOR_NATSEMI=y CONFIG_NET_VENDOR_8390=y # CONFIG_AX88796 is not set # CONFIG_ETHOC is not set CONFIG_NET_VENDOR_SEEQ=y CONFIG_NET_VENDOR_SMSC=y CONFIG_SMC91X=y # CONFIG_SMC911X is not set CONFIG_SMSC911X=y # CONFIG_SMSC911X_ARCH_HOOKS is not set CONFIG_NET_VENDOR_STMICRO=y # CONFIG_STMMAC_ETH is not set CONFIG_NET_VENDOR_TI=y # CONFIG_TI_DAVINCI_EMAC is not set CONFIG_TI_DAVINCI_MDIO=y CONFIG_TI_DAVINCI_CPDMA=y CONFIG_TI_CPSW=y # CONFIG_TI_CPTS is not set CONFIG_NET_VENDOR_WIZNET=y # CONFIG_WIZNET_W5100 is not set # CONFIG_WIZNET_W5300 is not set CONFIG_PHYLIB=y # # MII PHY device drivers # # CONFIG_AT803X_PHY is not set # CONFIG_AMD_PHY is not set # CONFIG_MARVELL_PHY is not set # CONFIG_DAVICOM_PHY is not set # CONFIG_QSEMI_PHY is not set # CONFIG_LXT_PHY is not set # CONFIG_CICADA_PHY is not set # CONFIG_VITESSE_PHY is not set CONFIG_SMSC_PHY=y # CONFIG_BROADCOM_PHY is not set # CONFIG_BCM87XX_PHY is not set # CONFIG_ICPLUS_PHY is not set # CONFIG_REALTEK_PHY is not set # CONFIG_NATIONAL_PHY is not set # CONFIG_STE10XP is not set # CONFIG_LSI_ET1011C_PHY is not set # CONFIG_MICREL_PHY is not set # CONFIG_FIXED_PHY is not set # CONFIG_MDIO_BITBANG is not set # CONFIG_MDIO_BUS_MUX_GPIO is not set # CONFIG_MDIO_BUS_MUX_MMIOREG is not set # CONFIG_MICREL_KS8995MA is not set # CONFIG_PPP is not set # CONFIG_SLIP is not set # # USB Network Adapters # # CONFIG_USB_CATC is not set # CONFIG_USB_KAWETH is not set # CONFIG_USB_PEGASUS is not set # CONFIG_USB_RTL8150 is not set CONFIG_USB_USBNET=y CONFIG_USB_NET_AX8817X=y CONFIG_USB_NET_AX88179_178A=y CONFIG_USB_NET_CDCETHER=y # CONFIG_USB_NET_CDC_EEM is not set CONFIG_USB_NET_CDC_NCM=y # CONFIG_USB_NET_CDC_MBIM is not set # CONFIG_USB_NET_DM9601 is not set # CONFIG_USB_NET_SMSC75XX is not set CONFIG_USB_NET_SMSC95XX=y # CONFIG_USB_NET_GL620A is not set CONFIG_USB_NET_NET1080=y # CONFIG_USB_NET_PLUSB is not set # CONFIG_USB_NET_MCS7830 is not set # CONFIG_USB_NET_RNDIS_HOST is not set CONFIG_USB_NET_CDC_SUBSET=y CONFIG_USB_ALI_M5632=y CONFIG_USB_AN2720=y CONFIG_USB_BELKIN=y CONFIG_USB_ARMLINUX=y CONFIG_USB_EPSON2888=y CONFIG_USB_KC2190=y CONFIG_USB_NET_ZAURUS=y # CONFIG_USB_NET_CX82310_ETH is not set # CONFIG_USB_NET_KALMIA is not set # CONFIG_USB_NET_QMI_WWAN is not set # CONFIG_USB_NET_INT51X1 is not set # CONFIG_USB_IPHETH is not set # CONFIG_USB_SIERRA_NET is not set # CONFIG_USB_VL600 is not set CONFIG_WLAN=y # CONFIG_LIBERTAS_THINFIRM is not set # CONFIG_AT76C50X_USB is not set # CONFIG_USB_ZD1201 is not set # CONFIG_USB_NET_RNDIS_WLAN is not set # CONFIG_RTL8187 is not set # CONFIG_MAC80211_HWSIM is not set # CONFIG_ATH_CARDS is not set # CONFIG_B43 is not set # CONFIG_B43LEGACY is not set # CONFIG_BRCMFMAC is not set # CONFIG_HOSTAP is not set CONFIG_LIBERTAS=m CONFIG_LIBERTAS_USB=m CONFIG_LIBERTAS_SDIO=m # CONFIG_LIBERTAS_SPI is not set CONFIG_LIBERTAS_DEBUG=y # CONFIG_LIBERTAS_MESH is not set # CONFIG_P54_COMMON is not set # CONFIG_RT2X00 is not set # CONFIG_RTLWIFI is not set # CONFIG_WL_TI is not set # CONFIG_ZD1211RW is not set # CONFIG_MWIFIEX is not set # # Enable WiMAX (Networking options) to see the WiMAX drivers # # CONFIG_WAN is not set # CONFIG_ISDN is not set # # Input device support # CONFIG_INPUT=y # CONFIG_INPUT_FF_MEMLESS is not set CONFIG_INPUT_POLLDEV=m # CONFIG_INPUT_SPARSEKMAP is not set CONFIG_INPUT_MATRIXKMAP=y # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_JOYDEV=y CONFIG_INPUT_EVDEV=y # CONFIG_INPUT_EVBUG is not set # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y # CONFIG_KEYBOARD_ADP5588 is not set # CONFIG_KEYBOARD_ADP5589 is not set CONFIG_KEYBOARD_ATKBD=y # CONFIG_KEYBOARD_QT1070 is not set # CONFIG_KEYBOARD_QT2160 is not set # CONFIG_KEYBOARD_LKKBD is not set CONFIG_KEYBOARD_GPIO=y # CONFIG_KEYBOARD_TCA6416 is not set # CONFIG_KEYBOARD_TCA8418 is not set CONFIG_KEYBOARD_MATRIX=m # CONFIG_KEYBOARD_LM8323 is not set # CONFIG_KEYBOARD_LM8333 is not set # CONFIG_KEYBOARD_MAX7359 is not set # CONFIG_KEYBOARD_MCS is not set # CONFIG_KEYBOARD_MPR121 is not set # CONFIG_KEYBOARD_NEWTON is not set # CONFIG_KEYBOARD_OPENCORES is not set # CONFIG_KEYBOARD_SAMSUNG is not set # CONFIG_KEYBOARD_STOWAWAY is not set # CONFIG_KEYBOARD_SUNKBD is not set # CONFIG_KEYBOARD_OMAP4 is not set CONFIG_KEYBOARD_TWL4030=y # CONFIG_KEYBOARD_XTKBD is not set CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=y CONFIG_MOUSE_PS2_ALPS=y CONFIG_MOUSE_PS2_LOGIPS2PP=y CONFIG_MOUSE_PS2_SYNAPTICS=y CONFIG_MOUSE_PS2_CYPRESS=y CONFIG_MOUSE_PS2_TRACKPOINT=y # CONFIG_MOUSE_PS2_ELANTECH is not set # CONFIG_MOUSE_PS2_SENTELIC is not set # CONFIG_MOUSE_PS2_TOUCHKIT is not set # CONFIG_MOUSE_SERIAL is not set # CONFIG_MOUSE_APPLETOUCH is not set # CONFIG_MOUSE_BCM5974 is not set # CONFIG_MOUSE_CYAPA is not set # CONFIG_MOUSE_VSXXXAA is not set # CONFIG_MOUSE_GPIO is not set # CONFIG_MOUSE_SYNAPTICS_I2C is not set # CONFIG_MOUSE_SYNAPTICS_USB is not set # CONFIG_INPUT_JOYSTICK is not set # CONFIG_INPUT_TABLET is not set CONFIG_INPUT_TOUCHSCREEN=y CONFIG_TOUCHSCREEN_ADS7846=y # CONFIG_TOUCHSCREEN_AD7877 is not set # CONFIG_TOUCHSCREEN_AD7879 is not set # CONFIG_TOUCHSCREEN_ATMEL_MXT is not set # CONFIG_TOUCHSCREEN_AUO_PIXCIR is not set # CONFIG_TOUCHSCREEN_BU21013 is not set # CONFIG_TOUCHSCREEN_CY8CTMG110 is not set # CONFIG_TOUCHSCREEN_CYTTSP_CORE is not set # CONFIG_TOUCHSCREEN_DYNAPRO is not set # CONFIG_TOUCHSCREEN_HAMPSHIRE is not set # CONFIG_TOUCHSCREEN_EETI is not set # CONFIG_TOUCHSCREEN_EGALAX is not set # CONFIG_TOUCHSCREEN_FUJITSU is not set # CONFIG_TOUCHSCREEN_ILI210X is not set # CONFIG_TOUCHSCREEN_GUNZE is not set # CONFIG_TOUCHSCREEN_ELO is not set # CONFIG_TOUCHSCREEN_WACOM_W8001 is not set # CONFIG_TOUCHSCREEN_WACOM_I2C is not set # CONFIG_TOUCHSCREEN_MAX11801 is not set # CONFIG_TOUCHSCREEN_MCS5000 is not set # CONFIG_TOUCHSCREEN_MMS114 is not set # CONFIG_TOUCHSCREEN_MTOUCH is not set # CONFIG_TOUCHSCREEN_INEXIO is not set # CONFIG_TOUCHSCREEN_MK712 is not set # CONFIG_TOUCHSCREEN_PENMOUNT is not set # CONFIG_TOUCHSCREEN_EDT_FT5X06 is not set # CONFIG_TOUCHSCREEN_TOUCHRIGHT is not set # CONFIG_TOUCHSCREEN_TOUCHWIN is not set # CONFIG_TOUCHSCREEN_PIXCIR is not set # CONFIG_TOUCHSCREEN_USB_COMPOSITE is not set # CONFIG_TOUCHSCREEN_TOUCHIT213 is not set # CONFIG_TOUCHSCREEN_TSC_SERIO is not set # CONFIG_TOUCHSCREEN_TSC2005 is not set # CONFIG_TOUCHSCREEN_TSC2007 is not set # CONFIG_TOUCHSCREEN_W90X900 is not set # CONFIG_TOUCHSCREEN_ST1232 is not set # CONFIG_TOUCHSCREEN_TPS6507X is not set CONFIG_INPUT_MISC=y # CONFIG_INPUT_AD714X is not set # CONFIG_INPUT_BMA150 is not set # CONFIG_INPUT_MMA8450 is not set # CONFIG_INPUT_MPU3050 is not set # CONFIG_INPUT_GP2A is not set # CONFIG_INPUT_GPIO_TILT_POLLED is not set # CONFIG_INPUT_ATI_REMOTE2 is not set # CONFIG_INPUT_KEYSPAN_REMOTE is not set # CONFIG_INPUT_KXTJ9 is not set # CONFIG_INPUT_POWERMATE is not set # CONFIG_INPUT_YEALINK is not set # CONFIG_INPUT_CM109 is not set CONFIG_INPUT_TWL4030_PWRBUTTON=y # CONFIG_INPUT_TWL4030_VIBRA is not set # CONFIG_INPUT_UINPUT is not set # CONFIG_INPUT_PCF8574 is not set # CONFIG_INPUT_GPIO_ROTARY_ENCODER is not set # CONFIG_INPUT_ADXL34X is not set # CONFIG_INPUT_IMS_PCU is not set # CONFIG_INPUT_CMA3000 is not set # # Hardware I/O ports # CONFIG_SERIO=y CONFIG_SERIO_SERPORT=y # CONFIG_SERIO_AMBAKMI is not set CONFIG_SERIO_LIBPS2=y # CONFIG_SERIO_RAW is not set # CONFIG_SERIO_ALTERA_PS2 is not set # CONFIG_SERIO_PS2MULT is not set # CONFIG_SERIO_ARC_PS2 is not set # CONFIG_SERIO_APBPS2 is not set # CONFIG_GAMEPORT is not set # # Character devices # CONFIG_TTY=y CONFIG_VT=y CONFIG_CONSOLE_TRANSLATIONS=y CONFIG_VT_CONSOLE=y CONFIG_VT_CONSOLE_SLEEP=y CONFIG_HW_CONSOLE=y CONFIG_VT_HW_CONSOLE_BINDING=y CONFIG_UNIX98_PTYS=y # CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set # CONFIG_LEGACY_PTYS is not set # CONFIG_SERIAL_NONSTANDARD is not set # CONFIG_N_GSM is not set # CONFIG_TRACE_SINK is not set CONFIG_DEVKMEM=y # # Serial drivers # CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_DEPRECATED_OPTIONS=y CONFIG_SERIAL_8250_CONSOLE=y CONFIG_SERIAL_8250_DMA=y CONFIG_SERIAL_8250_NR_UARTS=32 CONFIG_SERIAL_8250_RUNTIME_UARTS=4 CONFIG_SERIAL_8250_EXTENDED=y CONFIG_SERIAL_8250_MANY_PORTS=y CONFIG_SERIAL_8250_SHARE_IRQ=y CONFIG_SERIAL_8250_DETECT_IRQ=y CONFIG_SERIAL_8250_RSA=y # CONFIG_SERIAL_8250_DW is not set # CONFIG_SERIAL_8250_EM is not set # # Non-8250 serial port support # # CONFIG_SERIAL_AMBA_PL010 is not set CONFIG_SERIAL_AMBA_PL011=y CONFIG_SERIAL_AMBA_PL011_CONSOLE=y # CONFIG_SERIAL_MAX3100 is not set # CONFIG_SERIAL_MAX310X is not set CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y # CONFIG_SERIAL_OF_PLATFORM is not set CONFIG_SERIAL_OMAP=y CONFIG_SERIAL_OMAP_CONSOLE=y # CONFIG_SERIAL_SCCNXP is not set # CONFIG_SERIAL_TIMBERDALE is not set # CONFIG_SERIAL_ALTERA_JTAGUART is not set # CONFIG_SERIAL_ALTERA_UART is not set # CONFIG_SERIAL_IFX6X60 is not set # CONFIG_SERIAL_XILINX_PS_UART is not set # CONFIG_SERIAL_ARC is not set # CONFIG_TTY_PRINTK is not set # CONFIG_HVC_DCC is not set # CONFIG_IPMI_HANDLER is not set CONFIG_HW_RANDOM=y # CONFIG_HW_RANDOM_TIMERIOMEM is not set # CONFIG_HW_RANDOM_ATMEL is not set CONFIG_HW_RANDOM_OMAP=y # CONFIG_HW_RANDOM_EXYNOS is not set # CONFIG_R3964 is not set # CONFIG_RAW_DRIVER is not set # CONFIG_TCG_TPM is not set CONFIG_I2C=y CONFIG_I2C_BOARDINFO=y CONFIG_I2C_COMPAT=y CONFIG_I2C_CHARDEV=y # CONFIG_I2C_MUX is not set CONFIG_I2C_HELPER_AUTO=y # # I2C Hardware Bus support # # # I2C system bus drivers (mostly embedded / system-on-chip) # # CONFIG_I2C_CBUS_GPIO is not set # CONFIG_I2C_DESIGNWARE_PLATFORM is not set # CONFIG_I2C_GPIO is not set # CONFIG_I2C_NOMADIK is not set # CONFIG_I2C_OCORES is not set CONFIG_I2C_OMAP=y # CONFIG_I2C_PCA_PLATFORM is not set # CONFIG_I2C_PXA_PCI is not set # CONFIG_I2C_SIMTEC is not set # CONFIG_I2C_VERSATILE is not set # CONFIG_I2C_XILINX is not set # # External I2C/SMBus adapter drivers # # CONFIG_I2C_DIOLAN_U2C is not set # CONFIG_I2C_PARPORT_LIGHT is not set # CONFIG_I2C_TAOS_EVM is not set # CONFIG_I2C_TINY_USB is not set # # Other I2C/SMBus bus drivers # # CONFIG_I2C_STUB is not set # CONFIG_I2C_DEBUG_CORE is not set # CONFIG_I2C_DEBUG_ALGO is not set # CONFIG_I2C_DEBUG_BUS is not set CONFIG_SPI=y # CONFIG_SPI_DEBUG is not set CONFIG_SPI_MASTER=y # # SPI Master Controller Drivers # # CONFIG_SPI_ALTERA is not set # CONFIG_SPI_BITBANG is not set # CONFIG_SPI_GPIO is not set # CONFIG_SPI_FSL_SPI is not set # CONFIG_SPI_OC_TINY is not set CONFIG_SPI_OMAP24XX=y # CONFIG_SPI_PL022 is not set # CONFIG_SPI_PXA2XX_PCI is not set # CONFIG_SPI_SC18IS602 is not set # CONFIG_SPI_XCOMM is not set # CONFIG_SPI_XILINX is not set # CONFIG_SPI_DESIGNWARE is not set # # SPI Protocol Masters # # CONFIG_SPI_SPIDEV is not set # CONFIG_SPI_TLE62X0 is not set # # Qualcomm MSM SSBI bus support # # CONFIG_SSBI is not set # CONFIG_HSI is not set # # PPS support # # CONFIG_PPS is not set # # PPS generators support # # # PTP clock support # # CONFIG_PTP_1588_CLOCK is not set # # Enable PHYLIB and NETWORK_PHY_TIMESTAMPING to see the additional clocks. # # CONFIG_PTP_1588_CLOCK_PCH is not set CONFIG_PINCTRL=y # # Pin controllers # CONFIG_PINMUX=y CONFIG_PINCONF=y CONFIG_GENERIC_PINCONF=y # CONFIG_DEBUG_PINCTRL is not set CONFIG_PINCTRL_SINGLE=y # CONFIG_PINCTRL_EXYNOS is not set # CONFIG_PINCTRL_EXYNOS5440 is not set CONFIG_ARCH_HAVE_CUSTOM_GPIO_H=y CONFIG_ARCH_REQUIRE_GPIOLIB=y CONFIG_GPIO_DEVRES=y CONFIG_GPIOLIB=y CONFIG_OF_GPIO=y CONFIG_DEBUG_GPIO=y CONFIG_GPIO_SYSFS=y # # Memory mapped GPIO drivers: # # CONFIG_GPIO_GENERIC_PLATFORM is not set # CONFIG_GPIO_EM is not set # CONFIG_GPIO_PL061 is not set # CONFIG_GPIO_RCAR is not set # CONFIG_GPIO_TS5500 is not set # # I2C GPIO expanders: # # CONFIG_GPIO_MAX7300 is not set # CONFIG_GPIO_MAX732X is not set # CONFIG_GPIO_PCF857X is not set # CONFIG_GPIO_SX150X is not set CONFIG_GPIO_TWL4030=y # CONFIG_GPIO_ADP5588 is not set # CONFIG_GPIO_ADNP is not set # # PCI GPIO expanders: # # # SPI GPIO expanders: # # CONFIG_GPIO_MAX7301 is not set # CONFIG_GPIO_MCP23S08 is not set # CONFIG_GPIO_MC33880 is not set # CONFIG_GPIO_74X164 is not set # # AC97 GPIO expanders: # # # MODULbus GPIO expanders: # # CONFIG_GPIO_TPS65910 is not set # # USB GPIO expanders: # CONFIG_W1=y CONFIG_W1_CON=y # # 1-wire Bus Masters # # CONFIG_W1_MASTER_DS2490 is not set # CONFIG_W1_MASTER_DS2482 is not set # CONFIG_W1_MASTER_DS1WM is not set # CONFIG_W1_MASTER_GPIO is not set # CONFIG_HDQ_MASTER_OMAP is not set # # 1-wire Slaves # # CONFIG_W1_SLAVE_THERM is not set # CONFIG_W1_SLAVE_SMEM is not set # CONFIG_W1_SLAVE_DS2408 is not set # CONFIG_W1_SLAVE_DS2413 is not set # CONFIG_W1_SLAVE_DS2423 is not set # CONFIG_W1_SLAVE_DS2431 is not set # CONFIG_W1_SLAVE_DS2433 is not set # CONFIG_W1_SLAVE_DS2760 is not set # CONFIG_W1_SLAVE_DS2780 is not set # CONFIG_W1_SLAVE_DS2781 is not set # CONFIG_W1_SLAVE_DS28E04 is not set # CONFIG_W1_SLAVE_BQ27000 is not set CONFIG_POWER_SUPPLY=y # CONFIG_POWER_SUPPLY_DEBUG is not set # CONFIG_PDA_POWER is not set # CONFIG_TEST_POWER is not set # CONFIG_BATTERY_DS2780 is not set # CONFIG_BATTERY_DS2781 is not set # CONFIG_BATTERY_DS2782 is not set # CONFIG_BATTERY_SBS is not set # CONFIG_BATTERY_BQ27x00 is not set # CONFIG_BATTERY_MAX17040 is not set # CONFIG_BATTERY_MAX17042 is not set # CONFIG_CHARGER_ISP1704 is not set # CONFIG_CHARGER_MAX8903 is not set # CONFIG_CHARGER_TWL4030 is not set # CONFIG_CHARGER_LP8727 is not set # CONFIG_CHARGER_GPIO is not set # CONFIG_CHARGER_MANAGER is not set # CONFIG_CHARGER_BQ2415X is not set # CONFIG_CHARGER_SMB347 is not set # CONFIG_BATTERY_GOLDFISH is not set CONFIG_POWER_RESET=y # CONFIG_POWER_RESET_GPIO is not set # CONFIG_POWER_RESET_RESTART is not set CONFIG_POWER_RESET_VEXPRESS=y # CONFIG_POWER_AVS is not set CONFIG_HWMON=y # CONFIG_HWMON_VID is not set # CONFIG_HWMON_DEBUG_CHIP is not set # # Native drivers # # CONFIG_SENSORS_AD7314 is not set # CONFIG_SENSORS_AD7414 is not set # CONFIG_SENSORS_AD7418 is not set # CONFIG_SENSORS_ADCXX is not set # CONFIG_SENSORS_ADM1021 is not set # CONFIG_SENSORS_ADM1025 is not set # CONFIG_SENSORS_ADM1026 is not set # CONFIG_SENSORS_ADM1029 is not set # CONFIG_SENSORS_ADM1031 is not set # CONFIG_SENSORS_ADM9240 is not set # CONFIG_SENSORS_ADT7310 is not set # CONFIG_SENSORS_ADT7410 is not set # CONFIG_SENSORS_ADT7411 is not set # CONFIG_SENSORS_ADT7462 is not set # CONFIG_SENSORS_ADT7470 is not set # CONFIG_SENSORS_ADT7475 is not set # CONFIG_SENSORS_ASC7621 is not set # CONFIG_SENSORS_ATXP1 is not set # CONFIG_SENSORS_DS620 is not set # CONFIG_SENSORS_DS1621 is not set # CONFIG_SENSORS_F71805F is not set # CONFIG_SENSORS_F71882FG is not set # CONFIG_SENSORS_F75375S is not set # CONFIG_SENSORS_G760A is not set # CONFIG_SENSORS_GL518SM is not set # CONFIG_SENSORS_GL520SM is not set # CONFIG_SENSORS_GPIO_FAN is not set # CONFIG_SENSORS_HIH6130 is not set # CONFIG_SENSORS_IT87 is not set # CONFIG_SENSORS_JC42 is not set # CONFIG_SENSORS_LINEAGE is not set # CONFIG_SENSORS_LM63 is not set # CONFIG_SENSORS_LM70 is not set # CONFIG_SENSORS_LM73 is not set CONFIG_SENSORS_LM75=m # CONFIG_SENSORS_LM77 is not set # CONFIG_SENSORS_LM78 is not set # CONFIG_SENSORS_LM80 is not set # CONFIG_SENSORS_LM83 is not set # CONFIG_SENSORS_LM85 is not set # CONFIG_SENSORS_LM87 is not set # CONFIG_SENSORS_LM90 is not set # CONFIG_SENSORS_LM92 is not set # CONFIG_SENSORS_LM93 is not set # CONFIG_SENSORS_LTC4151 is not set # CONFIG_SENSORS_LTC4215 is not set # CONFIG_SENSORS_LTC4245 is not set # CONFIG_SENSORS_LTC4261 is not set # CONFIG_SENSORS_LM95234 is not set # CONFIG_SENSORS_LM95241 is not set # CONFIG_SENSORS_LM95245 is not set # CONFIG_SENSORS_MAX1111 is not set # CONFIG_SENSORS_MAX16065 is not set # CONFIG_SENSORS_MAX1619 is not set # CONFIG_SENSORS_MAX1668 is not set # CONFIG_SENSORS_MAX197 is not set # CONFIG_SENSORS_MAX6639 is not set # CONFIG_SENSORS_MAX6642 is not set # CONFIG_SENSORS_MAX6650 is not set # CONFIG_SENSORS_MAX6697 is not set # CONFIG_SENSORS_MCP3021 is not set # CONFIG_SENSORS_NCT6775 is not set # CONFIG_SENSORS_PC87360 is not set # CONFIG_SENSORS_PC87427 is not set # CONFIG_SENSORS_PCF8591 is not set # CONFIG_PMBUS is not set # CONFIG_SENSORS_SHT15 is not set # CONFIG_SENSORS_SHT21 is not set # CONFIG_SENSORS_SMM665 is not set # CONFIG_SENSORS_DME1737 is not set # CONFIG_SENSORS_EMC1403 is not set # CONFIG_SENSORS_EMC2103 is not set # CONFIG_SENSORS_EMC6W201 is not set # CONFIG_SENSORS_SMSC47M1 is not set # CONFIG_SENSORS_SMSC47M192 is not set # CONFIG_SENSORS_SMSC47B397 is not set # CONFIG_SENSORS_SCH56XX_COMMON is not set # CONFIG_SENSORS_SCH5627 is not set # CONFIG_SENSORS_SCH5636 is not set # CONFIG_SENSORS_ADS1015 is not set # CONFIG_SENSORS_ADS7828 is not set # CONFIG_SENSORS_ADS7871 is not set # CONFIG_SENSORS_AMC6821 is not set # CONFIG_SENSORS_INA209 is not set # CONFIG_SENSORS_INA2XX is not set # CONFIG_SENSORS_THMC50 is not set # CONFIG_SENSORS_TMP102 is not set # CONFIG_SENSORS_TMP401 is not set # CONFIG_SENSORS_TMP421 is not set # CONFIG_SENSORS_VEXPRESS is not set # CONFIG_SENSORS_VT1211 is not set # CONFIG_SENSORS_W83781D is not set # CONFIG_SENSORS_W83791D is not set # CONFIG_SENSORS_W83792D is not set # CONFIG_SENSORS_W83793 is not set # CONFIG_SENSORS_W83795 is not set # CONFIG_SENSORS_W83L785TS is not set # CONFIG_SENSORS_W83L786NG is not set # CONFIG_SENSORS_W83627HF is not set # CONFIG_SENSORS_W83627EHF is not set # CONFIG_THERMAL is not set CONFIG_WATCHDOG=y CONFIG_WATCHDOG_CORE=y # CONFIG_WATCHDOG_NOWAYOUT is not set # # Watchdog Device Drivers # # CONFIG_SOFT_WATCHDOG is not set # CONFIG_ARM_SP805_WATCHDOG is not set # CONFIG_DW_WATCHDOG is not set # CONFIG_MPCORE_WATCHDOG is not set CONFIG_OMAP_WATCHDOG=y CONFIG_TWL4030_WATCHDOG=y # CONFIG_MAX63XX_WATCHDOG is not set # # USB-based Watchdog Cards # # CONFIG_USBPCWATCHDOG is not set CONFIG_SSB_POSSIBLE=y # # Sonics Silicon Backplane # # CONFIG_SSB is not set CONFIG_BCMA_POSSIBLE=y # # Broadcom specific AMBA # # CONFIG_BCMA is not set # # Multifunction device drivers # CONFIG_MFD_CORE=y # CONFIG_MFD_AS3711 is not set # CONFIG_PMIC_ADP5520 is not set # CONFIG_MFD_AAT2870_CORE is not set # CONFIG_MFD_CROS_EC is not set # CONFIG_MFD_ASIC3 is not set # CONFIG_PMIC_DA903X is not set # CONFIG_MFD_DA9052_SPI is not set # CONFIG_MFD_DA9052_I2C is not set # CONFIG_MFD_DA9055 is not set # CONFIG_MFD_MC13XXX_SPI is not set # CONFIG_MFD_MC13XXX_I2C is not set # CONFIG_HTC_EGPIO is not set # CONFIG_HTC_PASIC3 is not set # CONFIG_HTC_I2CPLD is not set # CONFIG_MFD_88PM800 is not set # CONFIG_MFD_88PM805 is not set # CONFIG_MFD_88PM860X is not set # CONFIG_MFD_MAX77686 is not set # CONFIG_MFD_MAX77693 is not set # CONFIG_MFD_MAX8907 is not set # CONFIG_MFD_MAX8925 is not set # CONFIG_MFD_MAX8997 is not set # CONFIG_MFD_MAX8998 is not set # CONFIG_EZX_PCAP is not set # CONFIG_MFD_VIPERBOARD is not set # CONFIG_MFD_RETU is not set # CONFIG_MFD_PCF50633 is not set # CONFIG_MFD_RC5T583 is not set # CONFIG_MFD_SEC_CORE is not set # CONFIG_MFD_SM501 is not set # CONFIG_MFD_SMSC is not set # CONFIG_ABX500_CORE is not set # CONFIG_MFD_STMPE is not set # CONFIG_MFD_SYSCON is not set # CONFIG_MFD_TI_AM335X_TSCADC is not set # CONFIG_MFD_LP8788 is not set # CONFIG_MFD_PALMAS is not set # CONFIG_TPS6105X is not set # CONFIG_TPS65010 is not set # CONFIG_TPS6507X is not set # CONFIG_MFD_TPS65090 is not set CONFIG_MFD_TPS65217=y # CONFIG_MFD_TPS6586X is not set CONFIG_MFD_TPS65910=y # CONFIG_MFD_TPS65912 is not set # CONFIG_MFD_TPS65912_I2C is not set # CONFIG_MFD_TPS65912_SPI is not set # CONFIG_MFD_TPS80031 is not set CONFIG_TWL4030_CORE=y # CONFIG_TWL4030_MADC is not set CONFIG_TWL4030_POWER=y CONFIG_MFD_TWL4030_AUDIO=y # CONFIG_TWL6040_CORE is not set CONFIG_MENELAUS=y # CONFIG_MFD_WL1273_CORE is not set # CONFIG_MFD_SI476X_CORE is not set # CONFIG_MFD_LM3533 is not set # CONFIG_MFD_TC3589X is not set # CONFIG_MFD_TMIO is not set # CONFIG_MFD_T7L66XB is not set # CONFIG_MFD_TC6387XB is not set # CONFIG_MFD_TC6393XB is not set # CONFIG_MFD_ARIZONA_I2C is not set # CONFIG_MFD_ARIZONA_SPI is not set # CONFIG_MFD_WM8400 is not set # CONFIG_MFD_WM831X_I2C is not set # CONFIG_MFD_WM831X_SPI is not set # CONFIG_MFD_WM8350_I2C is not set # CONFIG_MFD_WM8994 is not set CONFIG_VEXPRESS_CONFIG=y CONFIG_REGULATOR=y # CONFIG_REGULATOR_DEBUG is not set # CONFIG_REGULATOR_DUMMY is not set CONFIG_REGULATOR_FIXED_VOLTAGE=y # CONFIG_REGULATOR_VIRTUAL_CONSUMER is not set # CONFIG_REGULATOR_USERSPACE_CONSUMER is not set # CONFIG_REGULATOR_GPIO is not set # CONFIG_REGULATOR_AD5398 is not set # CONFIG_REGULATOR_FAN53555 is not set # CONFIG_REGULATOR_ISL6271A is not set # CONFIG_REGULATOR_MAX1586 is not set # CONFIG_REGULATOR_MAX8649 is not set # CONFIG_REGULATOR_MAX8660 is not set # CONFIG_REGULATOR_MAX8952 is not set # CONFIG_REGULATOR_MAX8973 is not set # CONFIG_REGULATOR_LP3971 is not set # CONFIG_REGULATOR_LP3972 is not set # CONFIG_REGULATOR_LP872X is not set # CONFIG_REGULATOR_LP8755 is not set # CONFIG_REGULATOR_TPS51632 is not set # CONFIG_REGULATOR_TPS62360 is not set CONFIG_REGULATOR_TPS65023=y CONFIG_REGULATOR_TPS6507X=y CONFIG_REGULATOR_TPS65217=y # CONFIG_REGULATOR_TPS6524X is not set CONFIG_REGULATOR_TPS65910=y CONFIG_REGULATOR_TWL4030=y # CONFIG_REGULATOR_VEXPRESS is not set # CONFIG_MEDIA_SUPPORT is not set # # Graphics support # # CONFIG_DRM is not set # CONFIG_VGASTATE is not set # CONFIG_VIDEO_OUTPUT_CONTROL is not set CONFIG_FB=y CONFIG_FIRMWARE_EDID=y # CONFIG_FB_DDC is not set # CONFIG_FB_BOOT_VESA_SUPPORT is not set CONFIG_FB_CFB_FILLRECT=m CONFIG_FB_CFB_COPYAREA=m CONFIG_FB_CFB_IMAGEBLIT=m # CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set # CONFIG_FB_SYS_FILLRECT is not set # CONFIG_FB_SYS_COPYAREA is not set # CONFIG_FB_SYS_IMAGEBLIT is not set # CONFIG_FB_FOREIGN_ENDIAN is not set # CONFIG_FB_SYS_FOPS is not set # CONFIG_FB_SVGALIB is not set # CONFIG_FB_MACMODES is not set # CONFIG_FB_BACKLIGHT is not set CONFIG_FB_MODE_HELPERS=y CONFIG_FB_TILEBLITTING=y # # Frame buffer hardware drivers # # CONFIG_FB_ARMCLCD is not set # CONFIG_FB_UVESA is not set # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_TMIO is not set # CONFIG_FB_SMSCUFX is not set # CONFIG_FB_UDL is not set # CONFIG_FB_GOLDFISH is not set # CONFIG_FB_VIRTUAL is not set # CONFIG_FB_METRONOME is not set # CONFIG_FB_BROADSHEET is not set # CONFIG_FB_AUO_K190X is not set # CONFIG_FB_SIMPLE is not set CONFIG_OMAP2_VRFB=y CONFIG_OMAP2_DSS=m # CONFIG_OMAP2_DSS_DEBUG is not set # CONFIG_OMAP2_DSS_DEBUGFS is not set CONFIG_OMAP2_DSS_DPI=y CONFIG_OMAP2_DSS_RFBI=y CONFIG_OMAP2_DSS_VENC=y CONFIG_OMAP4_DSS_HDMI=y CONFIG_OMAP2_DSS_SDI=y CONFIG_OMAP2_DSS_DSI=y CONFIG_OMAP2_DSS_MIN_FCK_PER_PCK=0 CONFIG_OMAP2_DSS_SLEEP_AFTER_VENC_RESET=y CONFIG_FB_OMAP2=m CONFIG_FB_OMAP2_DEBUG_SUPPORT=y CONFIG_FB_OMAP2_NUM_FBS=3 # # OMAP2/3 Display Device Drivers # CONFIG_PANEL_GENERIC_DPI=m CONFIG_PANEL_TFP410=m # CONFIG_PANEL_LGPHILIPS_LB035Q02 is not set CONFIG_PANEL_SHARP_LS037V7DW01=m CONFIG_PANEL_NEC_NL8048HL11_01B=m # CONFIG_PANEL_PICODLP is not set CONFIG_PANEL_TAAL=m CONFIG_PANEL_TPO_TD043MTEA1=m CONFIG_PANEL_ACX565AKM=m # CONFIG_PANEL_N8X0 is not set # CONFIG_EXYNOS_VIDEO is not set CONFIG_BACKLIGHT_LCD_SUPPORT=y CONFIG_LCD_CLASS_DEVICE=y # CONFIG_LCD_L4F00242T03 is not set # CONFIG_LCD_LMS283GF05 is not set # CONFIG_LCD_LTV350QV is not set # CONFIG_LCD_ILI922X is not set # CONFIG_LCD_ILI9320 is not set # CONFIG_LCD_TDO24M is not set # CONFIG_LCD_VGG2432A4 is not set CONFIG_LCD_PLATFORM=y # CONFIG_LCD_S6E63M0 is not set # CONFIG_LCD_LD9040 is not set # CONFIG_LCD_AMS369FG06 is not set # CONFIG_LCD_LMS501KF03 is not set # CONFIG_LCD_HX8357 is not set CONFIG_BACKLIGHT_CLASS_DEVICE=m CONFIG_BACKLIGHT_GENERIC=m # CONFIG_BACKLIGHT_ADP8860 is not set # CONFIG_BACKLIGHT_ADP8870 is not set # CONFIG_BACKLIGHT_LM3630 is not set # CONFIG_BACKLIGHT_LM3639 is not set # CONFIG_BACKLIGHT_LP855X is not set # CONFIG_BACKLIGHT_PANDORA is not set # CONFIG_BACKLIGHT_TPS65217 is not set # # Console display driver support # CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y # CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y CONFIG_FONTS=y CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y # CONFIG_FONT_6x11 is not set # CONFIG_FONT_7x14 is not set # CONFIG_FONT_PEARL_8x8 is not set # CONFIG_FONT_ACORN_8x8 is not set # CONFIG_FONT_MINI_4x6 is not set # CONFIG_FONT_SUN8x16 is not set # CONFIG_FONT_SUN12x22 is not set # CONFIG_FONT_10x18 is not set CONFIG_LOGO=y CONFIG_LOGO_LINUX_MONO=y CONFIG_LOGO_LINUX_VGA16=y CONFIG_LOGO_LINUX_CLUT224=y # CONFIG_FB_SSD1307 is not set CONFIG_SOUND=m CONFIG_SOUND_OSS_CORE=y CONFIG_SOUND_OSS_CORE_PRECLAIM=y CONFIG_SND=m CONFIG_SND_TIMER=m CONFIG_SND_PCM=m CONFIG_SND_HWDEP=m CONFIG_SND_RAWMIDI=m CONFIG_SND_COMPRESS_OFFLOAD=m CONFIG_SND_JACK=y # CONFIG_SND_SEQUENCER is not set CONFIG_SND_OSSEMUL=y CONFIG_SND_MIXER_OSS=m CONFIG_SND_PCM_OSS=m CONFIG_SND_PCM_OSS_PLUGINS=y # CONFIG_SND_HRTIMER is not set # CONFIG_SND_DYNAMIC_MINORS is not set CONFIG_SND_SUPPORT_OLD_API=y CONFIG_SND_VERBOSE_PROCFS=y CONFIG_SND_VERBOSE_PRINTK=y CONFIG_SND_DEBUG=y # CONFIG_SND_DEBUG_VERBOSE is not set # CONFIG_SND_PCM_XRUN_DEBUG is not set # CONFIG_SND_RAWMIDI_SEQ is not set # CONFIG_SND_OPL3_LIB_SEQ is not set # CONFIG_SND_OPL4_LIB_SEQ is not set # CONFIG_SND_SBAWE_SEQ is not set # CONFIG_SND_EMU10K1_SEQ is not set CONFIG_SND_DRIVERS=y # CONFIG_SND_DUMMY is not set # CONFIG_SND_ALOOP is not set # CONFIG_SND_MTPAV is not set # CONFIG_SND_SERIAL_U16550 is not set # CONFIG_SND_MPU401 is not set CONFIG_SND_ARM=y # CONFIG_SND_ARMAACI is not set CONFIG_SND_SPI=y CONFIG_SND_USB=y CONFIG_SND_USB_AUDIO=m # CONFIG_SND_USB_UA101 is not set # CONFIG_SND_USB_CAIAQ is not set # CONFIG_SND_USB_6FIRE is not set CONFIG_SND_SOC=m CONFIG_SND_SOC_DMAENGINE_PCM=y # CONFIG_SND_ATMEL_SOC is not set # CONFIG_SND_DESIGNWARE_I2S is not set CONFIG_SND_OMAP_SOC=m CONFIG_SND_OMAP_SOC_MCBSP=m # CONFIG_SND_OMAP_SOC_N810 is not set # CONFIG_SND_OMAP_SOC_RX51 is not set # CONFIG_SND_OMAP_SOC_AM3517EVM is not set CONFIG_SND_OMAP_SOC_OMAP_TWL4030=m # CONFIG_SND_OMAP_SOC_OMAP_HDMI is not set CONFIG_SND_OMAP_SOC_OMAP3_PANDORA=m CONFIG_SND_SOC_I2C_AND_SPI=m # CONFIG_SND_SOC_ALL_CODECS is not set CONFIG_SND_SOC_TWL4030=m # CONFIG_SND_SIMPLE_CARD is not set # CONFIG_SOUND_PRIME is not set # # HID support # CONFIG_HID=y # CONFIG_HID_BATTERY_STRENGTH is not set # CONFIG_HIDRAW is not set # CONFIG_UHID is not set CONFIG_HID_GENERIC=y # # Special HID drivers # # CONFIG_HID_A4TECH is not set # CONFIG_HID_ACRUX is not set # CONFIG_HID_APPLE is not set # CONFIG_HID_AUREAL is not set # CONFIG_HID_BELKIN is not set # CONFIG_HID_CHERRY is not set # CONFIG_HID_CHICONY is not set # CONFIG_HID_PRODIKEYS is not set # CONFIG_HID_CYPRESS is not set # CONFIG_HID_DRAGONRISE is not set # CONFIG_HID_EMS_FF is not set # CONFIG_HID_ELECOM is not set # CONFIG_HID_EZKEY is not set # CONFIG_HID_HOLTEK is not set # CONFIG_HID_KEYTOUCH is not set # CONFIG_HID_KYE is not set # CONFIG_HID_UCLOGIC is not set # CONFIG_HID_WALTOP is not set # CONFIG_HID_GYRATION is not set # CONFIG_HID_ICADE is not set # CONFIG_HID_TWINHAN is not set # CONFIG_HID_KENSINGTON is not set # CONFIG_HID_LCPOWER is not set # CONFIG_HID_LENOVO_TPKBD is not set # CONFIG_HID_LOGITECH is not set # CONFIG_HID_MAGICMOUSE is not set # CONFIG_HID_MICROSOFT is not set # CONFIG_HID_MONTEREY is not set # CONFIG_HID_MULTITOUCH is not set # CONFIG_HID_NTRIG is not set # CONFIG_HID_ORTEK is not set # CONFIG_HID_PANTHERLORD is not set # CONFIG_HID_PETALYNX is not set # CONFIG_HID_PICOLCD is not set # CONFIG_HID_PRIMAX is not set # CONFIG_HID_PS3REMOTE is not set # CONFIG_HID_ROCCAT is not set # CONFIG_HID_SAITEK is not set # CONFIG_HID_SAMSUNG is not set # CONFIG_HID_SONY is not set # CONFIG_HID_SPEEDLINK is not set # CONFIG_HID_STEELSERIES is not set # CONFIG_HID_SUNPLUS is not set # CONFIG_HID_GREENASIA is not set # CONFIG_HID_SMARTJOYPLUS is not set # CONFIG_HID_TIVO is not set # CONFIG_HID_TOPSEED is not set # CONFIG_HID_THINGM is not set # CONFIG_HID_THRUSTMASTER is not set # CONFIG_HID_WACOM is not set # CONFIG_HID_WIIMOTE is not set # CONFIG_HID_ZEROPLUS is not set # CONFIG_HID_ZYDACRON is not set # CONFIG_HID_SENSOR_HUB is not set # # USB HID support # CONFIG_USB_HID=y # CONFIG_HID_PID is not set # CONFIG_USB_HIDDEV is not set # # I2C HID support # # CONFIG_I2C_HID is not set CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_USB_ARCH_HAS_EHCI=y # CONFIG_USB_ARCH_HAS_XHCI is not set CONFIG_USB_SUPPORT=y CONFIG_USB_COMMON=y CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB=y CONFIG_USB_DEBUG=y CONFIG_USB_ANNOUNCE_NEW_DEVICES=y # # Miscellaneous USB options # CONFIG_USB_DEFAULT_PERSIST=y # CONFIG_USB_DYNAMIC_MINORS is not set # CONFIG_USB_OTG_WHITELIST is not set # CONFIG_USB_OTG_BLACKLIST_HUB is not set CONFIG_USB_MON=y # CONFIG_USB_WUSB_CBAF is not set # # USB Host Controller Drivers # # CONFIG_USB_C67X00_HCD is not set # CONFIG_USB_EHCI_HCD is not set # CONFIG_USB_OXU210HP_HCD is not set # CONFIG_USB_ISP116X_HCD is not set # CONFIG_USB_ISP1760_HCD is not set # CONFIG_USB_ISP1362_HCD is not set # CONFIG_USB_OHCI_HCD is not set # CONFIG_USB_SL811_HCD is not set # CONFIG_USB_R8A66597_HCD is not set CONFIG_USB_MUSB_HDRC=y # CONFIG_USB_MUSB_TUSB6010 is not set CONFIG_USB_MUSB_OMAP2PLUS=y # CONFIG_USB_MUSB_AM35X is not set # CONFIG_USB_MUSB_DSPS is not set # CONFIG_USB_MUSB_UX500 is not set # CONFIG_USB_INVENTRA_DMA is not set CONFIG_MUSB_PIO_ONLY=y # CONFIG_USB_RENESAS_USBHS is not set # # USB Device Class drivers # # CONFIG_USB_ACM is not set # CONFIG_USB_PRINTER is not set CONFIG_USB_WDM=y # CONFIG_USB_TMC is not set # # NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may # # # also be needed; see USB_STORAGE Help for more info # CONFIG_USB_STORAGE=y # CONFIG_USB_STORAGE_DEBUG is not set # CONFIG_USB_STORAGE_REALTEK is not set # CONFIG_USB_STORAGE_DATAFAB is not set # CONFIG_USB_STORAGE_FREECOM is not set # CONFIG_USB_STORAGE_ISD200 is not set # CONFIG_USB_STORAGE_USBAT is not set # CONFIG_USB_STORAGE_SDDR09 is not set # CONFIG_USB_STORAGE_SDDR55 is not set # CONFIG_USB_STORAGE_JUMPSHOT is not set # CONFIG_USB_STORAGE_ALAUDA is not set # CONFIG_USB_STORAGE_ONETOUCH is not set # CONFIG_USB_STORAGE_KARMA is not set # CONFIG_USB_STORAGE_CYPRESS_ATACB is not set # CONFIG_USB_STORAGE_ENE_UB6250 is not set # # USB Imaging devices # # CONFIG_USB_MDC800 is not set # CONFIG_USB_MICROTEK is not set # CONFIG_USB_DWC3 is not set # CONFIG_USB_CHIPIDEA is not set # # USB port drivers # # CONFIG_USB_SERIAL is not set # # USB Miscellaneous drivers # # CONFIG_USB_EMI62 is not set # CONFIG_USB_EMI26 is not set # CONFIG_USB_ADUTUX is not set # CONFIG_USB_SEVSEG is not set # CONFIG_USB_RIO500 is not set # CONFIG_USB_LEGOTOWER is not set # CONFIG_USB_LCD is not set # CONFIG_USB_LED is not set # CONFIG_USB_CYPRESS_CY7C63 is not set # CONFIG_USB_CYTHERM is not set # CONFIG_USB_IDMOUSE is not set # CONFIG_USB_FTDI_ELAN is not set # CONFIG_USB_APPLEDISPLAY is not set # CONFIG_USB_SISUSBVGA is not set # CONFIG_USB_LD is not set # CONFIG_USB_TRANCEVIBRATOR is not set # CONFIG_USB_IOWARRIOR is not set CONFIG_USB_TEST=y # CONFIG_USB_ISIGHTFW is not set # CONFIG_USB_YUREX is not set # CONFIG_USB_EZUSB_FX2 is not set # CONFIG_USB_HSIC_USB3503 is not set CONFIG_USB_PHY=y # CONFIG_NOP_USB_XCEIV is not set CONFIG_OMAP_CONTROL_USB=y CONFIG_OMAP_USB2=y CONFIG_OMAP_USB3=y # CONFIG_SAMSUNG_USBPHY is not set # CONFIG_SAMSUNG_USB2PHY is not set # CONFIG_SAMSUNG_USB3PHY is not set CONFIG_TWL4030_USB=y CONFIG_TWL6030_USB=y # CONFIG_USB_GPIO_VBUS is not set # CONFIG_USB_ISP1301 is not set # CONFIG_USB_RCAR_PHY is not set # CONFIG_USB_ULPI is not set CONFIG_USB_GADGET=y CONFIG_USB_GADGET_DEBUG=y CONFIG_USB_GADGET_DEBUG_FILES=y CONFIG_USB_GADGET_DEBUG_FS=y CONFIG_USB_GADGET_VBUS_DRAW=2 CONFIG_USB_GADGET_STORAGE_NUM_BUFFERS=2 # # USB Peripheral Controller # # CONFIG_USB_FUSB300 is not set # CONFIG_USB_R8A66597 is not set # CONFIG_USB_PXA27X is not set # CONFIG_USB_MV_UDC is not set # CONFIG_USB_MV_U3D is not set CONFIG_USB_GADGET_MUSB_HDRC=y # CONFIG_USB_M66592 is not set # CONFIG_USB_NET2272 is not set # CONFIG_USB_DUMMY_HCD is not set CONFIG_USB_LIBCOMPOSITE=y CONFIG_USB_F_SS_LB=y CONFIG_USB_ZERO=y # CONFIG_USB_AUDIO is not set # CONFIG_USB_ETH is not set # CONFIG_USB_G_NCM is not set # CONFIG_USB_GADGETFS is not set # CONFIG_USB_FUNCTIONFS is not set # CONFIG_USB_MASS_STORAGE is not set # CONFIG_USB_G_SERIAL is not set # CONFIG_USB_MIDI_GADGET is not set # CONFIG_USB_G_PRINTER is not set # CONFIG_USB_CDC_COMPOSITE is not set # CONFIG_USB_G_ACM_MS is not set # CONFIG_USB_G_MULTI is not set # CONFIG_USB_G_HID is not set # CONFIG_USB_G_DBGP is not set CONFIG_MMC=y # CONFIG_MMC_DEBUG is not set CONFIG_MMC_UNSAFE_RESUME=y # CONFIG_MMC_CLKGATE is not set # # MMC/SD/SDIO Card Drivers # CONFIG_MMC_BLOCK=y CONFIG_MMC_BLOCK_MINORS=8 CONFIG_MMC_BLOCK_BOUNCE=y CONFIG_SDIO_UART=y # CONFIG_MMC_TEST is not set # # MMC/SD/SDIO Host Controller Drivers # CONFIG_MMC_ARMMMCI=y # CONFIG_MMC_SDHCI is not set # CONFIG_MMC_SDHCI_PXAV3 is not set # CONFIG_MMC_SDHCI_PXAV2 is not set CONFIG_MMC_OMAP=y CONFIG_MMC_OMAP_HS=y # CONFIG_MMC_DW is not set # CONFIG_MMC_VUB300 is not set # CONFIG_MMC_USHC is not set # CONFIG_MEMSTICK is not set CONFIG_NEW_LEDS=y CONFIG_LEDS_CLASS=y # # LED drivers # # CONFIG_LEDS_LM3530 is not set # CONFIG_LEDS_LM3642 is not set # CONFIG_LEDS_PCA9532 is not set CONFIG_LEDS_GPIO=y # CONFIG_LEDS_LP3944 is not set # CONFIG_LEDS_LP5521 is not set # CONFIG_LEDS_LP5523 is not set # CONFIG_LEDS_LP5562 is not set # CONFIG_LEDS_PCA955X is not set # CONFIG_LEDS_PCA9633 is not set # CONFIG_LEDS_DAC124S085 is not set # CONFIG_LEDS_REGULATOR is not set # CONFIG_LEDS_BD2802 is not set # CONFIG_LEDS_LT3593 is not set # CONFIG_LEDS_RENESAS_TPU is not set # CONFIG_LEDS_TCA6507 is not set # CONFIG_LEDS_LM355x is not set # CONFIG_LEDS_OT200 is not set # CONFIG_LEDS_BLINKM is not set # # LED Triggers # CONFIG_LEDS_TRIGGERS=y CONFIG_LEDS_TRIGGER_TIMER=y CONFIG_LEDS_TRIGGER_ONESHOT=y CONFIG_LEDS_TRIGGER_HEARTBEAT=y CONFIG_LEDS_TRIGGER_BACKLIGHT=y CONFIG_LEDS_TRIGGER_CPU=y CONFIG_LEDS_TRIGGER_GPIO=y CONFIG_LEDS_TRIGGER_DEFAULT_ON=y # # iptables trigger is under Netfilter config (LED target) # # CONFIG_LEDS_TRIGGER_TRANSIENT is not set # CONFIG_LEDS_TRIGGER_CAMERA is not set # CONFIG_ACCESSIBILITY is not set # CONFIG_EDAC is not set CONFIG_RTC_LIB=y CONFIG_RTC_CLASS=y CONFIG_RTC_HCTOSYS=y CONFIG_RTC_SYSTOHC=y CONFIG_RTC_HCTOSYS_DEVICE="rtc0" # CONFIG_RTC_DEBUG is not set # # RTC interfaces # CONFIG_RTC_INTF_SYSFS=y CONFIG_RTC_INTF_PROC=y CONFIG_RTC_INTF_DEV=y # CONFIG_RTC_INTF_DEV_UIE_EMUL is not set # CONFIG_RTC_DRV_TEST is not set # # I2C RTC drivers # # CONFIG_RTC_DRV_DS1307 is not set # CONFIG_RTC_DRV_DS1374 is not set # CONFIG_RTC_DRV_DS1672 is not set # CONFIG_RTC_DRV_DS3232 is not set # CONFIG_RTC_DRV_MAX6900 is not set # CONFIG_RTC_DRV_RS5C372 is not set # CONFIG_RTC_DRV_ISL1208 is not set # CONFIG_RTC_DRV_ISL12022 is not set # CONFIG_RTC_DRV_X1205 is not set # CONFIG_RTC_DRV_PCF8523 is not set # CONFIG_RTC_DRV_PCF8563 is not set # CONFIG_RTC_DRV_PCF8583 is not set # CONFIG_RTC_DRV_M41T80 is not set # CONFIG_RTC_DRV_BQ32K is not set CONFIG_RTC_DRV_TWL92330=y CONFIG_RTC_DRV_TWL4030=y # CONFIG_RTC_DRV_TPS65910 is not set # CONFIG_RTC_DRV_S35390A is not set # CONFIG_RTC_DRV_FM3130 is not set # CONFIG_RTC_DRV_RX8581 is not set # CONFIG_RTC_DRV_RX8025 is not set # CONFIG_RTC_DRV_EM3027 is not set # CONFIG_RTC_DRV_RV3029C2 is not set # # SPI RTC drivers # # CONFIG_RTC_DRV_M41T93 is not set # CONFIG_RTC_DRV_M41T94 is not set # CONFIG_RTC_DRV_DS1305 is not set # CONFIG_RTC_DRV_DS1390 is not set # CONFIG_RTC_DRV_MAX6902 is not set # CONFIG_RTC_DRV_R9701 is not set # CONFIG_RTC_DRV_RS5C348 is not set # CONFIG_RTC_DRV_DS3234 is not set # CONFIG_RTC_DRV_PCF2123 is not set # CONFIG_RTC_DRV_RX4581 is not set # # Platform RTC drivers # # CONFIG_RTC_DRV_CMOS is not set # CONFIG_RTC_DRV_DS1286 is not set # CONFIG_RTC_DRV_DS1511 is not set # CONFIG_RTC_DRV_DS1553 is not set # CONFIG_RTC_DRV_DS1742 is not set # CONFIG_RTC_DRV_STK17TA8 is not set # CONFIG_RTC_DRV_M48T86 is not set # CONFIG_RTC_DRV_M48T35 is not set # CONFIG_RTC_DRV_M48T59 is not set # CONFIG_RTC_DRV_MSM6242 is not set # CONFIG_RTC_DRV_BQ4802 is not set # CONFIG_RTC_DRV_RP5C01 is not set # CONFIG_RTC_DRV_V3020 is not set # CONFIG_RTC_DRV_DS2404 is not set # # on-CPU RTC drivers # CONFIG_RTC_DRV_OMAP=y # CONFIG_RTC_DRV_PL030 is not set # CONFIG_RTC_DRV_PL031 is not set # CONFIG_RTC_DRV_SNVS is not set # # HID Sensor RTC drivers # # CONFIG_RTC_DRV_HID_SENSOR_TIME is not set CONFIG_DMADEVICES=y # CONFIG_DMADEVICES_DEBUG is not set # # DMA Devices # # CONFIG_AMBA_PL08X is not set # CONFIG_DW_DMAC is not set # CONFIG_TIMB_DMA is not set # CONFIG_PL330_DMA is not set CONFIG_DMA_OMAP=y CONFIG_DMA_ENGINE=y CONFIG_DMA_VIRTUAL_CHANNELS=y CONFIG_DMA_OF=y # # DMA Clients # # CONFIG_NET_DMA is not set # CONFIG_ASYNC_TX_DMA is not set # CONFIG_DMATEST is not set # CONFIG_AUXDISPLAY is not set # CONFIG_UIO is not set # CONFIG_VIRT_DRIVERS is not set # # Virtio drivers # # CONFIG_VIRTIO_MMIO is not set # # Microsoft Hyper-V guest support # # CONFIG_STAGING is not set CONFIG_CLKDEV_LOOKUP=y CONFIG_HAVE_CLK_PREPARE=y CONFIG_COMMON_CLK=y # # Common Clock Framework # # CONFIG_COMMON_CLK_DEBUG is not set CONFIG_COMMON_CLK_VERSATILE=y # CONFIG_COMMON_CLK_SI5351 is not set # # Hardware Spinlock drivers # # CONFIG_HWSPINLOCK_OMAP is not set CONFIG_CLKSRC_OF=y CONFIG_CLKSRC_MMIO=y CONFIG_ARM_ARCH_TIMER=y # CONFIG_MAILBOX is not set CONFIG_IOMMU_SUPPORT=y CONFIG_OF_IOMMU=y # CONFIG_OMAP_IOMMU is not set # # Remoteproc drivers # # CONFIG_STE_MODEM_RPROC is not set # # Rpmsg drivers # # CONFIG_PM_DEVFREQ is not set # CONFIG_EXTCON is not set # CONFIG_MEMORY is not set # CONFIG_IIO is not set # CONFIG_PWM is not set CONFIG_IRQCHIP=y CONFIG_ARM_GIC=y # CONFIG_IPACK_BUS is not set # CONFIG_RESET_CONTROLLER is not set # # File systems # CONFIG_DCACHE_WORD_ACCESS=y CONFIG_EXT2_FS=y # CONFIG_EXT2_FS_XATTR is not set # CONFIG_EXT2_FS_XIP is not set CONFIG_EXT3_FS=y CONFIG_EXT3_DEFAULTS_TO_ORDERED=y # CONFIG_EXT3_FS_XATTR is not set CONFIG_EXT4_FS=y # CONFIG_EXT4_FS_POSIX_ACL is not set # CONFIG_EXT4_FS_SECURITY is not set # CONFIG_EXT4_DEBUG is not set CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_JBD2=y # CONFIG_JBD2_DEBUG is not set CONFIG_FS_MBCACHE=y # CONFIG_REISERFS_FS is not set # CONFIG_JFS_FS is not set # CONFIG_XFS_FS is not set # CONFIG_GFS2_FS is not set # CONFIG_OCFS2_FS is not set # CONFIG_BTRFS_FS is not set # CONFIG_NILFS2_FS is not set CONFIG_FS_POSIX_ACL=y CONFIG_FILE_LOCKING=y CONFIG_FSNOTIFY=y CONFIG_DNOTIFY=y CONFIG_INOTIFY_USER=y # CONFIG_FANOTIFY is not set CONFIG_QUOTA=y # CONFIG_QUOTA_NETLINK_INTERFACE is not set CONFIG_PRINT_QUOTA_WARNING=y # CONFIG_QUOTA_DEBUG is not set CONFIG_QUOTA_TREE=y # CONFIG_QFMT_V1 is not set CONFIG_QFMT_V2=y CONFIG_QUOTACTL=y # CONFIG_AUTOFS4_FS is not set # CONFIG_FUSE_FS is not set # # Caches # # CONFIG_FSCACHE is not set # # CD-ROM/DVD Filesystems # # CONFIG_ISO9660_FS is not set # CONFIG_UDF_FS is not set # # DOS/FAT/NT Filesystems # CONFIG_FAT_FS=y CONFIG_MSDOS_FS=y CONFIG_VFAT_FS=y CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1" # CONFIG_NTFS_FS is not set # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_SYSCTL=y CONFIG_PROC_PAGE_MONITOR=y CONFIG_SYSFS=y CONFIG_TMPFS=y # CONFIG_TMPFS_POSIX_ACL is not set # CONFIG_TMPFS_XATTR is not set # CONFIG_HUGETLB_PAGE is not set CONFIG_CONFIGFS_FS=y CONFIG_MISC_FILESYSTEMS=y # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set # CONFIG_ECRYPT_FS is not set # CONFIG_HFS_FS is not set # CONFIG_HFSPLUS_FS is not set # CONFIG_BEFS_FS is not set # CONFIG_BFS_FS is not set # CONFIG_EFS_FS is not set CONFIG_JFFS2_FS=y CONFIG_JFFS2_FS_DEBUG=0 CONFIG_JFFS2_FS_WRITEBUFFER=y # CONFIG_JFFS2_FS_WBUF_VERIFY is not set CONFIG_JFFS2_SUMMARY=y CONFIG_JFFS2_FS_XATTR=y CONFIG_JFFS2_FS_POSIX_ACL=y CONFIG_JFFS2_FS_SECURITY=y CONFIG_JFFS2_COMPRESSION_OPTIONS=y CONFIG_JFFS2_ZLIB=y CONFIG_JFFS2_LZO=y CONFIG_JFFS2_RTIME=y CONFIG_JFFS2_RUBIN=y # CONFIG_JFFS2_CMODE_NONE is not set CONFIG_JFFS2_CMODE_PRIORITY=y # CONFIG_JFFS2_CMODE_SIZE is not set # CONFIG_JFFS2_CMODE_FAVOURLZO is not set CONFIG_UBIFS_FS=y # CONFIG_UBIFS_FS_ADVANCED_COMPR is not set CONFIG_UBIFS_FS_LZO=y CONFIG_UBIFS_FS_ZLIB=y # CONFIG_LOGFS is not set CONFIG_CRAMFS=y # CONFIG_SQUASHFS is not set # CONFIG_VXFS_FS is not set # CONFIG_MINIX_FS is not set # CONFIG_OMFS_FS is not set # CONFIG_HPFS_FS is not set # CONFIG_QNX4FS_FS is not set # CONFIG_QNX6FS_FS is not set # CONFIG_ROMFS_FS is not set # CONFIG_PSTORE is not set # CONFIG_SYSV_FS is not set # CONFIG_UFS_FS is not set # CONFIG_F2FS_FS is not set CONFIG_NETWORK_FILESYSTEMS=y CONFIG_NFS_FS=y CONFIG_NFS_V2=y CONFIG_NFS_V3=y CONFIG_NFS_V3_ACL=y CONFIG_NFS_V4=y # CONFIG_NFS_SWAP is not set # CONFIG_NFS_V4_1 is not set CONFIG_ROOT_NFS=y # CONFIG_NFS_USE_LEGACY_DNS is not set CONFIG_NFS_USE_KERNEL_DNS=y # CONFIG_NFSD is not set CONFIG_LOCKD=y CONFIG_LOCKD_V4=y CONFIG_NFS_ACL_SUPPORT=y CONFIG_NFS_COMMON=y CONFIG_SUNRPC=y CONFIG_SUNRPC_GSS=y # CONFIG_SUNRPC_DEBUG is not set # CONFIG_CEPH_FS is not set # CONFIG_CIFS is not set # CONFIG_NCP_FS is not set # CONFIG_CODA_FS is not set # CONFIG_AFS_FS is not set CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" CONFIG_NLS_CODEPAGE_437=y # CONFIG_NLS_CODEPAGE_737 is not set # CONFIG_NLS_CODEPAGE_775 is not set # CONFIG_NLS_CODEPAGE_850 is not set # CONFIG_NLS_CODEPAGE_852 is not set # CONFIG_NLS_CODEPAGE_855 is not set # CONFIG_NLS_CODEPAGE_857 is not set # CONFIG_NLS_CODEPAGE_860 is not set # CONFIG_NLS_CODEPAGE_861 is not set # CONFIG_NLS_CODEPAGE_862 is not set # CONFIG_NLS_CODEPAGE_863 is not set # CONFIG_NLS_CODEPAGE_864 is not set # CONFIG_NLS_CODEPAGE_865 is not set # CONFIG_NLS_CODEPAGE_866 is not set # CONFIG_NLS_CODEPAGE_869 is not set # CONFIG_NLS_CODEPAGE_936 is not set # CONFIG_NLS_CODEPAGE_950 is not set # CONFIG_NLS_CODEPAGE_932 is not set # CONFIG_NLS_CODEPAGE_949 is not set # CONFIG_NLS_CODEPAGE_874 is not set # CONFIG_NLS_ISO8859_8 is not set # CONFIG_NLS_CODEPAGE_1250 is not set # CONFIG_NLS_CODEPAGE_1251 is not set # CONFIG_NLS_ASCII is not set CONFIG_NLS_ISO8859_1=y # CONFIG_NLS_ISO8859_2 is not set # CONFIG_NLS_ISO8859_3 is not set # CONFIG_NLS_ISO8859_4 is not set # CONFIG_NLS_ISO8859_5 is not set # CONFIG_NLS_ISO8859_6 is not set # CONFIG_NLS_ISO8859_7 is not set # CONFIG_NLS_ISO8859_9 is not set # CONFIG_NLS_ISO8859_13 is not set # CONFIG_NLS_ISO8859_14 is not set # CONFIG_NLS_ISO8859_15 is not set # CONFIG_NLS_KOI8_R is not set # CONFIG_NLS_KOI8_U is not set # CONFIG_NLS_MAC_ROMAN is not set # CONFIG_NLS_MAC_CELTIC is not set # CONFIG_NLS_MAC_CENTEURO is not set # CONFIG_NLS_MAC_CROATIAN is not set # CONFIG_NLS_MAC_CYRILLIC is not set # CONFIG_NLS_MAC_GAELIC is not set # CONFIG_NLS_MAC_GREEK is not set # CONFIG_NLS_MAC_ICELAND is not set # CONFIG_NLS_MAC_INUIT is not set # CONFIG_NLS_MAC_ROMANIAN is not set # CONFIG_NLS_MAC_TURKISH is not set # CONFIG_NLS_UTF8 is not set # CONFIG_DLM is not set # # Kernel hacking # CONFIG_PRINTK_TIME=y CONFIG_DEFAULT_MESSAGE_LOGLEVEL=4 CONFIG_ENABLE_WARN_DEPRECATED=y CONFIG_ENABLE_MUST_CHECK=y CONFIG_FRAME_WARN=1024 CONFIG_MAGIC_SYSRQ=y # CONFIG_STRIP_ASM_SYMS is not set # CONFIG_READABLE_ASM is not set # CONFIG_UNUSED_SYMBOLS is not set CONFIG_DEBUG_FS=y # CONFIG_HEADERS_CHECK is not set # CONFIG_DEBUG_SECTION_MISMATCH is not set CONFIG_DEBUG_KERNEL=y # CONFIG_DEBUG_SHIRQ is not set # CONFIG_LOCKUP_DETECTOR is not set # CONFIG_PANIC_ON_OOPS is not set CONFIG_PANIC_ON_OOPS_VALUE=0 # CONFIG_DETECT_HUNG_TASK is not set CONFIG_SCHED_DEBUG=y CONFIG_SCHEDSTATS=y CONFIG_TIMER_STATS=y # CONFIG_DEBUG_OBJECTS is not set # CONFIG_DEBUG_SLAB is not set CONFIG_HAVE_DEBUG_KMEMLEAK=y # CONFIG_DEBUG_KMEMLEAK is not set # CONFIG_DEBUG_RT_MUTEXES is not set # CONFIG_RT_MUTEX_TESTER is not set CONFIG_DEBUG_SPINLOCK=y CONFIG_DEBUG_MUTEXES=y CONFIG_DEBUG_LOCK_ALLOC=y CONFIG_PROVE_LOCKING=y CONFIG_LOCKDEP=y # CONFIG_LOCK_STAT is not set # CONFIG_DEBUG_LOCKDEP is not set CONFIG_TRACE_IRQFLAGS=y # CONFIG_DEBUG_ATOMIC_SLEEP is not set # CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set CONFIG_STACKTRACE=y # CONFIG_DEBUG_STACK_USAGE is not set # CONFIG_DEBUG_KOBJECT is not set # CONFIG_DEBUG_HIGHMEM is not set # CONFIG_DEBUG_BUGVERBOSE is not set CONFIG_DEBUG_INFO=y # CONFIG_DEBUG_INFO_REDUCED is not set # CONFIG_DEBUG_VM is not set # CONFIG_DEBUG_WRITECOUNT is not set # CONFIG_DEBUG_MEMORY_INIT is not set # CONFIG_DEBUG_LIST is not set # CONFIG_TEST_LIST_SORT is not set # CONFIG_DEBUG_SG is not set # CONFIG_DEBUG_NOTIFIERS is not set # CONFIG_DEBUG_CREDENTIALS is not set # CONFIG_BOOT_PRINTK_DELAY is not set # # RCU Debugging # # CONFIG_PROVE_RCU is not set # CONFIG_SPARSE_RCU_POINTER is not set # CONFIG_RCU_TORTURE_TEST is not set CONFIG_RCU_CPU_STALL_TIMEOUT=21 # CONFIG_RCU_CPU_STALL_INFO is not set # CONFIG_RCU_TRACE is not set # CONFIG_KPROBES_SANITY_TEST is not set # CONFIG_BACKTRACE_SELF_TEST is not set # CONFIG_DEBUG_BLOCK_EXT_DEVT is not set # CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set # CONFIG_DEBUG_PER_CPU_MAPS is not set # CONFIG_LKDTM is not set # CONFIG_NOTIFIER_ERROR_INJECTION is not set # CONFIG_FAULT_INJECTION is not set # CONFIG_DEBUG_PAGEALLOC is not set CONFIG_NOP_TRACER=y CONFIG_HAVE_FUNCTION_TRACER=y CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y CONFIG_HAVE_DYNAMIC_FTRACE=y CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y CONFIG_HAVE_SYSCALL_TRACEPOINTS=y CONFIG_HAVE_C_RECORDMCOUNT=y CONFIG_TRACE_CLOCK=y CONFIG_RING_BUFFER=y CONFIG_EVENT_TRACING=y CONFIG_CONTEXT_SWITCH_TRACER=y CONFIG_RING_BUFFER_ALLOW_SWAP=y CONFIG_TRACING=y CONFIG_TRACING_SUPPORT=y CONFIG_FTRACE=y # CONFIG_FUNCTION_TRACER is not set # CONFIG_IRQSOFF_TRACER is not set # CONFIG_SCHED_TRACER is not set # CONFIG_ENABLE_DEFAULT_TRACERS is not set # CONFIG_FTRACE_SYSCALLS is not set # CONFIG_TRACER_SNAPSHOT is not set CONFIG_BRANCH_PROFILE_NONE=y # CONFIG_PROFILE_ANNOTATED_BRANCHES is not set # CONFIG_PROFILE_ALL_BRANCHES is not set # CONFIG_STACK_TRACER is not set # CONFIG_BLK_DEV_IO_TRACE is not set CONFIG_KPROBE_EVENT=y CONFIG_PROBE_EVENTS=y # CONFIG_RING_BUFFER_BENCHMARK is not set # CONFIG_RING_BUFFER_STARTUP_TEST is not set # CONFIG_RBTREE_TEST is not set # CONFIG_INTERVAL_TREE_TEST is not set # CONFIG_DYNAMIC_DEBUG is not set # CONFIG_DMA_API_DEBUG is not set # CONFIG_ATOMIC64_SELFTEST is not set # CONFIG_SAMPLES is not set CONFIG_HAVE_ARCH_KGDB=y # CONFIG_KGDB is not set # CONFIG_TEST_STRING_HELPERS is not set # CONFIG_TEST_KSTRTOX is not set # CONFIG_STRICT_DEVMEM is not set CONFIG_ARM_UNWIND=y # CONFIG_DEBUG_USER is not set # CONFIG_DEBUG_LL is not set CONFIG_DEBUG_LL_INCLUDE="mach/debug-macro.S" CONFIG_UNCOMPRESS_INCLUDE="debug/uncompress.h" # CONFIG_OC_ETM is not set # CONFIG_ARM_KPROBES_TEST is not set # CONFIG_PID_IN_CONTEXTIDR is not set # # Security options # CONFIG_KEYS=y # CONFIG_ENCRYPTED_KEYS is not set # CONFIG_KEYS_DEBUG_PROC_KEYS is not set # CONFIG_SECURITY_DMESG_RESTRICT is not set CONFIG_SECURITY=y # CONFIG_SECURITYFS is not set # CONFIG_SECURITY_NETWORK is not set # CONFIG_SECURITY_PATH is not set # CONFIG_SECURITY_SMACK is not set # CONFIG_SECURITY_TOMOYO is not set # CONFIG_SECURITY_APPARMOR is not set # CONFIG_SECURITY_YAMA is not set # CONFIG_IMA is not set # CONFIG_EVM is not set CONFIG_DEFAULT_SECURITY_DAC=y CONFIG_DEFAULT_SECURITY="" CONFIG_CRYPTO=y # # Crypto core or helper # CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_ALGAPI2=y CONFIG_CRYPTO_AEAD2=y CONFIG_CRYPTO_BLKCIPHER=m CONFIG_CRYPTO_BLKCIPHER2=y CONFIG_CRYPTO_HASH=y CONFIG_CRYPTO_HASH2=y CONFIG_CRYPTO_RNG2=y CONFIG_CRYPTO_PCOMP2=y CONFIG_CRYPTO_MANAGER=m CONFIG_CRYPTO_MANAGER2=y # CONFIG_CRYPTO_USER is not set CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y # CONFIG_CRYPTO_GF128MUL is not set # CONFIG_CRYPTO_NULL is not set # CONFIG_CRYPTO_PCRYPT is not set CONFIG_CRYPTO_WORKQUEUE=y # CONFIG_CRYPTO_CRYPTD is not set # CONFIG_CRYPTO_AUTHENC is not set # CONFIG_CRYPTO_TEST is not set # # Authenticated Encryption with Associated Data # # CONFIG_CRYPTO_CCM is not set # CONFIG_CRYPTO_GCM is not set # CONFIG_CRYPTO_SEQIV is not set # # Block modes # # CONFIG_CRYPTO_CBC is not set # CONFIG_CRYPTO_CTR is not set # CONFIG_CRYPTO_CTS is not set CONFIG_CRYPTO_ECB=m # CONFIG_CRYPTO_LRW is not set # CONFIG_CRYPTO_PCBC is not set # CONFIG_CRYPTO_XTS is not set # # Hash modes # # CONFIG_CRYPTO_CMAC is not set # CONFIG_CRYPTO_HMAC is not set # CONFIG_CRYPTO_XCBC is not set # CONFIG_CRYPTO_VMAC is not set # # Digest # CONFIG_CRYPTO_CRC32C=y # CONFIG_CRYPTO_CRC32 is not set # CONFIG_CRYPTO_GHASH is not set # CONFIG_CRYPTO_MD4 is not set # CONFIG_CRYPTO_MD5 is not set CONFIG_CRYPTO_MICHAEL_MIC=y # CONFIG_CRYPTO_RMD128 is not set # CONFIG_CRYPTO_RMD160 is not set # CONFIG_CRYPTO_RMD256 is not set # CONFIG_CRYPTO_RMD320 is not set # CONFIG_CRYPTO_SHA1 is not set # CONFIG_CRYPTO_SHA1_ARM is not set CONFIG_CRYPTO_SHA256=m # CONFIG_CRYPTO_SHA512 is not set # CONFIG_CRYPTO_TGR192 is not set # CONFIG_CRYPTO_WP512 is not set # # Ciphers # CONFIG_CRYPTO_AES=y # CONFIG_CRYPTO_AES_ARM is not set # CONFIG_CRYPTO_ANUBIS is not set CONFIG_CRYPTO_ARC4=m # CONFIG_CRYPTO_BLOWFISH is not set # CONFIG_CRYPTO_CAMELLIA is not set # CONFIG_CRYPTO_CAST5 is not set # CONFIG_CRYPTO_CAST6 is not set # CONFIG_CRYPTO_DES is not set # CONFIG_CRYPTO_FCRYPT is not set # CONFIG_CRYPTO_KHAZAD is not set # CONFIG_CRYPTO_SALSA20 is not set # CONFIG_CRYPTO_SEED is not set # CONFIG_CRYPTO_SERPENT is not set # CONFIG_CRYPTO_TEA is not set # CONFIG_CRYPTO_TWOFISH is not set # # Compression # CONFIG_CRYPTO_DEFLATE=y # CONFIG_CRYPTO_ZLIB is not set CONFIG_CRYPTO_LZO=y # CONFIG_CRYPTO_LZ4 is not set # CONFIG_CRYPTO_LZ4HC is not set # # Random Number Generation # # CONFIG_CRYPTO_ANSI_CPRNG is not set # CONFIG_CRYPTO_USER_API_HASH is not set # CONFIG_CRYPTO_USER_API_SKCIPHER is not set CONFIG_CRYPTO_HW=y # CONFIG_CRYPTO_DEV_OMAP_SHAM is not set # CONFIG_CRYPTO_DEV_OMAP_AES is not set # CONFIG_ASYMMETRIC_KEY_TYPE is not set CONFIG_BINARY_PRINTF=y # # Library routines # CONFIG_BITREVERSE=y CONFIG_GENERIC_STRNCPY_FROM_USER=y CONFIG_GENERIC_STRNLEN_USER=y CONFIG_GENERIC_PCI_IOMAP=y CONFIG_GENERIC_IO=y CONFIG_CRC_CCITT=y CONFIG_CRC16=y CONFIG_CRC_T10DIF=y CONFIG_CRC_ITU_T=y CONFIG_CRC32=y # CONFIG_CRC32_SELFTEST is not set CONFIG_CRC32_SLICEBY8=y # CONFIG_CRC32_SLICEBY4 is not set # CONFIG_CRC32_SARWATE is not set # CONFIG_CRC32_BIT is not set CONFIG_CRC7=y CONFIG_LIBCRC32C=y # CONFIG_CRC8 is not set CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=y CONFIG_LZO_COMPRESS=y CONFIG_LZO_DECOMPRESS=y # CONFIG_XZ_DEC is not set # CONFIG_XZ_DEC_BCJ is not set CONFIG_DECOMPRESS_GZIP=y CONFIG_HAS_IOMEM=y CONFIG_HAS_DMA=y CONFIG_CPU_RMAP=y CONFIG_DQL=y CONFIG_NLATTR=y CONFIG_GENERIC_ATOMIC64=y CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE=y CONFIG_AVERAGE=y # CONFIG_CORDIC is not set # CONFIG_DDR is not set CONFIG_OID_REGISTRY=y # CONFIG_VIRTUALIZATION is not set ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-24 5:41 ` Kishon Vijay Abraham I @ 2013-04-24 19:08 ` Tony Lindgren 2013-04-24 19:23 ` Tony Lindgren 0 siblings, 1 reply; 27+ messages in thread From: Tony Lindgren @ 2013-04-24 19:08 UTC (permalink / raw) To: linux-arm-kernel * Kishon Vijay Abraham I <kishon@ti.com> [130423 22:46]: > Hi Tony, > > On Wednesday 24 April 2013 04:46 AM, Tony Lindgren wrote: > >* Tony Lindgren <tony@atomide.com> [130423 14:37]: > >>* Tony Lindgren <tony@atomide.com> [130423 10:28]: > >>>* Kishon Vijay Abraham I <kishon@ti.com> [130423 08:15]: > >>>>>>>2. MUSB fails with legacy booting and DT on panda es > >>>>>>> > >>>>>>>With both legacy and DT booting I get something like: > >>>>>>> > >>>>>>>HS USB OTG: no transceiver configured > >>>>>>>musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517 > >>>>>> > >>>>>>The dt should work fine with https://patchwork.kernel.org/patch/2423061/. > >>>>> > >>>>>OK thanks for checking that. > > > >Kishon, I think there's also some other issue remaining > >in linux next with MUSB and DT. I'm still getting the > >"HS USB OTG: no transceiver configured" although the nop > >xceiv is compiled in. Maybe give it a try against linux > >next? > > For OMAP4 MUSB, you'll need omap-usb2 phy. I've attached my .config. Thanks your config helped me to track it down. Looks like I got the PHYs the wrong way around between EHCI and MUSB.. In any case, I did have omap-usb2 compiled in, but I did not have OMAP_OCP2SCP=y set. Should OMAP_USB2 depend on that? Also, looks like MUSB just sits in b_idle mode though, so no more ID pin interrupt for some reason. Regards, Tony ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-24 19:08 ` Tony Lindgren @ 2013-04-24 19:23 ` Tony Lindgren 2013-04-25 9:04 ` Felipe Balbi 0 siblings, 1 reply; 27+ messages in thread From: Tony Lindgren @ 2013-04-24 19:23 UTC (permalink / raw) To: linux-arm-kernel * Tony Lindgren <tony@atomide.com> [130424 12:13]: > * Kishon Vijay Abraham I <kishon@ti.com> [130423 22:46]: > > Hi Tony, > > > > On Wednesday 24 April 2013 04:46 AM, Tony Lindgren wrote: > > >* Tony Lindgren <tony@atomide.com> [130423 14:37]: > > >>* Tony Lindgren <tony@atomide.com> [130423 10:28]: > > >>>* Kishon Vijay Abraham I <kishon@ti.com> [130423 08:15]: > > >>>>>>>2. MUSB fails with legacy booting and DT on panda es > > >>>>>>> > > >>>>>>>With both legacy and DT booting I get something like: > > >>>>>>> > > >>>>>>>HS USB OTG: no transceiver configured > > >>>>>>>musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517 > > >>>>>> > > >>>>>>The dt should work fine with https://patchwork.kernel.org/patch/2423061/. > > >>>>> > > >>>>>OK thanks for checking that. > > > > > >Kishon, I think there's also some other issue remaining > > >in linux next with MUSB and DT. I'm still getting the > > >"HS USB OTG: no transceiver configured" although the nop > > >xceiv is compiled in. Maybe give it a try against linux > > >next? > > > > For OMAP4 MUSB, you'll need omap-usb2 phy. I've attached my .config. > > Thanks your config helped me to track it down. Looks like I got > the PHYs the wrong way around between EHCI and MUSB.. > > In any case, I did have omap-usb2 compiled in, but I did not have > OMAP_OCP2SCP=y set. Should OMAP_USB2 depend on that? > > Also, looks like MUSB just sits in b_idle mode though, so no more > ID pin interrupt for some reason. OK looks like I got the ID interrupt going by enabling CONFIG_TWL6030_USB=y. Still stays in a_idle with no keyboard after plugging it in, but now changes between a and b mode. Regards, Tony ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-24 19:23 ` Tony Lindgren @ 2013-04-25 9:04 ` Felipe Balbi 2013-04-25 15:01 ` Tony Lindgren 0 siblings, 1 reply; 27+ messages in thread From: Felipe Balbi @ 2013-04-25 9:04 UTC (permalink / raw) To: linux-arm-kernel Hi, On Wed, Apr 24, 2013 at 12:23:30PM -0700, Tony Lindgren wrote: > * Tony Lindgren <tony@atomide.com> [130424 12:13]: > > * Kishon Vijay Abraham I <kishon@ti.com> [130423 22:46]: > > > Hi Tony, > > > > > > On Wednesday 24 April 2013 04:46 AM, Tony Lindgren wrote: > > > >* Tony Lindgren <tony@atomide.com> [130423 14:37]: > > > >>* Tony Lindgren <tony@atomide.com> [130423 10:28]: > > > >>>* Kishon Vijay Abraham I <kishon@ti.com> [130423 08:15]: > > > >>>>>>>2. MUSB fails with legacy booting and DT on panda es > > > >>>>>>> > > > >>>>>>>With both legacy and DT booting I get something like: > > > >>>>>>> > > > >>>>>>>HS USB OTG: no transceiver configured > > > >>>>>>>musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517 > > > >>>>>> > > > >>>>>>The dt should work fine with https://patchwork.kernel.org/patch/2423061/. > > > >>>>> > > > >>>>>OK thanks for checking that. > > > > > > > >Kishon, I think there's also some other issue remaining > > > >in linux next with MUSB and DT. I'm still getting the > > > >"HS USB OTG: no transceiver configured" although the nop > > > >xceiv is compiled in. Maybe give it a try against linux > > > >next? > > > > > > For OMAP4 MUSB, you'll need omap-usb2 phy. I've attached my .config. > > > > Thanks your config helped me to track it down. Looks like I got > > the PHYs the wrong way around between EHCI and MUSB.. > > > > In any case, I did have omap-usb2 compiled in, but I did not have > > OMAP_OCP2SCP=y set. Should OMAP_USB2 depend on that? > > > > Also, looks like MUSB just sits in b_idle mode though, so no more > > ID pin interrupt for some reason. > > OK looks like I got the ID interrupt going by enabling > CONFIG_TWL6030_USB=y. Still stays in a_idle with no keyboard > after plugging it in, but now changes between a and b mode. come again, you ground ID pin and have no devices attached ? Then it should stay in a_idle. -- balbi -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130425/c2074be5/attachment-0001.sig> ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-25 9:04 ` Felipe Balbi @ 2013-04-25 15:01 ` Tony Lindgren 2013-04-25 15:13 ` Felipe Balbi 0 siblings, 1 reply; 27+ messages in thread From: Tony Lindgren @ 2013-04-25 15:01 UTC (permalink / raw) To: linux-arm-kernel * Felipe Balbi <balbi@ti.com> [130425 02:10]: > On Wed, Apr 24, 2013 at 12:23:30PM -0700, Tony Lindgren wrote: > > * Tony Lindgren <tony@atomide.com> [130424 12:13]: > > > * Kishon Vijay Abraham I <kishon@ti.com> [130423 22:46]: > > > > Hi Tony, > > > > > > > > On Wednesday 24 April 2013 04:46 AM, Tony Lindgren wrote: > > > > >* Tony Lindgren <tony@atomide.com> [130423 14:37]: > > > > >>* Tony Lindgren <tony@atomide.com> [130423 10:28]: > > > > >>>* Kishon Vijay Abraham I <kishon@ti.com> [130423 08:15]: > > > > >>>>>>>2. MUSB fails with legacy booting and DT on panda es > > > > >>>>>>> > > > > >>>>>>>With both legacy and DT booting I get something like: > > > > >>>>>>> > > > > >>>>>>>HS USB OTG: no transceiver configured > > > > >>>>>>>musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517 > > > > >>>>>> > > > > >>>>>>The dt should work fine with https://patchwork.kernel.org/patch/2423061/. > > > > >>>>> > > > > >>>>>OK thanks for checking that. > > > > > > > > > >Kishon, I think there's also some other issue remaining > > > > >in linux next with MUSB and DT. I'm still getting the > > > > >"HS USB OTG: no transceiver configured" although the nop > > > > >xceiv is compiled in. Maybe give it a try against linux > > > > >next? > > > > > > > > For OMAP4 MUSB, you'll need omap-usb2 phy. I've attached my .config. > > > > > > Thanks your config helped me to track it down. Looks like I got > > > the PHYs the wrong way around between EHCI and MUSB.. > > > > > > In any case, I did have omap-usb2 compiled in, but I did not have > > > OMAP_OCP2SCP=y set. Should OMAP_USB2 depend on that? > > > > > > Also, looks like MUSB just sits in b_idle mode though, so no more > > > ID pin interrupt for some reason. > > > > OK looks like I got the ID interrupt going by enabling > > CONFIG_TWL6030_USB=y. Still stays in a_idle with no keyboard > > after plugging it in, but now changes between a and b mode. > > come again, you ground ID pin and have no devices attached ? Then it > should stay in a_idle. After playing with looks like it detects the keyboard after replugging the cable a few times. So it's not detecting the keyboard every time when plugged in, but sounds like that's not related to the DT patches. It's probably the session bit related issues again.. Regards, Tony ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-25 15:01 ` Tony Lindgren @ 2013-04-25 15:13 ` Felipe Balbi 0 siblings, 0 replies; 27+ messages in thread From: Felipe Balbi @ 2013-04-25 15:13 UTC (permalink / raw) To: linux-arm-kernel HI, On Thu, Apr 25, 2013 at 08:01:20AM -0700, Tony Lindgren wrote: > > > > > >>>>>>>2. MUSB fails with legacy booting and DT on panda es > > > > > >>>>>>> > > > > > >>>>>>>With both legacy and DT booting I get something like: > > > > > >>>>>>> > > > > > >>>>>>>HS USB OTG: no transceiver configured > > > > > >>>>>>>musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517 > > > > > >>>>>> > > > > > >>>>>>The dt should work fine with https://patchwork.kernel.org/patch/2423061/. > > > > > >>>>> > > > > > >>>>>OK thanks for checking that. > > > > > > > > > > > >Kishon, I think there's also some other issue remaining > > > > > >in linux next with MUSB and DT. I'm still getting the > > > > > >"HS USB OTG: no transceiver configured" although the nop > > > > > >xceiv is compiled in. Maybe give it a try against linux > > > > > >next? > > > > > > > > > > For OMAP4 MUSB, you'll need omap-usb2 phy. I've attached my .config. > > > > > > > > Thanks your config helped me to track it down. Looks like I got > > > > the PHYs the wrong way around between EHCI and MUSB.. > > > > > > > > In any case, I did have omap-usb2 compiled in, but I did not have > > > > OMAP_OCP2SCP=y set. Should OMAP_USB2 depend on that? > > > > > > > > Also, looks like MUSB just sits in b_idle mode though, so no more > > > > ID pin interrupt for some reason. > > > > > > OK looks like I got the ID interrupt going by enabling > > > CONFIG_TWL6030_USB=y. Still stays in a_idle with no keyboard > > > after plugging it in, but now changes between a and b mode. > > > > come again, you ground ID pin and have no devices attached ? Then it > > should stay in a_idle. > > After playing with looks like it detects the keyboard after replugging > the cable a few times. So it's not detecting the keyboard every time when > plugged in, but sounds like that's not related to the DT patches. It's > probably the session bit related issues again.. could be, that part definitely needs some clenaning. -- balbi -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130425/c462710c/attachment.sig> ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-19 17:13 Multiple issues with omap4 panda es in linux next Tony Lindgren ` (2 preceding siblings ...) 2013-04-22 8:41 ` Kishon Vijay Abraham I @ 2013-04-22 9:08 ` Tomi Valkeinen 2013-04-22 10:24 ` Tomi Valkeinen 2013-04-24 19:44 ` Tony Lindgren 4 siblings, 1 reply; 27+ messages in thread From: Tomi Valkeinen @ 2013-04-22 9:08 UTC (permalink / raw) To: linux-arm-kernel On 2013-04-19 20:13, Tony Lindgren wrote: > 3. DSS fails with DT booting > > Works with legacy booting but fails with DT. I'm almost certain > the DT booting was working last week or so? > > This is what I now get with DT booting: > > omapdss DSI error: can't get VDDS_DSI regulator > omapdss HDMI error: can't get VDDA_HDMI_DAC regulator > omapdss HDMI error: device hdmi init failed: -517 > omapdss CORE error: driver probe failed: -22 > ... I think this is the issue Christoph Fritz reported earlier, DSS is being initialized before TWL, and thus DSS doesn't find the regulators. The proper fix is of course to make DSS support EPROBE_DEFER, but that's easier said than done. I'll have a look if I can get it working enough to fix this issue. Tomi -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 899 bytes Desc: OpenPGP digital signature URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130422/88930a19/attachment-0001.sig> ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-22 9:08 ` Tomi Valkeinen @ 2013-04-22 10:24 ` Tomi Valkeinen 2013-04-22 12:21 ` Grygorii Strashko 0 siblings, 1 reply; 27+ messages in thread From: Tomi Valkeinen @ 2013-04-22 10:24 UTC (permalink / raw) To: linux-arm-kernel On 2013-04-22 12:08, Tomi Valkeinen wrote: > On 2013-04-19 20:13, Tony Lindgren wrote: > >> 3. DSS fails with DT booting >> >> Works with legacy booting but fails with DT. I'm almost certain >> the DT booting was working last week or so? >> >> This is what I now get with DT booting: >> >> omapdss DSI error: can't get VDDS_DSI regulator >> omapdss HDMI error: can't get VDDA_HDMI_DAC regulator >> omapdss HDMI error: device hdmi init failed: -517 >> omapdss CORE error: driver probe failed: -22 >> ... > > I think this is the issue Christoph Fritz reported earlier, DSS is being > initialized before TWL, and thus DSS doesn't find the regulators. > > The proper fix is of course to make DSS support EPROBE_DEFER, but that's > easier said than done. I'll have a look if I can get it working enough > to fix this issue. Yes, it seems delayed regulator initialization brought up this issue. I hacked DSI driver of omapdss and Taal panel driver to somewhat work with EPROBE_DEFER. But then the issue was with omapfb. omapfb is currently set to start at late_initcall, so that omapdss and panels are loaded before omapfb. But even that's not late enough to get the regulators for omapdss. It seems the regulators get also initialized at the late_initcall level. Changing omapfb to late_initcall_sync was late enough to get things working. Again, making omapdss, panel drivers and omapfb support EPROBE_DEFER and dynamic panel driver insertion is the proper fix, but it's a big job, and there are "interesting" issues with it (like how to know if a panel device will ever get a driver loaded). But is there something wrong with the TWL and regulators? late_initcall sounds rather late for such a core resource. Even if all drivers supported EPROBE_DEFER, won't it cause extra delays in the boot as drivers are getting probed multiple times? As for fixing the DSS problem for 3.10, I don't have any ideas except pure hacks. I'll continue studying this. Tomi -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 899 bytes Desc: OpenPGP digital signature URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130422/f61fc675/attachment-0001.sig> ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-22 10:24 ` Tomi Valkeinen @ 2013-04-22 12:21 ` Grygorii Strashko 2013-04-22 18:08 ` Tony Lindgren 0 siblings, 1 reply; 27+ messages in thread From: Grygorii Strashko @ 2013-04-22 12:21 UTC (permalink / raw) To: linux-arm-kernel On 04/22/2013 01:24 PM, Tomi Valkeinen wrote: > On 2013-04-22 12:08, Tomi Valkeinen wrote: >> On 2013-04-19 20:13, Tony Lindgren wrote: >> >>> 3. DSS fails with DT booting >>> >>> Works with legacy booting but fails with DT. I'm almost certain >>> the DT booting was working last week or so? >>> >>> This is what I now get with DT booting: >>> >>> omapdss DSI error: can't get VDDS_DSI regulator >>> omapdss HDMI error: can't get VDDA_HDMI_DAC regulator >>> omapdss HDMI error: device hdmi init failed: -517 >>> omapdss CORE error: driver probe failed: -22 >>> ... >> I think this is the issue Christoph Fritz reported earlier, DSS is being >> initialized before TWL, and thus DSS doesn't find the regulators. >> >> The proper fix is of course to make DSS support EPROBE_DEFER, but that's >> easier said than done. I'll have a look if I can get it working enough >> to fix this issue. > Yes, it seems delayed regulator initialization brought up this issue. > > I hacked DSI driver of omapdss and Taal panel driver to somewhat work > with EPROBE_DEFER. But then the issue was with omapfb. > > omapfb is currently set to start at late_initcall, so that omapdss and > panels are loaded before omapfb. But even that's not late enough to get > the regulators for omapdss. It seems the regulators get also initialized > at the late_initcall level. Changing omapfb to late_initcall_sync was > late enough to get things working. > > Again, making omapdss, panel drivers and omapfb support EPROBE_DEFER and > dynamic panel driver insertion is the proper fix, but it's a big job, > and there are "interesting" issues with it (like how to know if a panel > device will ever get a driver loaded). > > But is there something wrong with the TWL and regulators? late_initcall > sounds rather late for such a core resource. Even if all drivers > supported EPROBE_DEFER, won't it cause extra delays in the boot as > drivers are getting probed multiple times? > > As for fixing the DSS problem for 3.10, I don't have any ideas except > pure hacks. I'll continue studying this. Hi Tomi, twl is not initialized because of I2C, I2C is not initialized because of pinctrl-single, pinctrl-single is initialized at mudule/device init time. So, most everything will be shifted at late_initcall time. Hack that sequence is here - https://patchwork.kernel.org/patch/2444501/ > > Tomi > > ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-22 12:21 ` Grygorii Strashko @ 2013-04-22 18:08 ` Tony Lindgren 2013-04-23 13:53 ` Grygorii Strashko 0 siblings, 1 reply; 27+ messages in thread From: Tony Lindgren @ 2013-04-22 18:08 UTC (permalink / raw) To: linux-arm-kernel * Grygorii Strashko <grygorii.strashko@ti.com> [130422 05:27]: > On 04/22/2013 01:24 PM, Tomi Valkeinen wrote: > >On 2013-04-22 12:08, Tomi Valkeinen wrote: > >>On 2013-04-19 20:13, Tony Lindgren wrote: > >> > >>>3. DSS fails with DT booting > >>> > >>>Works with legacy booting but fails with DT. I'm almost certain > >>>the DT booting was working last week or so? > >>> > >>>This is what I now get with DT booting: > >>> > >>>omapdss DSI error: can't get VDDS_DSI regulator > >>>omapdss HDMI error: can't get VDDA_HDMI_DAC regulator > >>>omapdss HDMI error: device hdmi init failed: -517 > >>>omapdss CORE error: driver probe failed: -22 > >>>... > >>I think this is the issue Christoph Fritz reported earlier, DSS is being > >>initialized before TWL, and thus DSS doesn't find the regulators. > >> > >>The proper fix is of course to make DSS support EPROBE_DEFER, but that's > >>easier said than done. I'll have a look if I can get it working enough > >>to fix this issue. > >Yes, it seems delayed regulator initialization brought up this issue. > > > >I hacked DSI driver of omapdss and Taal panel driver to somewhat work > >with EPROBE_DEFER. But then the issue was with omapfb. > > > >omapfb is currently set to start at late_initcall, so that omapdss and > >panels are loaded before omapfb. But even that's not late enough to get > >the regulators for omapdss. It seems the regulators get also initialized > >at the late_initcall level. Changing omapfb to late_initcall_sync was > >late enough to get things working. > > > >Again, making omapdss, panel drivers and omapfb support EPROBE_DEFER and > >dynamic panel driver insertion is the proper fix, but it's a big job, > >and there are "interesting" issues with it (like how to know if a panel > >device will ever get a driver loaded). > > > >But is there something wrong with the TWL and regulators? late_initcall > >sounds rather late for such a core resource. Even if all drivers > >supported EPROBE_DEFER, won't it cause extra delays in the boot as > >drivers are getting probed multiple times? > > > >As for fixing the DSS problem for 3.10, I don't have any ideas except > >pure hacks. I'll continue studying this. > Hi Tomi, > twl is not initialized because of I2C, > I2C is not initialized because of pinctrl-single, > pinctrl-single is initialized at mudule/device init time. > So, most everything will be shifted at late_initcall time. > > Hack that sequence is here - https://patchwork.kernel.org/patch/2444501/ Hmm I'm pretty sure the LCD was working on panda with DT few weeks ago? In any case, all those drivers should be just module_init so we get out of the race to bottom to initialize drivers early. Pinctrl is already before i2c in drivers/Makefile. I suspect there may be some recent regression that has happened in linux next over past few weeks. Regards, Tony ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-22 18:08 ` Tony Lindgren @ 2013-04-23 13:53 ` Grygorii Strashko 2013-04-23 17:31 ` Tony Lindgren 0 siblings, 1 reply; 27+ messages in thread From: Grygorii Strashko @ 2013-04-23 13:53 UTC (permalink / raw) To: linux-arm-kernel On 04/22/2013 09:08 PM, Tony Lindgren wrote: > * Grygorii Strashko <grygorii.strashko@ti.com> [130422 05:27]: >> On 04/22/2013 01:24 PM, Tomi Valkeinen wrote: >>> On 2013-04-22 12:08, Tomi Valkeinen wrote: >>>> On 2013-04-19 20:13, Tony Lindgren wrote: >>>> >>>>> 3. DSS fails with DT booting >>>>> >>>>> Works with legacy booting but fails with DT. I'm almost certain >>>>> the DT booting was working last week or so? >>>>> >>>>> This is what I now get with DT booting: >>>>> >>>>> omapdss DSI error: can't get VDDS_DSI regulator >>>>> omapdss HDMI error: can't get VDDA_HDMI_DAC regulator >>>>> omapdss HDMI error: device hdmi init failed: -517 >>>>> omapdss CORE error: driver probe failed: -22 >>>>> ... >>>> I think this is the issue Christoph Fritz reported earlier, DSS is being >>>> initialized before TWL, and thus DSS doesn't find the regulators. >>>> >>>> The proper fix is of course to make DSS support EPROBE_DEFER, but that's >>>> easier said than done. I'll have a look if I can get it working enough >>>> to fix this issue. >>> Yes, it seems delayed regulator initialization brought up this issue. >>> >>> I hacked DSI driver of omapdss and Taal panel driver to somewhat work >>> with EPROBE_DEFER. But then the issue was with omapfb. >>> >>> omapfb is currently set to start at late_initcall, so that omapdss and >>> panels are loaded before omapfb. But even that's not late enough to get >>> the regulators for omapdss. It seems the regulators get also initialized >>> at the late_initcall level. Changing omapfb to late_initcall_sync was >>> late enough to get things working. >>> >>> Again, making omapdss, panel drivers and omapfb support EPROBE_DEFER and >>> dynamic panel driver insertion is the proper fix, but it's a big job, >>> and there are "interesting" issues with it (like how to know if a panel >>> device will ever get a driver loaded). >>> >>> But is there something wrong with the TWL and regulators? late_initcall >>> sounds rather late for such a core resource. Even if all drivers >>> supported EPROBE_DEFER, won't it cause extra delays in the boot as >>> drivers are getting probed multiple times? >>> >>> As for fixing the DSS problem for 3.10, I don't have any ideas except >>> pure hacks. I'll continue studying this. >> Hi Tomi, >> twl is not initialized because of I2C, >> I2C is not initialized because of pinctrl-single, >> pinctrl-single is initialized at mudule/device init time. >> So, most everything will be shifted at late_initcall time. >> >> Hack that sequence is here - https://patchwork.kernel.org/patch/2444501/ > Hmm I'm pretty sure the LCD was working on panda with DT > few weeks ago? > > In any case, all those drivers should be just module_init > so we get out of the race to bottom to initialize drivers > early. Pinctrl is already before i2c in drivers/Makefile. > > I suspect there may be some recent regression that has > happened in linux next over past few weeks. Hi Tony, I've posted two patches to fix I2C/TWL initialization and they should fix DSS indirectly (if not - DSS need to be shifted to init later). lkml.org/lkml/2013/4/23/215 lkml.org/lkml/2013/4/23/217 In addition, It seems, possibly :), drivers/Makefile might need to be changed a bit: - move generic drivers framework to be initialized first ("base", "clk"); - move "i2c" buses initialization as early as possible (but after "pinctrl" and "gpio") - move "mfd" initialization before "regulators" - move "video" initialization down after "regulators" (as minimum). Regards -grygorii > Regards, > > Tony > -- > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > the body of a message to majordomo at vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-23 13:53 ` Grygorii Strashko @ 2013-04-23 17:31 ` Tony Lindgren 0 siblings, 0 replies; 27+ messages in thread From: Tony Lindgren @ 2013-04-23 17:31 UTC (permalink / raw) To: linux-arm-kernel * Grygorii Strashko <grygorii.strashko@ti.com> [130423 06:59]: > > I've posted two patches to fix I2C/TWL initialization and they should fix > DSS indirectly (if not - DSS need to be shifted to init later). > lkml.org/lkml/2013/4/23/215 > lkml.org/lkml/2013/4/23/217 OK, thanks. We may want to wait a bit on those, but I'll reply to that thread. > In addition, It seems, possibly :), drivers/Makefile might need to > be changed a bit: > - move generic drivers framework to be initialized first ("base", "clk"); > - move "i2c" buses initialization as early as possible (but after > "pinctrl" and "gpio") > - move "mfd" initialization before "regulators" > - move "video" initialization down after "regulators" (as minimum). I doubt that we want to start messing with the current ordering of the drivers/Makefile. That always breaks something else, and the real fix is to get -EPROBE_DEFER to work for us. With the DSS there are way too many dependencies to various other drivers to try to initialize it early. We're better off just fixing it to work with -EPROBE_DEFER. Regards, Tony ^ permalink raw reply [flat|nested] 27+ messages in thread
* Multiple issues with omap4 panda es in linux next 2013-04-19 17:13 Multiple issues with omap4 panda es in linux next Tony Lindgren ` (3 preceding siblings ...) 2013-04-22 9:08 ` Tomi Valkeinen @ 2013-04-24 19:44 ` Tony Lindgren 4 siblings, 0 replies; 27+ messages in thread From: Tony Lindgren @ 2013-04-24 19:44 UTC (permalink / raw) To: linux-arm-kernel * Tony Lindgren <tony@atomide.com> [130419 10:18]: > > 4. WLAN with wl12xx fails with both legacy and DT booting > > No real output here with the legacy mode, just the usual > using pinctrl dummy state warning. The WLAN legacy booting issue was caused by me not having lib80211 module loaded. Regards, Tony ^ permalink raw reply [flat|nested] 27+ messages in thread
end of thread, other threads:[~2013-04-26 8:40 UTC | newest] Thread overview: 27+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2013-04-19 17:13 Multiple issues with omap4 panda es in linux next Tony Lindgren 2013-04-19 17:41 ` Santosh Shilimkar 2013-04-19 17:44 ` Tony Lindgren 2013-04-19 17:53 ` Santosh Shilimkar 2013-04-19 18:18 ` Tony Lindgren 2013-04-25 13:58 ` Kevin Hilman 2013-04-26 8:40 ` Santosh Shilimkar 2013-04-22 7:49 ` Felipe Balbi 2013-04-22 8:41 ` Kishon Vijay Abraham I 2013-04-22 18:03 ` Tony Lindgren 2013-04-23 15:10 ` Kishon Vijay Abraham I 2013-04-23 17:23 ` Tony Lindgren 2013-04-23 21:31 ` Tony Lindgren 2013-04-23 23:16 ` Tony Lindgren 2013-04-24 5:41 ` Kishon Vijay Abraham I 2013-04-24 19:08 ` Tony Lindgren 2013-04-24 19:23 ` Tony Lindgren 2013-04-25 9:04 ` Felipe Balbi 2013-04-25 15:01 ` Tony Lindgren 2013-04-25 15:13 ` Felipe Balbi 2013-04-22 9:08 ` Tomi Valkeinen 2013-04-22 10:24 ` Tomi Valkeinen 2013-04-22 12:21 ` Grygorii Strashko 2013-04-22 18:08 ` Tony Lindgren 2013-04-23 13:53 ` Grygorii Strashko 2013-04-23 17:31 ` Tony Lindgren 2013-04-24 19:44 ` Tony Lindgren
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).