Hi Chanwoo,
> >> >> >>> + touchkey@20 {
> >> >> >>> + compatible = "samsung,tm2-touchkey";
> >> >> >>> + reg = <0x20>;
> >> >> >>> + interrupt-parent = <&gpa3>;
> >> >> >>> + interrupts = <2 IRQ_TYPE_EDGE_FALLING>;
> >> >> >>> + vcc-supply = <&ldo32_reg>;
> >> >> >>> + vdd-supply = <&ldo33_reg>;
> >> >> >>> + };
> >> >> >>> +};
> >> >> >>> +
> >> >> >>> &ldo31_reg {
> >> >> >>> regulator-name = "TSP_VDD_1.85V_AP";
> >> >> >>> regulator-min-microvolt = <1850000>;
> >> >>
> >> >> I repiled the touchkey driver against compatible name.
> >> >> Usually, when developing the device driver, we use the specific h/w name
> >> >> but in this patch, the touckey dt node uses the h/w board name instead of
> >> >> original touckhey name.
> >> >
> >> > this should be a device specifically done for the tm2 and we are
> >> > not sure who is the manufacturer of the device. In order to not
> >>
> >> As I knew, this touchkey was made by Cypress semiconductor.
> >> But, for more correct information, you may try to find it.
> >
> > The Android Kernel says that this is the cy8cmbr3xxx. I
> > downloaded the datasheets, but it doesn't have any similarity
> > with the device. Which means that on tm2 we don't the
> > cy8cmbr3xxx bot something else that I even doubt comes from
> > cypress, but I strongly believe it's a dedicated hardware.
>
> Although this device is a dedicated h/w, you should keep the principal.
> Did you check the schematic document of TM2? The schematic document
> might include the specific device name.
>
> Sometimes, the downloaded datasheet does not include the
> all of information of device because of confidential information.
> But, I’m not sure. Just it is guess as my experience.
>
> I want to check the manufacturer and name of device with you
> on next Monday.
Yes, I checked everything, but didn't find the exact device name.
Anyway, let's take this discussion offline and find the correct
way.
Andi
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
