netdev - Re: Query on acpi support for dsa driver

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: Fri, 14 Jul 2023 21:19:35 -0700
From: SIMON BABY <simonkbaby@...il.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org
Subject: Re: Query on acpi support for dsa driver

Thank you Andrew for the quick reply and helping this. I will have a look into the sample driver code you provided  and let you know if I have any more queries. 



Regards
Simon

Sent from my iPhone

> On Jul 14, 2023, at 8:17 PM, Andrew Lunn <andrew@...n.ch> wrote:
> 
> On Fri, Jul 14, 2023 at 07:46:27PM -0700, SIMON BABY wrote:
> 
>> Thanks Andrew . So if I add a platform driver, will it get triggered
>> by ACPI table or Device Tree or by some other mechanism?
> 
> There are a couple of options.
> 
> You can just load the module, e.g. via /etc/modules. That is the
> simplest solution.
> 
> If your board has unique BIOS identity strings, you can use that to
> trigger loading. e.g. look at drivers/platform/x86/pcengines-apuv2.c.
> 
> apu_gpio_dmi_table[] __initconst = {
> 
>        /* APU2 w/ legacy BIOS < 4.0.8 */
>        {
>                .ident          = "apu2",
>                .matches        = {
>                        DMI_MATCH(DMI_SYS_VENDOR, "PC Engines"),
>                        DMI_MATCH(DMI_BOARD_NAME, "APU2")
>                },
>                .driver_data    = (void *)&board_apu2,
>        },
> 
> But they BIOS strings need to be unique to your product. If you have a
> generic ComExpress module for example as the core of your product, you
> need to customise the BIOS strings. Otherwise this platform driver
> module will be loaded for any product which happens to have that
> ComExpress card, not just your product.
> 
>> My goal is to see all the switch ports in Linux kernel . The switch
>> is connected via I2C bus .
> 
> Yes, that is the idea of DSA. You can treat the switch ports as Linux
> interfaces. All you need is the control plain bus, i2c in your case,
> and a 'SoC' Ethernet interface connected to one of the ports of the
> switch. I say 'SoC' because such systems are typically ARM or MIPS
> systems with an integrated Ethernet controller, but i guess you have a
> PCIe NIC? i210 or something like that? That works equally as well.
> 
>     Andrew