linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Mallon <ryan@bluewatersys.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: linux-fbdev-devel@lists.sourceforge.net,
	arm kernel <linux-arm-kernel@lists.arm.linux.org.uk>
Subject: Re: [RFC PATCH 2/2] ep93xx framebuffer driver
Date: Wed, 27 May 2009 15:04:52 +1200	[thread overview]
Message-ID: <4A1CADD4.7000006@bluewatersys.com> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE1909017FF7FC@mi8nycmail19.Mi8.com>

H Hartley Sweeten wrote:
> On Sunday, May 24, 2009 10:34 PM, Ryan Mallon wrote:
>> This patch adds support for the ep93xx framebuffer. Patch is against
>> arm ep93xx branch.
>>
>> Can anybody with ep93xx hardware please test, specifically with regard
>> to the physical address bit 27 bug. My hardware has the bug, but I'm
>> not sure about other ep93xx chips.
> 
> I have not seen the address bit 27 bug on my custom hardware with
> EP9307 Rev E0 silicon.

Have you had the driver allocate a physical memory address which has bit
27 set? I'm basically wondering whether to enable the check by default
or not. If the problem only exists on a few ep93xx chips then it may be
better to leave the check off by default.

>> +
>> +static struct platform_device ep93xx_fb_device = {
>> +	.name			= "ep93xxfb",
>> +	.id			= 0,
> 
> Since there can only be one framebuffer device how about using
> .id = -1?  This will change the clk dev_id to "ep93xxfb".  Also,
> maybe change the name to "ep93xx-fb", that's how the usb host is
> named.

Will fix both.

> 
>> +	.dev.platform_data	= &ep93xxfb_data,
>> +	.dev.coherent_dma_mask	= 0xf7ffffff,
> 
> I think this is supposed to be
> 
> 	.dev.coherent_dma_mask	= DMA_BIT_MASK(32),
> 
> Or is the missing bit due to the address bit 27 bug?

Yeah, its for bit 27. Not sure how to handle this correctly if the check
is a driver option. If you don't have this problem, just change it to
DMA_BIT_MASK(32) for testing.

~Ryan

-- 
Bluewater Systems Ltd - ARM Technology Solution Centre

       Ryan Mallon                              Unit 5, Amuri Park
       Phone: +64 3 3779127                     404 Barbadoes St
       Fax:   +64 3 3779135                     PO Box 13 889
       Email: ryan@bluewatersys.com             Christchurch, 8013
       Web:   http://www.bluewatersys.com       New Zealand
       Freecall Australia  1800 148 751         USA 1800 261 2934

------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian 
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com 

  reply	other threads:[~2009-05-27  3:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4A1A2ABD.8000104@bluewatersys.com>
2009-05-25  5:33 ` [RFC PATCH 2/2] ep93xx framebuffer driver Ryan Mallon
2009-05-26 16:29   ` H Hartley Sweeten
2009-05-27  3:04     ` Ryan Mallon [this message]
2009-05-27 16:35       ` H Hartley Sweeten

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=4A1CADD4.7000006@bluewatersys.com \
    --to=ryan@bluewatersys.com \
    --cc=hartleys@visionengravers.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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 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).