[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <285EC979-8472-4634-863C-E7A9967C9AD0@public-files.de>
Date: Fri, 23 Aug 2019 17:35:36 +0200
From: Frank Wunderlich <frank-w@...lic-files.de>
To: linux-mediatek@...ts.infradead.org,
Matthias Brugger <matthias.bgg@...il.com>,
Hsin-Hsiung Wang <hsin-hsiung.wang@...iatek.com>
CC: Mark Rutland <mark.rutland@....com>,
Alessandro Zummo <a.zummo@...ertech.it>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
srv_heupstream@...iatek.com, devicetree@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Sean Wang <sean.wang@...iatek.com>,
Liam Girdwood <lgirdwood@...il.com>,
Rob Herring <robh+dt@...nel.org>, linux-kernel@...r.kernel.org,
Richard Fontana <rfontana@...hat.com>,
Mark Brown <broonie@...nel.org>,
linux-arm-kernel@...ts.infradead.org,
René van Dorst <opensource@...rst.com>,
Thomas Gleixner <tglx@...utronix.de>,
Eddie Huang <eddie.huang@...iatek.com>,
Lee Jones <lee.jones@...aro.org>,
Kate Stewart <kstewart@...uxfoundation.org>,
linux-rtc@...r.kernel.org
Subject: Re: [BUG] [PATCH v5 02/10] mfd: mt6397: extract irq related code from core driver
As far as i understand does old init-function not rely on the chip-id, so it seems that with this commit a prior bug is shown.
maybe the chip-id (should be 0x23 like constant) is set later after irq-request or completely missing for mt6323
Powered by blists - more mailing lists