drm/tilcdc: fix parsing of some DT properties
The DT binding for tildc is not consistent with the driver code: there are two options - 'max-width' and 'max-pixelclock' specified in the documentation which are parsed as 'ti,max-width' and 'ti,max-pixelclock' respectively. Make the driver code consistent with the binding. Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com> Reviewed-by: Jyri Sarha <jsarha@ti.com> Signed-off-by: Jyri Sarha <jsarha@ti.com>
This commit is contained in:
		
							parent
							
								
									3672583f25
								
							
						
					
					
						commit
						0186fcce89
					
				| @ -296,12 +296,12 @@ static int tilcdc_init(struct drm_driver *ddrv, struct device *dev) | ||||
| 
 | ||||
| 	DBG("Maximum Bandwidth Value %d", priv->max_bandwidth); | ||||
| 
 | ||||
| 	if (of_property_read_u32(node, "ti,max-width", &priv->max_width)) | ||||
| 	if (of_property_read_u32(node, "max-width", &priv->max_width)) | ||||
| 		priv->max_width = TILCDC_DEFAULT_MAX_WIDTH; | ||||
| 
 | ||||
| 	DBG("Maximum Horizontal Pixel Width Value %dpixels", priv->max_width); | ||||
| 
 | ||||
| 	if (of_property_read_u32(node, "ti,max-pixelclock", | ||||
| 	if (of_property_read_u32(node, "max-pixelclock", | ||||
| 					&priv->max_pixelclock)) | ||||
| 		priv->max_pixelclock = TILCDC_DEFAULT_MAX_PIXELCLOCK; | ||||
| 
 | ||||
|  | ||||
		Loading…
	
		Reference in New Issue
	
	Block a user