Skip to content

Series short description

Tony Lindgren linux-arm-kernel linux-omap 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest0 of 8 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 8 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/8] Series short description
Quoted 32 lines · Hemanth V

----- Original Message ----- From: "Tony Lindgren" <[email protected]>
To: <[email protected]>
Cc: <[email protected]>
Sent: Thursday, November 26, 2009 5:48 AM
Subject: [PATCH 0/8] Series short description

Quoted 24 lines

Hi all,

Here are some omap mux updates for review. These are intended for the v2.6.33 merge window.

Initially this series changes the omap34xx mux code, I'm planning on adding 3630, 2420, and 2430 code later on.

There are several reasons why we need better mux code:

- We want to make the mux code more generic and this will allow us to use the internal signal names and gpio numbers instead of mux register offsets. The internal signal names stay the same across omap generations for some devices.

- We need to map mux registers to GPIO registers for dynamic muxing of the GPIO pins during off-idle.

- We want to be able to override the bootloader mux values for the modded boards, such as the Beagle.

Quoted 6 lines
Quoted 2 lines

- We want to have the mux signals and balls available under debugfs for debugging new drivers.

Does it also detect conflicts when two drivers try to step on each other and overwrite the mux settings of other. SPI and EHCI was one of the problems I faced.

It does not, but that could be added by adding a usecount to struct omap_mux.

In fact it's already a problem with the cmdline mux options as that does not prevent other init code from muxing over the cmdline options.

But then again, just being able to override the bootloader settings might do the trick for most people customizing their Beagle boards.

Currently we're not checking the return values for muxing, so adding a usecount sounds like a follow-up patch after these changes.

Regards,

Tony