> > The CC/CV for each battery temperature zone is defined as part of battery > > spec. > This is > > as per the JEITA/PSE standards. So IMO, this is a battery charging > > information > > (charging object) rather than a thermal throttling information. > > > > Also the battery information may not fit into a standard format. Different > > standards > have > > different format for charging object. So I would suggest to make it > > flexible enough to > > support different charging object format. For example MIPI BIF charging > > object > format > > (https://members.mipi.org/wg/BIF/document/11518) and MIPI BIF Rule based > charging algorithm > > (http://mipi.org/sites/default/files/mipi_BIF_rule-based-charging_white-paper_1.pdf) > > has different charging object format. This is why the patch > https://lkml.org/lkml/2014/8/13/355 > > has option to support different charging objects and different charging > > algorithms. > > Yes, and this is also why your patches are not being > merged. Overengineered, too complex. Citing standards will not improve > the patches. > > And yes, adding cc/cv to the thermal interface seems like a good idea > to me.
Sorry to disagree with you. IMHO it's a charging profile and not a thermal profile. The cc/cv information is defined as part of battery spec. If the intention here is to provide a place for battery info, then cc/cv should be part of battery info. The latest charger chips allows to configure CC/CV for different temperature zone. IMHO adding these information to thermal profile doesn't seems to be the right approach since the thermal subsystem need to be aware of the charging subsystem constraints. The standards were cited to point where the industry is moving. Anyway let the maintainer take a final call - should we align with industry standards or stick to legacy charging methodologies? -Jenny -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
