Displaying 3 results from an estimated 3 matches for "nvkm_client_nam".
Did you mean:
nvkm_client_name
2015 Aug 12
2
[PATCH] Revert "drm/nouveau/fifo/gk104: kick channels when deactivating them"
...*chan)
-{
- struct nvkm_object *obj = (void *)chan;
- struct gk104_fifo_priv *priv = (void *)obj->engine;
-
- nv_wr32(priv, 0x002634, chan->base.chid);
- if (!nv_wait(priv, 0x002634, 0x100000, 0x000000)) {
- nv_error(priv, "channel %d [%s] kick timeout\n",
- chan->base.chid, nvkm_client_name(chan));
- return -EBUSY;
- }
-
- return 0;
-}
-
-static int
gk104_fifo_context_detach(struct nvkm_object *parent, bool suspend,
struct nvkm_object *object)
{
struct nvkm_bar *bar = nvkm_bar(parent);
+ struct gk104_fifo_priv *priv = (void *)parent->engine;
struct gk104_fifo_base *ba...
2015 Jun 08
7
[PATCH 0/5][GIT PULL] Miscellaneous fixes for GF100+
Here are a few small fixes for issues we found while implementing
support for GM20B. The first two are specific to Tegra/GK20A, but
the last 3 patches may have a broader (hopefully beneficial) effect.
Note that the newly introduced gf100_gr_wait_idle() function on patch 5/5
is exported on purpose. GK20A and GM20B drivers will soon make use of it.
Ben, since you seemed to like these changes, a
2015 Aug 31
8
[RFC PATCH v2 0/5] More explicit pushbuf error handling
Hi there,
Resending these now that they've had some more polish and testing, and I heard
that Ben's vacation is over :-)
These patches work as a starting point for more explicit error mechanisms and
better robustness. At the moment, when a job hangs or faults, it seems that
nouveau doesn't quite know how to handle the situation and often results in a
hang. Some of these situations