From: Dave Airlie <airlied@gmail.com>
To: Jordan Crouse <jcrouse@codeaurora.org>
Cc: dri-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] drm: Allow platform devices to register as DRM devices
Date: Tue, 16 Mar 2010 13:05:32 +1000 [thread overview]
Message-ID: <21d7e9971003152005j4245ca6dh82462d650cce2bff@mail.gmail.com> (raw)
In-Reply-To: <4B9E76B8.2000208@codeaurora.org>
>
> I guess technically we could also drop the AGP requirement, but since it
> worked
> on my box with AGP=n it seemed to me like a NOP.
Its not a NOP, otherwise we'd remove it, AGP || AGP=n means if
AGP is enabled DRM must be enabled similiarly, it stops AGP=m + DRM=y
basically.
>>> EXPORT_SYMBOL(drm_init);
>>> diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
>>> index ab6c973..48a14a0 100644
>>> --- a/drivers/gpu/drm/drm_edid.c
>>> +++ b/drivers/gpu/drm/drm_edid.c
>>> @@ -1220,6 +1220,9 @@ struct edid *drm_get_edid(struct drm_connector
>>> *connector,
>>> int ret;
>>> struct edid *edid;
>>>
>>> + if (drm_core_check_feature(connector->dev,
>>> DRIVER_USE_PLATFORM_DEVICE))
>>> + return NULL;
>>> +
>>
>>
>> This makes no sense, having the ability to probe EDID or not is most
>> definitely not a platform vs PCI problem.
>
> Yeah, that was my poor man's "Don't probe EDID" hack. I'm not sure if there
> is a smart way to implicitly check to see if EDID should be probed, but I'm
> worried about abusing the features flag too badly, though if a
> DRIVER_USE_EDID
> is needed then we shouldn't be shy about using it.
The generic code never calls this only the driver, so there should be no
need for flags at all.
>> Not 100% sure about this, but if you only intend on KMS and don't need to
>> inform userspace of irq support this should be okay.
>
> Again, a "don't do this" hack. I'll look at this more carefully and see if
> there
> is a good way to evaluate this based on the hooks that the platform has
> defined.
Its mostly used in UMS to inform userspace for some strange reason
its pretty legacy at this point, new driver should probably not hit it.
>>> @@ -60,7 +60,7 @@ static pgprot_t drm_io_prot(uint32_t map_type, struct
>>
>> This also doesn't address noueau/vmwgfx entry points.
>
> Yep, thats my bad. I'll refresh and push better patches without whitespace
> stupidity.
Thanks,
Dave.
next prev parent reply other threads:[~2010-03-16 3:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B8BE42C.1090401@codeaurora.org>
[not found] ` <4B8BE489.7020402@codeaurora.org>
2010-03-15 0:56 ` [PATCH] drm: Allow platform devices to register as DRM devices Dave Airlie
2010-03-15 18:04 ` Jordan Crouse
2010-03-16 3:05 ` Dave Airlie [this message]
2010-03-16 2:41 ` Paul Mundt
2010-03-15 19:27 ` Ville Syrjälä
2010-05-27 19:40 ` [PATCH v2] DRM platform device support jcrouse
2010-08-04 20:48 ` [PATCH v3] " Jordan Crouse
2010-08-04 20:48 ` [PATCH 1/4] drm: Remove drm_resource wrappers Jordan Crouse
2010-08-04 20:53 ` Matt Turner
2010-08-04 20:48 ` [PATCH 2/4] drm: Add support for platform devices to register as DRM devices Jordan Crouse
2010-08-04 20:48 ` [PATCH 3/4] drm: Add __arm defines to DRM Jordan Crouse
2010-08-04 20:48 ` [PATCH 4/4] drm: Make sure the DRM offset matches the CPU Jordan Crouse
2010-05-27 19:40 ` [PATCH 1/4] drm: Remove drm_resource wrappers jcrouse
2010-05-27 21:15 ` Matt Turner
2010-05-27 19:40 ` [PATCH 2/4] drm: Add support for platform devices to register as DRM devices jcrouse
2010-05-27 19:40 ` [PATCH 3/4] drm: Add __arm defines to DRM jcrouse
2010-05-27 19:40 ` [PATCH 4/4] drm: Make sure the DRM offset matches the CPU jcrouse
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=21d7e9971003152005j4245ca6dh82462d650cce2bff@mail.gmail.com \
--to=airlied@gmail.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=jcrouse@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@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).