On Mon, Mar 03, 2014 at 03:01:52AM +, li.xi...@freescale.com wrote:
> I think we should move the set_cache_io() calling more earlier as we discussed
> before, but need much more research and testing. Splitting them into another
> separate patch later will be much better and easier to be
> > "Just removing the set_cache_io() call will not work for all
> > drivers. There are some MFD child devices which use regmap from the parent
> > device. So dev_get_regmap() will return NULL for those."
>
> This is the sort of thing that I was referring to when talking about
> doing the
Just removing the set_cache_io() call will not work for all
drivers. There are some MFD child devices which use regmap from the parent
device. So dev_get_regmap() will return NULL for those.
This is the sort of thing that I was referring to when talking about
doing the non-boring drivers
On Mon, Mar 03, 2014 at 03:01:52AM +, li.xi...@freescale.com wrote:
I think we should move the set_cache_io() calling more earlier as we discussed
before, but need much more research and testing. Splitting them into another
separate patch later will be much better and easier to be
On Fri, Feb 28, 2014 at 05:04:25PM +0800, Xiubo Li wrote:
> "Just removing the set_cache_io() call will not work for all
> drivers. There are some MFD child devices which use regmap from the parent
> device. So dev_get_regmap() will return NULL for those."
This is the sort of thing that I was
On Fri, Feb 28, 2014 at 05:04:25PM +0800, Xiubo Li wrote:
Just removing the set_cache_io() call will not work for all
drivers. There are some MFD child devices which use regmap from the parent
device. So dev_get_regmap() will return NULL for those.
This is the sort of thing that I was
6 matches
Mail list logo
