linux-kernel - Re: [PATCH 13/23] mfd/db5500-prcmu: update mailbox handling

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 5 Oct 2011 18:57:11 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Samuel Ortiz <sameo@...ux.intel.com>
Cc:	Linus Walleij <linus.walleij@...ricsson.com>,
	linux-kernel@...r.kernel.org, Lee Jones <lee.jones@...aro.org>,
	Shreshtha Kumar Sahu <shreshthakumar.sahu@...ricsson.com>,
	Vijaya Kumar Kilari <vijay.kilari@...ricsson.com>
Subject: Re: [PATCH 13/23] mfd/db5500-prcmu: update mailbox handling

On Mon, Oct 3, 2011 at 5:53 PM, Samuel Ortiz <sameo@...ux.intel.com> wrote:
> On Fri, Aug 12, 2011 at 10:29:20AM +0200, Linus Walleij wrote:
>> From: Shreshtha Kumar Sahu <shreshthakumar.sahu@...ricsson.com>
>>
>> This updates the mailbox handling to be more robust and
>> adds basic infrastructure for event (IRQ) handling.
>
> This patch and the next one (#14) adds 500 lines of code but I have the
> feeling a lot of it could be shared between 8500 and 5500. What are your plans
> for that ?

I've tried to locate similarities, but it's quite hard. The drivers reflect
the fact that they are talking to software, which is reengineered for
each SoC produced.

So for example if I take a common function like
u*500_prcmu_set_power_state() you can see that they write very
different things into very different mailboxes.

I do look for similarities and try to find some pattern, and I also
think some vtable scheme for switching between the implementations
could be good.

If you think there is too much functional growth and too little
consolidation from patch 13 onwards (i.e. the DB5500 stuff) then
feel free to stop applying at this point.

I think the two fixup patches I just sent out can apply on top of
patch 12 or so anyway, maybe with some patch -p1 <
to avoid patching the clock control in db5500-prcmu.c.

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/