All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Sumit Semwal <sumit.semwal@ti.com>
Cc: tomi.valkeinen@nokia.com, paul@pwsan.com, hvaibhav@ti.com,
	linux-omap@vger.kernel.org
Subject: Re: [PATCH v7 00/18] OMAP2,3: hwmod DSS Adaptation
Date: Thu, 20 Jan 2011 21:06:27 -0800	[thread overview]
Message-ID: <87fwsmj164.fsf@ti.com> (raw)
In-Reply-To: <1295196103-29417-1-git-send-email-sumit.semwal@ti.com> (Sumit Semwal's message of "Sun, 16 Jan 2011 22:11:25 +0530")

Hi Sumit,

Sumit Semwal <sumit.semwal@ti.com> writes:

[...]

> Testing:
> ---------
> The patches are tested on 2420-n800, 2430sdp, 3630zoom, 3430sdp.
> Complete bootup with penguins on panel is done on 3430sdp.
> For the rest of the mentioned platforms, kernel is built with "OMAP2_DSS"
> and bootup is tested so that base address and clk_get calls are successful.

I think this series needs more validation on the other platforms.
Getting a visible framebuffer w/tux on all tested platforms seems like a
minimal requirement.

I gave a test of this on 3530/Beagle with CONFIG_PANEL_GENERIC_DPI=y and
driving a DVI monitor, using the following kernel cmdline

# cat /proc/cmdline                                                 
console=ttyO2,115200n8 mpurate=600 vram=12M omapfb.mode=dvi:1024x768MR-16@60 omapfb.debug=y omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait

Without your series, I see penguin logo and get a console login on the
screen with this boot log (from dmesg |grep -i omapfb):

[    2.651885] OMAPFB: omapfb_init                                              
[    2.652160] OMAPFB: omapfb_probe                                             
[    2.657653] OMAPFB: create 3 framebuffers                                    
[    2.657714] OMAPFB: fb_infos allocated                                       
[    2.657714] OMAPFB: allocating 1572864 bytes for fb 0                        
[    2.668212] OMAPFB: allocated VRAM paddr 8f400000, vaddr d0a00000            
[    2.668243] OMAPFB: region0 phys 8f400000 virt d0a00000 size=1572864         
[    2.668243] OMAPFB: region1 phys 00000000 virt   (null) size=0               
[    2.668273] OMAPFB: region2 phys 00000000 virt   (null) size=0               
[    2.668273] OMAPFB: fbmems allocated                                         
[    2.668518] OMAPFB: check_fb_var 0                                           
[    2.668548] OMAPFB: max frame size 1572864, line size 2048                   
[    2.668548] OMAPFB: xres = 1024, yres = 768, vxres = 1024, vyres = 768       
[    2.668579] OMAPFB: set_fb_fix                                               
[    2.669036] OMAPFB: fb_infos initialized                                     
[    2.673522] OMAPFB: set_par(0)                                               
[    2.673614] OMAPFB: set_fb_fix                                               
[    2.673614] OMAPFB: apply_changes, fb 0, ovl 0                               
[    2.673645] OMAPFB: setup_overlay 0, posx 0, posy 0, outw 1024, outh 768     
[    2.673645] OMAPFB: paddr 8f400000, vaddr d0a00000                           
[    2.674346] OMAPFB: pan_display(0)                                           
[    2.674346] OMAPFB: setcmap                                                  
[    2.674377] OMAPFB: setcmap                                                  
[    2.683746] OMAPFB: pan_display(0)                                           
[    2.683776] OMAPFB: setcmap                                                  
[    2.692108] OMAPFB: setcmap                                                  
[    2.701599] OMAPFB: framebuffers registered                                  
[    2.701629] OMAPFB: apply_changes, fb 0, ovl 0                               
[    2.701660] OMAPFB: setup_overlay 0, posx 0, posy 0, outw 1024, outh 768     
[    2.701690] OMAPFB: paddr 8f400000, vaddr d0a00000                           
[    2.701721] OMAPFB: apply_changes, fb 1, ovl 1                               
[    2.701751] OMAPFB: apply_changes, fb 2, ovl 2                               
[    2.701751] OMAPFB: create_framebuffers done                                 
[    2.702331] OMAPFB: mgr->apply'ed                                            
[    2.704803] OMAPFB: create sysfs for fbs                                     
[    2.704833] OMAPFB: create sysfs for fbs                                     

With your series applied (no other changes), I don't see anything on the
screen because omapfb_probe() fails:

[    2.519653] OMAPFB: omapfb_init                                              
[    2.519958] OMAPFB: omapfb_probe                                             
[    2.520019] omapfb omapfb: no driver for display                             
[    2.525115] OMAPFB: free_resources                                           
[    2.525146] OMAPFB: free all fbmem                                           
[    2.525177] omapfb omapfb: failed to setup omapfb                            

which indicates that omap_dss_get_device() is failing in omapfb_probe().

Kevin

  parent reply	other threads:[~2011-01-21  5:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-16 16:41 [PATCH v7 00/18] OMAP2,3: hwmod DSS Adaptation Sumit Semwal
2011-01-16 16:41 ` [PATCH v7 01/18] OMAP2,3: DSS2: remove forced clk-disable from omap_dss_remove Sumit Semwal
2011-01-16 16:41 ` [PATCH v7 02/18] OMAP2420: hwmod data: add DSS DISPC RFBI VENC Sumit Semwal
2011-01-16 16:41 ` [PATCH v7 03/18] OMAP2430: " Sumit Semwal
2011-01-16 16:41 ` [PATCH v7 04/18] OMAP3: hwmod data: add DSS DISPC RFBI DSI VENC Sumit Semwal
2011-01-16 16:41 ` [PATCH v7 05/18] OMAP2,3 DSS2 Change driver name to omap_display Sumit Semwal
2011-01-16 16:41 ` [PATCH v7 06/18] OMAP2,3 DSS2 Use Regulator init with driver name Sumit Semwal
2011-01-16 16:41 ` [PATCH v7 07/18] OMAP2,3: DSS2: Create new file display.c for central dss driver registration Sumit Semwal
2011-01-16 16:41 ` [PATCH v7 08/18] OMAP2,3: DSS2: board files: replace platform_device_register with omap_display_init() Sumit Semwal
2011-01-16 16:41 ` [PATCH v7 09/18] OMAP2,3: DSS2: Build omap_device for each DSS HWIP Sumit Semwal
2011-01-16 16:41 ` [PATCH v7 10/18] OMAP2,3: DSS2: DSS: create platform_driver, move init,exit to driver Sumit Semwal
2011-01-16 16:41 ` [PATCH v7 11/18] OMAP2,3: DSS2: Move clocks from core driver to dss driver Sumit Semwal
2011-01-16 16:41 ` [PATCH v7 12/18] OMAP2,3: DSS2: RFBI: create platform_driver, move init,exit to driver Sumit Semwal
2011-01-16 16:41 ` [PATCH v7 13/18] OMAP2,3: DSS2: DISPC: " Sumit Semwal
2011-01-16 16:41 ` [PATCH v7 14/18] OMAP2,3: DSS2: VENC: " Sumit Semwal
2011-01-16 16:41 ` [PATCH v7 15/18] OMAP2,3: DSS2: DSI: " Sumit Semwal
2011-01-16 16:41 ` [PATCH v7 16/18] OMAP2,3: DSS2: replace printk with dev_dbg in init Sumit Semwal
2011-01-16 16:41 ` [PATCH v7 17/18] OMAP2,3: DSS2: Use platform device to get baseaddr Sumit Semwal
2011-01-16 16:41 ` [PATCH v7 18/18] OMAP2,3: DSS2: Get DSS IRQ from platform device Sumit Semwal
2011-01-21  5:06 ` Kevin Hilman [this message]
2011-01-21 11:56   ` [PATCH v7 00/18] OMAP2,3: hwmod DSS Adaptation Semwal, Sumit

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fwsmj164.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=hvaibhav@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=sumit.semwal@ti.com \
    --cc=tomi.valkeinen@nokia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.