On Sat, 2013-04-13 at 20:30 +0200, Javier Martinez Canillas wrote:
> On Sat, Apr 13, 2013 at 7:42 PM, Christoph Fritz
> <chf.fritz@xxxxxxxxxxxxxx> wrote:
> Yes, my last approach to solve the IRQ flags not saved on the
> IORESOURCE_IRQ struct resource issue is to add a new
> irq_get_trigger_type() function to get the edge/level flags from an
> IRQ number and use that function on the smsc911x driver probe function
> to get the IRQ flags.
>
> The patch-set is composed of these patches:
>
> [PATCH v2 1/2] genirq: add function to get IRQ edge/level flags [1]
> [PATCH 2/2] net: smsc911x: get IRQ flags from chip if not present in
> IORESOURCE_IRQ [2]
>
> and the cover letter is this [3]
>
> It would be great if you can test these patches and give some feedback.
>
> > For me it works when doing this in the device tree:
> >
> > +&omap3_pmx_wkup {
> > + pinctrl-names = "default";
> > +
> > + lan9221_pins: pinmux_lan9221_pins {
> > + pinctrl-single,pins = <
> > + 0x5A 0x104 /* gpio_129, INPUT | MODE4 */
> > + >;
> > + };
> > +};
> > +
> > <SNIP>
> > + lan9221@15000000 {
> > + compatible = "smsc,lan9221", "smsc,lan9115";
> > + reg = <0x15000000 0x400>;
>
> If I understood correctly your smsc ethernet chip is connected to the
> OMAP through the GPMC, then you should use a chip-select, base address
> and size instead of the physical address and size.
Yes, it's connected with GPMC.
> Do you have commit 5330dc161 ("ARM: OMAP2+: Add GPMC DT support for
> Ethernet child nodes") already on your tree? [4]
No I haven't.
>
> > + phy-mode = "mii";
> > + interrupt-parent = <&gpio5>;
> > + interrupts = <1 0x2>; /* gpio_129, trigger: falling-edge */
>
> I'm confused here, do you get the IRQ_TYPE_EDGE_FALLING (0x2) trigger
> type flag on the smsc911x driver probe function?
I added printks for irq_res->flags and irq_flags:
[ 1.259857] smsc911x_drv_probe, 2396, irq_res->flags 0x00000400
[ 1.266113] smsc911x_drv_probe, 2397, irq_flags 0x00000000
So the answer is no. But weird that the smsc911x works nevertheless.
>
> > + reg-io-width = <4>;
> > + vdd33a-supply = <®_vcc3>;
> > + vddvario-supply = <®_vcc3>;
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&lan9221_pins>;
> > + };
> >
> > but in arch/arm/mach-omap2/gpmc.c gpmc_probe_dt() I still need this
> > hack:
> >
> > + ret = gpio_request_one(129, GPIOF_IN, "lan9221 irq");
> > + if (ret) {
> > + pr_err("Failed to request IRQ GPIO%d\n", 129);
> > + return ret;
> > + }
> >
>
> Yes, this hack is still needed until we figure out how to enable the
> GPIO bank before a call to request_irq() is made.
>
> > The following patches (already sent mainline) are also applied:
> > "arm/dts: OMAP3: fix pinctrl-single configuration"
> > "net: smsc911x: adopt pinctrl support"
> >
>
> Yes, but that patch is not needed anymore from 3.9, look at this [5]
>
> [1]: http://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg88241.html
> [2]: http://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg88225.html
> [3]: http://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg88224.html
> [4]: https://patchwork.kernel.org/patch/2273851/
> [5]: http://marc.info/?l=linux-kernel&m=135887740715083&w=2
Thanks
-- Christoph
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
