From: nick <xerofoify@gmail.com>
To: inki.dae@samsung.com
Cc: devicetree@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
jy0922.shim@samsung.com, airlied@linux.ie,
sw0312.kim@samsung.com, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, kyungmin.park@samsung.com, kgene@kernel.org,
dri-devel@lists.freedesktop.org, grant.likely@linaro.org,
linux-arm-kernel@lists.infradead.org
Subject: Question about the function,g2d_suspend in the file,exynos_drm_g2d.c
Date: Tue, 13 Jan 2015 00:35:02 -0500 [thread overview]
Message-ID: <54B4AE86.1090301@gmail.com> (raw)
Greetings All,
I am wondering as I don't have the hardware to test if the usleep range has a correct and good
value. Otherwise if one of the maintainers has the hardware and has tested there to be better
values for the sleep range, please send them to me so I can send in a patch for this.
Regards,
Nick
WARNING: multiple messages have this Message-ID (diff)
From: xerofoify@gmail.com (nick)
To: linux-arm-kernel@lists.infradead.org
Subject: Question about the function,g2d_suspend in the file,exynos_drm_g2d.c
Date: Tue, 13 Jan 2015 00:35:02 -0500 [thread overview]
Message-ID: <54B4AE86.1090301@gmail.com> (raw)
Greetings All,
I am wondering as I don't have the hardware to test if the usleep range has a correct and good
value. Otherwise if one of the maintainers has the hardware and has tested there to be better
values for the sleep range, please send them to me so I can send in a patch for this.
Regards,
Nick
next reply other threads:[~2015-01-13 5:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 5:35 nick [this message]
2015-01-13 5:35 ` Question about the function,g2d_suspend in the file,exynos_drm_g2d.c nick
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=54B4AE86.1090301@gmail.com \
--to=xerofoify@gmail.com \
--cc=airlied@linux.ie \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=grant.likely@linaro.org \
--cc=inki.dae@samsung.com \
--cc=jy0922.shim@samsung.com \
--cc=kgene@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sw0312.kim@samsung.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.