lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 24 Aug 2020 08:54:56 +0800 From: Qiwu Huang <yanziily@...il.com> To: Greg KH <gregkh@...uxfoundation.org> Cc: Sebastian Reichel <sre@...nel.org>, linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org, Qiwu Huang <huangqiwu@...omi.com> Subject: Re: [PATCH v8 1/4] power: supply: core: add quick charge type property On Tue, Aug 18, 2020 at 2:07 PM Greg KH <gregkh@...uxfoundation.org> wrote: > > On Tue, Aug 18, 2020 at 09:56:28AM +0800, Qiwu Huang wrote: > > On Fri, Aug 14, 2020 at 2:09 PM Greg KH <gregkh@...uxfoundation.org> wrote: > > > > > > On Fri, Aug 14, 2020 at 11:46:54AM +0800, Qiwu Huang wrote: > > > > From: Qiwu Huang <huangqiwu@...omi.com> > > > > > > > > Reports the kind of quick charge type based on > > > > different adapter power. > > > > > > > > Signed-off-by: Qiwu Huang <huangqiwu@...omi.com> > > > > --- > > > > Documentation/ABI/testing/sysfs-class-power | 21 +++++++++ > > > > drivers/power/supply/power_supply_sysfs.c | 1 + > > > > drivers/power/supply/qcom_smbb.c | 51 +++++++++++++++++++++ > > > > include/linux/power_supply.h | 14 ++++++ > > > > 4 files changed, 87 insertions(+) > > > > > > You should also submit your driver that uses these new attributes at the > > > same time. What happened to that request? Otherwise no one really > > > knows how these are being used, or if they even are used by anyone. > > > > > > > I don't think I can submit the whole driver because our drivers are > > divided into three parts, the first part is in ADSP, the second part > > is in kernel and the third part is in Android Hal.This is the second > > part. > > WHat is "ADSP"? ADSP: advanced digital signal processor > > Just submit your kernel driver code, that's all we care about here. > Userspace code is not anything we can do anything with :) If we ported the full driver, we would break the existing driver structure because we would introduce more Qualcomm code. I think that's an unreasonable change. > > thanks, > > greg k-h -- Thanks Qiwu
Powered by blists - more mailing lists