linux-s390.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Farhan Ali <alifm@linux.vnet.ibm.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>,
	Thomas Huth <thuth@redhat.com>,
	linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
	linux-fbdev@vger.kernel.org
Cc: schwidefsky@de.ibm.com, borntraeger@de.ibm.com,
	stefan.kristiansson@saunalahti.fi
Subject: Re: [PATCH v1 2/2] fbdev: Kconfig: Add HAS_IOMEM dependency for FB_OPENCORES
Date: Fri, 26 Jan 2018 14:32:11 +0000	[thread overview]
Message-ID: <0f10ed78-3275-6356-8357-a6f499213d52@linux.vnet.ibm.com> (raw)
In-Reply-To: <1fae3814-705e-a221-5e58-cef8da3a2f7d@ti.com>



On 01/26/2018 07:38 AM, Tomi Valkeinen wrote:
> On 26/01/18 14:33, Thomas Huth wrote:
>> On 25.01.2018 16:47, Farhan Ali wrote:
>>> The Opencores framebuffer device uses I/O memory and with
>>> CONFIG_HAS_IOMEM disabled will lead to build errors:
>>>
>>> ERROR: "devm_ioremap_resource" [drivers/video/fbdev/ocfb.ko] undefined!
>>>
>>> Fix this by adding HAS_IOMEM dependency for FB_OPENCORES.
>>>
>>> Signed-off-by: Farhan Ali <alifm@linux.vnet.ibm.com>
>>> ---
>>>   drivers/video/fbdev/Kconfig | 2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/video/fbdev/Kconfig b/drivers/video/fbdev/Kconfig
>>> index 5e58f5e..8667e5d 100644
>>> --- a/drivers/video/fbdev/Kconfig
>>> +++ b/drivers/video/fbdev/Kconfig
>>> @@ -976,7 +976,7 @@ config FB_PVR2
>>>   
>>>   config FB_OPENCORES
>>>   	tristate "OpenCores VGA/LCD core 2.0 framebuffer support"
>>> -	depends on FB && HAS_DMA
>>> +	depends on FB && HAS_DMA && HAS_IOMEM
>>>   	select FB_CFB_FILLRECT
>>>   	select FB_CFB_COPYAREA
>>>   	select FB_CFB_IMAGEBLIT
>>
>> I think it would be better if fbdevs in general would depend on
>> HAS_IOMEM ... or could there be any frame buffer devices without IOMEM ?
> 
> There are some small ones which are updated with, say, i2c
> (ssd1307fb.c). I think those don't need iomem.
> 
>   Tomi
> 

Most of the other framebuffer devices are fenced of by architecture 
dependency or PCI dependency. So I am hesitant to introduce a blanket 
dependency for all fbdevs.

Thank you guys for reviewing!

Thanks
Farhan

  reply	other threads:[~2018-01-26 14:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25 15:47 [PATCH v1 0/2] Kconfig changes to enable Graphics Support for S390 Farhan Ali
2018-01-25 15:47 ` [PATCH v1 1/2] Kconfig : Remove HAS_IOMEM dependency for Graphics support Farhan Ali
2018-01-26 12:31   ` Thomas Huth
2018-01-25 15:47 ` [PATCH v1 2/2] fbdev: Kconfig: Add HAS_IOMEM dependency for FB_OPENCORES Farhan Ali
2018-01-26 12:33   ` Thomas Huth
2018-01-26 12:38     ` Tomi Valkeinen
2018-01-26 14:32       ` Farhan Ali [this message]
2018-01-26 13:41 ` [PATCH v1 0/2] Kconfig changes to enable Graphics Support for S390 Geert Uytterhoeven
2018-01-26 14:35   ` Farhan Ali
2018-01-26 15:06     ` Geert Uytterhoeven
2018-01-26 16:26       ` Farhan Ali
2018-01-30 13:22         ` Christian Borntraeger

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=0f10ed78-3275-6356-8357-a6f499213d52@linux.vnet.ibm.com \
    --to=alifm@linux.vnet.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=stefan.kristiansson@saunalahti.fi \
    --cc=thuth@redhat.com \
    --cc=tomi.valkeinen@ti.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 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).