> -----Original Message----- > From: Horia Ioan Geanta Neag > Sent: Wednesday, April 20, 2016 6:42 AM > To: Stuart Yoder <stuart.yoder@xxxxxxx>; Jose Rivera <german.rivera@xxxxxxx> > Cc: gregkh@xxxxxxxxxxxxxxxxxxx; devel@xxxxxxxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; > agraf@xxxxxxx; arnd@xxxxxxxx; Yang-Leo Li <leoyang.li@xxxxxxx> > Subject: Re: [PATCH 11/14] staging: fsl-mc: add quirk handling for dpseci objects < 4.0 > > On 4/11/2016 7:50 PM, Stuart Yoder wrote: > > From: Horia Geanta <horia.geanta@xxxxxxx> > > > > dpseci objects < 4.0 are not coherent-- in spite of the fact > > that the MC reports them to be coherent in certain versions. > > Add a special case to set the no shareability flag for dpseci > > objects < 4.0. > > > > Signed-off-by: Horia Geanta <horia.geanta@xxxxxxx> > > (Stuart: reworded commit message, updated comment in patch) > > Signed-off-by: Stuart Yoder <stuart.yoder@xxxxxxx> > > Do we really need this? > First upstream dpsec driver will be for dpsec >= v4.0. This has nothing to do with the dpsec driver, it's just trying to be complete with potential MC firmware versions that might be encountered. There is supported MC firmware (and example non-upstream Linux drivers) in customer hands with dpsec < 4.0, and we are handling that case even if encountering it is not likely (e.g. what if someone develops their own driver?). So let's keep this quirk for now. Stuart _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
