linux-kernel - [PATCH 0/1] MFD: Add U300 AB3100 core support v2

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>] [day] [month] [year] [list]

Message-ID: <63386a3d0905181338l2ce5bd9er9f6e4470e3656dd9@mail.gmail.com>
Date:	Mon, 18 May 2009 22:38:08 +0200
From:	Linus Walleij <linus.ml.walleij@...il.com>
To:	linux-kernel@...r.kernel.org, sameo@...ux.intel.com
Cc:	linux-i2c@...r.kernel.org,
	Linus Walleij <linus.walleij@...ricsson.com>
Subject: [PATCH 0/1] MFD: Add U300 AB3100 core support v2

ChangeLog from v1 -> v2:

* use dynamically allocated struct ab3100 holder for
  state encapsulation.

* Create sub-platform_devices for all the devices found
  inside the AB3100. This is done after init, and all
  drivers have to pass the driver_data back in order
  to call back into ab3100-core. I also define a resource
  containing the register range applicable for each
  functionality so that it is actually possible to
  limit register access to the appropriate registers for
  each sub-device sometime further down the road.

* Since all sub-devices are initialized after the AB3100,
  the initialization check could be removed from all
  symbols.

* Converted the callback into a broadcasting notifier,
  simplifying that code quite a bit by catenating the
  event flags into a 24-bit field passed as value to
  the listeners for masking and reacting to the proper
  events.

* Register a secondary dummy I2C client for performing
  test register operations.

* const on AB3100 debugfs file operations struct.

* free_irq() on the IRQ.

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/