From: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v4] fbdev: remove dependency of FB_SH_MOBILE_MERAM from FB_SH_MOBILE_LCDC
Date: Wed, 21 Mar 2012 14:01:00 +0000 [thread overview]
Message-ID: <4F69DF1C.5070508@gmx.de> (raw)
In-Reply-To: <87obrqwxp2.wl%kuninori.morimoto.gx@renesas.com>
Hi Laurent,
On 03/21/2012 01:49 PM, Laurent Pinchart wrote:
> Hi Morimoto-san,
>
> On Tuesday 20 March 2012 18:27:08 Kuninori Morimoto wrote:
>> MERAM can be used for other IP blocks as well in the future.
>> It doesn't necessarily mean that the MERAM driver depends on the LCDC.
>> This patch corrects dependency.
>>
>> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
>> ---
>> v3 -> v4
>>
>> - move config to before endpoint
>
> As the driver doesn't depend on FB and can also be used by other subsystems,
> would it make sense to move it out of drivers/video/ ? drivers/sh/ might be a
> candidate, although I think selecting a location based on the platform is
> frowned upon (drivers/platform/x86 comes to mind). There's probably a better
> location.
Well, as long as it is related to video/graphic I think drivers/video is
a good location. There are also backlight and console in that directory
without being directly related to the framebuffer subsystem.
Best regards,
Florian Tobias Schandinat
>
>> drivers/video/Kconfig | 23 +++++++++++------------
>> 1 files changed, 11 insertions(+), 12 deletions(-)
>>
>> diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig
>> index 8951cbd..0fb9540 100644
>> --- a/drivers/video/Kconfig
>> +++ b/drivers/video/Kconfig
>> @@ -2013,18 +2013,6 @@ config FB_SH_MOBILE_HDMI
>> ---help---
>> Driver for the on-chip SH-Mobile HDMI controller.
>>
>> -config FB_SH_MOBILE_MERAM
>> - tristate "SuperH Mobile MERAM read ahead support for LCDC"
>> - depends on FB_SH_MOBILE_LCDC
>> - default y
>> - ---help---
>> - Enable MERAM support for the SH-Mobile LCD controller.
>> -
>> - This will allow for caching of the framebuffer to provide more
>> - reliable access under heavy main memory bus traffic situations.
>> - Up to 4 memory channels can be configured, allowing 4 RGB or
>> - 2 YCbCr framebuffers to be configured.
>> -
>> config FB_TMIO
>> tristate "Toshiba Mobile IO FrameBuffer support"
>> depends on FB && MFD_CORE
>> @@ -2434,4 +2422,15 @@ if FB || SGI_NEWPORT_CONSOLE
>> source "drivers/video/logo/Kconfig"
>> endif
>>
>> +config FB_SH_MOBILE_MERAM
>> + tristate "SuperH Mobile MERAM read ahead support"
>> + depends on (SUPERH || ARCH_SHMOBILE)
>> + ---help---
>> + Enable MERAM support for the SuperH controller.
>> +
>> + This will allow for caching of the framebuffer to provide more
>> + reliable access under heavy main memory bus traffic situations.
>> + Up to 4 memory channels can be configured, allowing 4 RGB or
>> + 2 YCbCr framebuffers to be configured.
>> +
>> endmenu
next prev parent reply other threads:[~2012-03-21 14:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 1:27 [PATCH v4] fbdev: remove dependency of FB_SH_MOBILE_MERAM from FB_SH_MOBILE_LCDC Kuninori Morimoto
2012-03-21 13:49 ` Laurent Pinchart
2012-03-21 14:01 ` Florian Tobias Schandinat [this message]
2012-03-21 14:09 ` Laurent Pinchart
2012-03-21 14:26 ` Florian Tobias Schandinat
2012-03-21 14:27 ` Laurent Pinchart
2012-03-21 18:46 ` Florian Tobias Schandinat
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=4F69DF1C.5070508@gmx.de \
--to=florianschandinat@gmx.de \
--cc=linux-fbdev@vger.kernel.org \
/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).