On Tue, Jun 23, 2020 at 1:37 AM Marc Zyngier wrote:
>
> + Saravana
>
> On 2020-06-23 07:36, Hanks Chen wrote:
>
> [...]
>
> > Hi Marc,
> >
> > I want to break the dependency between ARCH_MEDIATEK and CIRQ/SYSIRQ,
> > because we need to follow the GKI.
>
> This isn't what GKI mandates. GKI requires
+ Saravana
On 2020-06-23 07:36, Hanks Chen wrote:
[...]
Hi Marc,
I want to break the dependency between ARCH_MEDIATEK and CIRQ/SYSIRQ,
because we need to follow the GKI.
This isn't what GKI mandates. GKI requires that the SoC code is compiled
as modules, not that it is dissociated from its
On Thu, 2020-06-18 at 22:22 +0800, Hanks Chen wrote:
> On Thu, 2020-06-18 at 13:41 +0100, Marc Zyngier wrote:
> > On 2020-06-18 13:31, Hanks Chen wrote:
> > > Mediatek sysirq and cirq drivers as-is were bound together to the
> > > config
> > > of ARCH_MEDIATEK. These two drivers should be able to
On Thu, 2020-06-18 at 13:41 +0100, Marc Zyngier wrote:
> On 2020-06-18 13:31, Hanks Chen wrote:
> > Mediatek sysirq and cirq drivers as-is were bound together to the
> > config
> > of ARCH_MEDIATEK. These two drivers should be able to be configured
> > separately. For example, on new Mediatek mo
On 2020-06-18 13:31, Hanks Chen wrote:
Mediatek sysirq and cirq drivers as-is were bound together to the
config
of ARCH_MEDIATEK. These two drivers should be able to be configured
separately. For example, on new Mediatek mobile chips such as
Dimensity
820, the sysirq driver is not used since
5 matches
Mail list logo