Creating functions for uploading a mipmapped texture.

include/gpu/GrTexture.h

Index: include/gpu/GrTexture.h
diff --git a/include/gpu/GrTexture.h b/include/gpu/GrTexture.h
index ddba94065be2600847422bc887b89db46f62f9a0..15d21f41fad6b8df858bd09f08ce9d92a945eff1 100644
--- a/include/gpu/GrTexture.h
+++ b/include/gpu/GrTexture.h
@@ -51,16 +51,14 @@ protected:
 
 private:
     size_t onGpuMemorySize() const override;
-    void dirtyMipMaps(bool mipMapsDirty);

[bsalomon, 2015/09/15 13:14:10]

What happens if we draw to the base of a texture that has mips? Don't we still
need to regenerate in that case? Maybe we need a test for this case?

[cblume, 2015/09/16 18:40:46]

You are right. Last night, while writing this, I thought "the user will provide
all the mipmap levels." But that isn't the case for rendered-to content. We had
already mentioned that and I forgot last night.

 
     enum MipMapsStatus {
         kNotAllocated_MipMapsStatus,
-        kAllocated_MipMapsStatus,
-        kValid_MipMapsStatus
+        kAllocated_MipMapsStatus
     };
 
     MipMapsStatus   fMipMapsStatus;
-    // These two shift a fixed-point value into normalized coordinates	
+    // These two shift a fixed-point value into normalized coordinates
     // for this texture if the texture is power of two sized.
     int             fShiftFixedX;
     int             fShiftFixedY;