On Fri, Sep 4, 2020 at 12:09 PM William.Sung
<William.Sung@xxxxxxxxxxxxxxxx> wrote:
> > -----Original Message-----
> > From: Andy Shevchenko <andy.shevchenko@xxxxxxxxx>
> > Sent: Friday, September 4, 2020 3:48 PM
> > To: William.Sung <William.Sung@xxxxxxxxxxxxxxxx>
> > On Fri, Sep 4, 2020 at 5:34 AM William.Sung
> > <William.Sung@xxxxxxxxxxxxxxxx> wrote:
> > > > -----Original Message-----
> > > > From: Andy Shevchenko <andy.shevchenko@xxxxxxxxx>
> > > > Sent: Thursday, September 3, 2020 6:42 PM On Thu, Sep 3, 2020 at
> > > > 10:37 AM AceLan Kao <acelan.kao@xxxxxxxxxxxxx>
> > > > wrote:
I think we may return to mailing list now (I slightly censored your
reply to me just in case).
...
> > > > > Here is the ADS5593 asl code, but I have no idea how to re-use it
> > > > > after it's been modified, the only way I know is to override the
> > > > > ACPI tables via initrd[1].
> > > >
> > > > There is also Config FS approach (like overlays) to do it at runtime.
> > > > That what we are using in Yocto build for Intel Edison.
> > > >
> > > > > Could you share some examples in real cases that I can follow?
> > > >
> > > > Yes, like I mentioned StackOverflow search results (maybe G will give
> > better).
> > > > But let's see what you have in your ASL code first.
> > > >
> > > > On the first glance I didn't see any issues with it, but on second look here is
> > one.
> > > > Look into this [5] example.
> > > > If you noticed it uses the same path in Scope and in the reference
> > > > in
> > > > I2cSerialBus() while in your ASL they are different.
> > > >
> > > > Do you have issues with loading it (as is and after above addressed)?
> > >
> > > Maybe I can explain it.
> > > In the beginning, I set I2C1 to both scope and reference in
> > > I2cSerialBus but it doesn't work. Then I check the probe progress of
> > > the i2c controller and found that the fwnode of i2c controller has
> > > replaced by \\_SB.PCI0.D022. After modifying the reference path to it, the
> > ad5593r driver works.
> >
> > Okay, so do I understand this right that you now have working case?
> >
> > About the reference node. Can I see DSDT (you may send it privately if you
> > consider it not for others)?
>
> The attachment is out original DSDT except ADS5593.
Thank you, it's very helpful!
> And the section of ADS5593 is what
> we got, and we do a little modification such as i2c bus reference
> and mode setting to fix our platform. After adding the part of ADS5593, we could successfully
> probe up ad5593r with the driver in the current upstream source code.
>
> > And can you elaborate a bit about I²C host controllers on your platform and
> > how they got enumerated (ACPI / PCI)?
>
> I'm sorry that I don't clearly know how the I2C host controller to be enumerated in our platform.
> The things I know getting from our BIOS team is that they implement in PCI mode (not ACPI mode).
> And the messages I got from dmesg show something like:
> ACPI: bus type PCI registered
> pci 0000:00:18.1 [8086:0f41] type 00 class 0x0c8000 // the i2c controller we used.
> After catting the ADR from the fwnode of I2C controller, I got "0x00180001", so I do know it reference
> to D022. But I do have no idea how it can be done.
This is almost it, only one little part is missed in above is the ACPI
ASL code, i.e.
Device (D022)
{
Name (_ADR, 0x00180001) // _ADR: Address
}
that's how you got your firmware node for certain I²C host controller
and that's why you need that device node.
So, it means that your Scope should also point to this node.
And if you wish you may consider ADS5593 code to be part of DSDT (just
defined somewhere after D022).
> > As I explained AceLan in previous reply the ADS5593 should be a child node of
> > the host controller node in DSDT.
> >
>
> Yes, you're right.
>
> > > I also did the different tests by switching the path of scope and
> > > reference between
> > > I2C1 and PCI0.D022, and the result seems like only the reference path
> > > of I2cSerialBus would impact to the ad5593r.
> >
> > Because we have a workaround in the kernel to find all I2cSerialBus()
> > resources over the ACPI namespace. It *does not* mean you can leave it like
> > this. You basically need to understand device hierarchy in your DSDT. It seems
> > that actual controller is defined as D022 under PCI0 in SB (System Bus) scope.
> >
> > > I will fix it on the same path for consistency and also preventing to have
> > doubts about these.
> > >
> > > About the second _ADR value wrong, from now on the second channel can
> > > be set to the proper mode. But it still needs to be fixed since it was a typo
> > wrong.
> >
> > Basically the ACPI way is to use _ADR, but DT uses 'reg' property for that. I
> > hope at some point we will get some unification between those two in Linux
> > kernel to have common API.
> May I know more about it?
Sure.
> In ads5592r-base.c, it parse the properties by:
> device_for_each_child_node(st->dev, child) {
> ret = fwnode_property_read_u32(child, "reg", ®);
> if (ret || reg >= ARRAY_SIZE(st->channel_modes))
> continue;
>
> ret = fwnode_property_read_u32(child, "adi,mode", &tmp);
> if (!ret)
> st->channel_modes[reg] = tmp;
>
> fwnode_property_read_u32(child, "adi,off-state", &tmp);
> if (!ret)
> st->channel_offstate[reg] = tmp;
> }
> In my understanding, it looks like ad5592r-base parse the properties no matter what
> he ADR value is. Is there a proper way that we could use ADR value instead?
What I meant here is some API instead of
ret = fwnode_property_read_u32(child, "reg", ®);
do something like
ret = fwnode_property_get_child_address(child, ®);
and behind the scenes it will try 'reg' property followed by _ADR evalution.
> > > > [5]:
> > > > https://github.com/westeri/meta-acpi/blob/master/recipes-bsp/acpi-ta
> > > > bles/sa
> > > > mples/edison/ft6236.asli
> > > >
> > > > > Thanks.
> > > > >
> > > > > 1. Documentation/admin-guide/acpi/initrd_table_override.rst
> > > > >
> > > > > Andy Shevchenko <andy.shevchenko@xxxxxxxxx> 於 2020年8月31日
> > 週
> > > > 一 下午8:48寫道：
> > > > > >
> > > > > > On Mon, Aug 31, 2020 at 3:45 PM Andy Shevchenko
> > > > > > <andy.shevchenko@xxxxxxxxx> wrote:
> > > > > > > On Mon, Aug 31, 2020 at 2:28 PM AceLan Kao
> > > > <acelan.kao@xxxxxxxxxxxxx> wrote:
> > > > > > > > This patch is mainly for Advantech's UNO-420[1] which is a
> > > > > > > > x86-based
> > > > platform.
> > > > > > > > This platform is more like a development platform for
> > > > > > > > customers to customize their products, so, specify the
> > > > > > > > channel modes in ACPI table is not generic enough, that's
> > > > > > > > why William submit this patch.
> > > > > > > >
> > > > > > > > Are there other ways to specify or pass values to the module
> > > > > > > > without using module parameters?
> > > > > > > > It's good if we can leverage sysfs, but I don't know if
> > > > > > > > there is one for this scenario.
> > > > > > >
> > > > > > > Can we provide DT bindings for that and use then in ACPI? ACPI
> > > > > > > has a possibility to reuse DT properties and compatible strings [1].
> > > > > > > As far as I can see the driver uses fwnode API, so it supports
> > > > > > > ACPI case already [2]. So, what prevents you to utilize 'adi,mode'
> > > > property?
> > > > > > >
> > > > > > > Also, we accept examples of ASL excerpt in meta-acpi project [3].
> > > > > > > It has already plenty of examples [4] how to use PRP0001 for
> > > > > > > DIY / development boards.
> > > > > > >
> > > > > > > So, take all together I think this patch is simple redundant.
> > > > > >
> > > > > > One more useful link is SO answers on the topic:
> > > > > > https://stackoverflow.com/search?tab=newest&q=prp0001
> > > > > >
> > > > > > > [1]:
> > > > > > > https://www.kernel.org/doc/html/latest/firmware-guide/acpi/enu
> > > > > > > mera tion.html#device-tree-namespace-link-device-id
> > > > > > > [2]:
> > > > > > > https://elixir.bootlin.com/linux/v5.9-rc3/source/Documentation
> > > > > > > /dev icetree/bindings/iio/dac/ad5592r.txt
> > > > > > > [3]: https://github.com/westeri/meta-acpi
> > > > > > > [4]:
> > > > > > > https://github.com/westeri/meta-acpi/tree/master/recipes-bsp/a
> > > > > > > cpi-
> > > > > > > tables/samples
> > > > > > >
> > > > > > > P.S. Jonathan, it seems this driver has artificial ACPI HID.
> > > > > > > We probably have to remove it. However, ADS is indeed reserved
> > > > > > > for Analog Devices in PNP registry. Can we have AD's official answer
> > on this?
> > > > > > > Cc'ing additional AD people.
> > > > > > >
> > > > > > > > 1.
> > > > > > > > https://www.advantech.com/products/9a0cc561-8fc2-4e22-969c-9
> > > > > > > > df90
> > > > > > > > a3952b5/uno-420/mod_2d6a546b-39e3-4bc4-bbf4-ac89e6b7667c
--
With Best Regards,
Andy Shevchenko
